evomedia.netAccessibility audit and remediation
A whole-site audit against WCAG 2.2 AA, the fixes made in your code, and a re-test, by a disabled engineer who builds for his own input method.
Why me
I was a Principal QA Engineer at Autodesk for twenty years: finding what breaks, before the people who depend on it do. I am also disabled. I type with a mouthstick, one key at a time, and point with a trackball. So I know from the inside what a drag-only control, a tiny target or a focus ring you cannot see costs a person, and I build for it: evo.ablecamera and evo.polaris were made for people with limited fine motor control, starting with me.
This site has been through the same automated sweep, keyboard walk and screen-reader pass I would run on yours, and it has an accessibility mode and a page that says exactly what was checked. Everything in this portfolio was built with the same mouthstick. None of it slowed the work down.
What you get
- A whole-site sweep with the scanner’s engine, without its page limit, at desktop and phone widths, in your default look and in any accessibility mode you have.
- A keyboard and screen-reader pass of the paths that matter: sign-in, search, the forms that make you money, the menus, with NVDA and with nothing but a keyboard.
- A written report against the WCAG 2.2 criteria: what fails, where, why it matters to a real person, and what to change, ordered by impact.
- The fixes, made in your code as pull requests you review, or, where a fix would change your design, an accessibility mode like this site’s that turns every aid on at once.
- A re-test and an accessibility statement you can publish honestly.
How to start
Run the free scan at wcag.evomedia.net first if you like; it takes a minute and the report is yours either way. Then get in touch with the address of the site and, if you have one, the scan’s link. I will come back with what I found on a first look and a quote for the audit; the remediation is quoted once the audit says how much there is.