Legal
Our commitment to making Rufkey usable by everyone, the standards we target, the measures we take, and how to reach us with feedback.
Last updated: August 2, 2026
Rufkey is committed to making the marketplace usable by as many people as possible, including users with disabilities. We treat accessibility as a core part of the product rather than an afterthought, and we work to apply recognized accessibility standards throughout design and development. This statement describes the conformance level we target, the measures we take, the known limitations, and how to reach us.
Rufkey targets conformance with WCAG 2.1 Level AA. WCAG — the Web Content Accessibility Guidelines — is the international standard published by the W3C for making web content accessible to people with a wide range of disabilities. Level AA is the most widely referenced conformance level and is the basis for accessibility requirements in many jurisdictions. We continually review the interface against these guidelines as the product evolves.
To meet our accessibility target, Rufkey uses semantic HTML so that screen readers and other assistive technologies can interpret the page structure correctly; ARIA attributes where native semantics are not sufficient; full keyboard navigation so every interactive control is reachable and operable without a mouse; visible focus states so keyboard users can see where they are; and a color palette chosen to meet WCAG contrast ratios for text and interactive elements. We also avoid relying on color alone to convey meaning and provide text alternatives for meaningful images.
Rufkey is designed to be compatible with mainstream screen readers and browser assistive features. We use standard HTML landmarks, headings, and labels so that screen reader users can navigate by region and by heading. Form controls are associated with their labels, and dynamic updates use accessible names and roles where appropriate. We test with common browser and screen reader combinations and address issues reported by users.
Every interactive element on Rufkey — links, buttons, form fields, menus, and dialogs — can be reached and operated with the keyboard alone. Tab order follows the visual layout, and modal dialogs trap focus while open and return focus to the triggering control when closed. We avoid keyboard traps and provide a visible focus indicator on all focusable elements.
Despite our efforts, some content on Rufkey may not yet be fully accessible. Listing media — photographs, virtual tours, and other assets uploaded by sellers — is provided by users and may not include text alternatives or captions. User-generated content such as listing descriptions and messages between buyers and sellers is written by users and may contain formatting that is not fully accessible. We work to provide accessible alternatives where we can and welcome reports of specific issues so we can address them.
If any part of Rufkey is not accessible to you, or if you need an accessible alternative to listing media or user-generated content, contact us through the in-app contact form or by emailing the address listed on the Contact page. We will work with you to provide the information, listing detail, or feature you need in a format that is accessible, and we will prioritize requests that affect your ability to use the marketplace.
We welcome feedback on accessibility. If you encounter a barrier — a control you cannot reach by keyboard, content a screen reader cannot interpret, a contrast issue, or anything else — please report it through the in-app contact form. Include the page or feature, the assistive technology you were using, and a short description of what happened. We review every report and prioritize fixes that block access to core features.
Rufkey assesses accessibility through a combination of automated checks, manual keyboard and screen reader testing, and review against the WCAG 2.1 AA success criteria during development. We revisit this assessment when significant new features ship and when users report issues. This statement will be updated as our conformance status changes.
Rufkey is built with modern web standards and is intended to work with current versions of major browsers and the assistive technologies that run on them. Older browsers or assistive technologies that do not support current standards may not provide the full experience. If you encounter a compatibility issue, please report it so we can investigate and improve support where feasible.
