Keyboard access
We design navigation, forms, controls, and dialogs to work without requiring a mouse.
Access for more people
Accessibility Statement
Rumiby is committed to making property discovery and professional connections usable by people with diverse abilities.
Last updated: September 8, 2026
Readable presentation
We use structured headings, visible focus states, legible type, and color contrast as product requirements.
Clear language
We aim for understandable labels, instructions, validation messages, and descriptions of important limitations.
Responsive use
Core experiences are designed to work across current mobile and desktop browsers at different viewport sizes.
Our accessibility goal
We use the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA as our target. WCAG organizes accessibility around content that is perceivable, operable, understandable, and robust.
Rumiby has not yet completed an independent, site-wide accessibility audit. Accordingly, we do not claim that every page or feature fully conforms to WCAG 2.2 AA today. Accessibility is an ongoing engineering and content responsibility, not a one-time certification.
Known limitations
We are continuing to evaluate the following areas:
- Interactive maps may not communicate every spatial relationship equally well to screen-reader or keyboard users.
- Property photographs and user-submitted profile images may have incomplete or inconsistent text alternatives.
- User-provided property descriptions may contain unclear formatting or language outside Rumiby’s direct control.
- Some authentication, mapping, and other third-party interfaces may have accessibility behavior controlled by their providers.
Where a map or image is difficult to use, property information should also be available in the accompanying listing text. Contact us if you need information in another reasonable format.
Compatibility and testing
Rumiby is built with semantic HTML, CSS, JavaScript, and ARIA where appropriate. We intend to support current versions of major browsers and commonly used assistive technologies. Older browsers or unusual browser and assistive-technology combinations may not provide the same experience.
Our evaluation process currently includes developer review, keyboard checks, responsive testing, and automated linting. Automated tools cannot identify every accessibility barrier, and broader manual and assistive-technology testing remains part of our roadmap.
Feedback and assistance
If you encounter a barrier, tell us the page or feature, what you were trying to accomplish, the browser or assistive technology used, and the format or accommodation that would help. Do not include passwords or sensitive financial or identity information.
Rumiby Accessibility
accessibility@rumiby.comWe will make a good-faith effort to review feedback and provide a reasonable alternative when available. This statement does not limit rights available under applicable law.
Read the official W3C overview of WCAG or return to Rumiby.