Our accessibility statement
Fix4Ever is committed to making its platform usable by as many people as possible, including those who rely on assistive technologies. This page describes what we have done, what we are still working on, and how to report issues.
Last reviewed: March 2026
Accessibility measures in place
These are the concrete steps we have taken to improve accessibility across the Fix4Ever web application.
Keyboard navigation
All interactive elements — buttons, links, form fields, and modals — are reachable and operable using a keyboard alone. We use logical tab order and visible focus indicators throughout.
Screen reader compatibility
We use semantic HTML elements, ARIA labels, and landmark roles to ensure our pages are readable by screen readers such as NVDA (Windows), JAWS, and VoiceOver (macOS/iOS).
Colour contrast
We aim to meet WCAG 2.1 Level AA colour contrast ratios for all text and interactive elements. If you find a contrast issue, please report it so we can fix it.
Responsive layout
Fix4Ever works on a range of screen sizes and supports browser text zoom up to at least 200% without loss of content or functionality. The site does not rely on horizontal scrolling.
Form accessibility
All form fields have visible labels. Error messages are descriptive and associated with their respective fields. Required fields are clearly marked.
Known accessibility issues
We believe in being transparent about what is not yet fully accessible. The following are known issues we are actively working to resolve.
- 1
Some older modal dialogs may not trap keyboard focus correctly — we are actively fixing these.
- 2
The real-time chat component may not announce new messages to screen readers automatically in all browsers.
- 3
A small number of icon-only buttons may be missing accessible labels — these are being addressed.
Technical approach
Fix4Ever is a Next.js application. We write semantic HTML5 and use Tailwind CSS. We are targeting WCAG 2.1 Level AA as our standard. We have not yet commissioned an independent accessibility audit.
- –Semantic HTML elements (nav, main, section, header)
- –ARIA roles and labels on interactive components
- –Visible focus ring on all focusable elements
- –Descriptive alt text on meaningful images
- –Server-side rendering for fast initial load
Frequently asked questions
Found an accessibility issue?
We want to know. Email us with:
- The page or feature where you encountered the issue
- A description of what happened
- The browser and assistive technology you were using
We aim to respond to accessibility reports within 3 business days.