Accessibility
Designed to work for more people
Nauro is targeting WCAG 2.2 Level AA. This is a target and engineering commitment, not a claim that an independent conformance audit has been completed.
On this page
The legal and support pages implement accessible foundations and have received code-level checks. Keyboard, screen-reader, 200% zoom, high-contrast, color-vision, and device testing are still required across the complete web product before launch.
1. Our accessibility target
Nauro's product requirements set WCAG 2.2 Level AA as the standard for public marketing, support, legal, account deletion, and shared-bill experiences. We aim to make core tasks usable with a keyboard, screen reader, larger text, reduced motion, and without relying on color alone.
Accessibility work is ongoing. New features should be tested before release, and problems should be treated as product defects rather than optional polish.
2. Implemented on these pages
- A skip link moves directly to the main content.
- Landmarks, headings, lists, tables, labels, and native disclosure controls use semantic HTML.
- Interactive controls have visible focus indicators and a minimum 44-by-44 CSS pixel target where practical.
- Text and layout reflow for narrow screens and enlarged browser text.
- Legal documents use a readable line length and print-specific styles.
- Reduced-motion preferences disable nonessential movement in this page family.
- Status words accompany color, so color is never the only status signal.
- Horizontal overflow is contained for data tables on small screens.
3. Forms, errors, and status feedback
Interactive support, report, privacy-choice, and account interfaces use visible labels and native input types. Required fields are marked in text, and status feedback is announced in a live region.
A request interface must clearly report whether it was accepted. It must not present a success state when its configured service is unavailable.
4. Compatibility approach
The launch test plan includes current Safari on iPhone and macOS, current Chrome on Android, macOS, and Windows, and current Edge on Windows. It also calls for small-screen iPhone, narrow Android, iPad portrait, 1280- and 1440-pixel desktop, large text, keyboard, screen-reader, high-contrast, and 200% zoom reviews.
This statement does not claim that every combination has passed. Test results should be recorded and linked from the launch evidence before the status is upgraded.
5. Known limitations
- No independent WCAG audit or accessibility certification is recorded.
- The full shared-bill, receipt, payment, and live-update experiences require their own assistive-technology testing.
- A monitored accessibility-support response process must be verified before public launch.
A limitation on one route should not block improvements elsewhere. The implementation will update this statement as testing and fixes are completed.
6. Accessibility feedback
If an accessibility barrier prevents you from using Nauro, useful details include the page, the task you were trying to complete, your browser and assistive technology, and what happened. Do not include a raw bill link, receipt, session token, or other sensitive data.
Email support@nauro.app or use the support page and select accessibility as the topic. A verified response owner and monitored delivery service remain launch requirements.