Accessibility Statement

Fixxo is built for people who need something fixed at home. That includes people who are older, disabled, or using a screen reader, a keyboard, or a phone in poor light with one hand. Accessibility is part of doing the job properly.

Our commitment

We work to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA. We treat accessibility as a launch requirement rather than a follow-up project, and we include it in our design system so that every new page starts accessible rather than being remediated later.

We also aim to meet the requirements of the Americans with Disabilities Act as applied to websites and mobile apps, and we do not discriminate against a customer or a technician on the basis of disability.

What we have done

• Semantic structure. One main landmark per page, correctly ordered headings, and landmark regions for navigation and content.
• Keyboard operation. Every interactive control — navigation, forms, the consent checkbox, dialogs — is reachable and operable by keyboard alone, with a visible focus indicator that is not suppressed.
• Skip link. A skip-to-content link is the first focusable element on every page.
• Colour contrast. Body text and interface text meet or exceed the AA contrast ratio for their size, including our accent purple on white and white on purple.
• Not colour alone. Status is never communicated by colour by itself — a label, icon or text accompanies it.
• Text scaling. Layouts tolerate text resized to 200% and reflow to a single column without horizontal scrolling at 320 CSS pixels.
• Touch targets. Interactive targets meet the 24×24 CSS pixel minimum, and our primary controls are larger.
• Alternative text. Informative images carry meaningful descriptions; decorative images are marked so they are ignored.
• Forms. Every input has a programmatically associated label, errors are identified in text and not by colour alone, and instructions do not depend on sensory characteristics alone.
• Motion. We respect the prefers-reduced-motion setting and keep animation minimal and non-essential.
• Language and reading order. Pages declare their language, and the DOM order matches the visual order for screen-reader users.
• Consistent help. Contact routes and the accessibility feedback address appear in the same place on every page.

Assistive technology we consider

• Screen readers including NVDA and JAWS on Windows, VoiceOver on macOS and iOS, and TalkBack on Android.
• Screen magnification and operating-system text scaling.
• Speech recognition and switch or other alternative input devices.
• Browser and operating-system high-contrast and dark modes.

Known limitations

We would rather list what is not yet right than claim perfection.

• Third-party embedded content — such as map or scheduling widgets — may not fully meet AA. Where we use them, we provide an equivalent route: you can always complete a booking or an application by email or by speaking to a person.
• User-submitted photographs — the photographs customers send us are not written by us and may lack descriptions. Our interface does not depend on those images alone to convey information.
• PDFs — where we publish a document as a PDF, we aim to provide a tagged, accessible version and, where possible, an HTML equivalent. If you need one in another format, ask and we will supply it.
• Legacy content — pages published before this statement may not yet meet every criterion. They are being brought into line, and the pages in the main navigation have been prioritised.

Accessibility is not only about the website

• Telephone and email booking are available for anyone who cannot or would rather not use the app. You are never required to use an automated system.
• Technicians are expected to accommodate reasonable access and communication needs, including speaking clearly, allowing extra time, and following instructions given by a carer or family member where you have authorised it.
• Service animals are welcome at every appointment.
• If you need a different format — large print, plain text, or an audio version of any policy on this site — we will provide it free of charge.

How we test

• Automated checks on every build for contrast, labelling, landmarks and heading order.
• Manual keyboard-only passes on new screens before release.
• Screen-reader checks on the booking and application flows, which are the highest-risk journeys.
• Review of new components against WCAG 2.2 AA criteria as part of the design system, before they ship.

Tell us about a barrier

If something on this site or in our service is difficult or impossible for you to use, we want to know, and we will not treat your report as a complaint.

• Email: [email protected]
• By post: Fixxo LLC, Virginia, United States, marked "Accessibility"
• What to include: the page or step you were on, what you were trying to do, and what happened. A screenshot or the assistive technology you use helps but is not required.

What you can expect: we acknowledge your report within two working days, tell you what we plan to do and when, and give you an alternative way to complete the task in the meantime — including taking the booking or application over email or by phone. If we cannot fix something immediately, we will tell you that plainly rather than leaving it unanswered.

Enforcement

If you are not satisfied with our response, you may raise the matter with the relevant civil-rights or disability authority. We would always prefer the chance to fix it first.

This statement describes our current accessibility position in good faith. It is not a warranty of full conformance, and it does not limit any right you have under disability-access law.