1. Our accessibility commitment
HouseKeepr is designed and tested to conform to WCAG 2.2 Level AA. We treat accessibility as an ongoing product requirement and include accessibility checks in development and regression testing.
This is a HouseKeepr conformance statement, not a certification or endorsement by W3C. W3C does not verify individual conformance claims.
2. Scope of this statement
This statement covers the HouseKeepr web application and HouseKeepr-authored public pages at housekeepr.pro as of September 4, 2026. It covers HouseKeepr-authored interfaces rendered with HTML, CSS, and JavaScript.
External websites opened from HouseKeepr, including retailer and partner services, are operated by third parties and are not included in this conformance scope.
3. Accessibility features
HouseKeepr includes accessibility support such as:
- Keyboard-accessible navigation and controls, including keyboard alternatives for reorderable dashboard content.
- A skip link, semantic landmarks, programmatic labels, route-focus management, and live status announcements.
- Visible keyboard focus treatment and controls sized or spaced for accessible interaction.
- Text-size controls, responsive reflow, and support for WCAG text-spacing adjustments.
- Reduced-motion support for users who request less animation.
- Alternative text or appropriate decorative treatment for images and icons.
- Color and contrast rules intended to keep information readable across HouseKeepr themes.
- No core HouseKeepr task that depends on hearing audio.
4. How we evaluated HouseKeepr
Our September 4, 2026 accessibility review combined source-level regression tests, production build checks, layout and reflow testing, and browser-based behavioral testing. The behavioral suite exercises mobile WebKit and desktop Chromium and covers areas including keyboard operation, skip-link and route focus, modal focus behavior, focus visibility, 320-pixel reflow, text spacing, target sizing, and keyboard alternatives for drag-and-drop interactions.
The current automated and browser-level accessibility suites passed at the conclusion of this review. Automated testing cannot by itself prove accessibility for every user or assistive-technology combination.
5. Assistive technology testing
HouseKeepr has not yet completed a documented human test pass using dedicated screen readers such as NVDA, JAWS, or VoiceOver. The application includes programmatic semantics intended for assistive technologies, but we disclose this testing limitation rather than representing automated browser testing as human screen-reader verification.
We intend to continue accessibility evaluation as HouseKeepr changes and to address verified accessibility barriers as they are identified.
6. Feedback and accessibility problems
If you encounter an accessibility barrier in HouseKeepr, please use the Feedback page inside the application and describe the page, feature, and problem you encountered. Accessibility reports are useful even when a problem occurs only with a particular browser, device, keyboard workflow, or assistive technology.
We will use accessibility feedback to investigate reproducible barriers and prioritize appropriate corrections.
7. Maintaining conformance
HouseKeepr is actively developed. New or materially changed interfaces are expected to preserve the accessibility requirements covered by our regression and behavioral testing. If a future change creates a known accessibility issue, we will work to correct it and update this statement when the scope or status of our conformance claim materially changes.