Accessibility

Our commitment

Repaired is committed to ensuring the website and web app are accessible to people with disabilities, and to holding the Android and iOS apps to the same bar when they ship. We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA.

What we support

• Keyboard navigation. All interactive elements on the website are reachable and operable with a keyboard alone. Focus order follows the visual layout.
• Skip link. A “Skip to main content” link is the first focusable element on every page, letting keyboard and screen reader users bypass navigation.
• Focus indicators. Visible focus outlines are present on all focusable elements. We do not suppress :focus-visible styles.
• Color contrast. Text and interactive elements meet WCAG AA contrast ratios (4.5:1 for normal text, 3:1 for large text).
• Semantic HTML. Pages use appropriate heading hierarchy, landmark regions (header, main, nav, footer), and ARIA labels on interactive elements where native semantics are insufficient.
• Responsive layout. Content reflows at all zoom levels up to 400% without loss of content or functionality.
• Mobile touch targets. Interactive elements meet the WCAG 2.5.5 minimum touch target size of 44×44px on mobile devices.

How we test it

Accessibility here is a build gate rather than a periodic review. Automated axe checks run against every public page on every pull request, and a failure blocks the merge in the same way a failing unit test does. Interactive states are checked too, not just the page as it first loads: a quiz mid-question and a quiz showing its result are separate assertions, because a page can pass on arrival and fail the moment someone uses it.

Colour contrast is checked the same way. When we recently put a breadcrumb trail on a dark gradient header, the contrast was verified with axe across every changed page before it shipped, rather than judged by eye.

Automated testing has real limits. It catches missing labels, broken heading order, and insufficient contrast. It does not catch a form that is technically labelled but confusing, or a flow that is exhausting to complete with a keyboard. Those need people, which is why the reporting route below matters more than the test suite.

What we aim for

WCAG 2.2 Level AA is the standard we hold the product to. That covers keyboard operation of everything interactive, visible focus indicators, text that scales without breaking layout, respect for reduced-motion preferences, and content that makes sense when read aloud in order.

Known limitations

• Web only for now. Repaired currently runs in the browser; native Android and iOS apps are in development. The web app is tested with screen readers, but platform-native assistive technology integration (TalkBack, VoiceOver) arrives with the native apps.
• Third-party content. Some external links (Google Play Store, research papers) lead to pages we do not control and cannot guarantee are accessible.

Reporting an issue

If you encounter an accessibility barrier on the website or in the app, please let us know. We take these reports seriously and will respond within five business days.

Email: hello@repairedapp.com

Please include the URL or screen where you encountered the issue and a description of what happened. If you use assistive technology, let us know which one. It helps us reproduce and fix the problem faster.

Feedback

We welcome feedback on the accessibility of Repaired. If you find something that works well, we want to know that too.