WCAG 2.1 AA Accessibility Audit and Remediation
Employer
Ivan
Project parameters
Type of cooperationOne-time project
SectionWeb development
Prepaymentwithout prepayment
Payment methodsCash, Bank transfer
Acceptance of requestsfrom today, 04:05 until Sep 8, 2026
Project description
We run a live production website and we need it to be genuinely usable by people with disabilities, not just formally marked as compliant. Right now we honestly do not know how bad the situation is: nobody on our team tests with a screen reader, some pages cannot be navigated with a keyboard alone, and we have had a couple of complaints about text that is hard to read and forms that cannot be completed. We want an expert to go through the whole site, tell us exactly what is broken, and then fix it so we can confidently say we meet WCAG 2.1 Level AA.
The audit should cover the real user journeys: the home page, catalogue and search, a product or service page, registration and login, the contact and checkout forms, and the account area. We expect testing with actual assistive technology (NVDA or VoiceOver plus keyboard-only navigation), not only an automated scanner. We care about the things automated tools miss: logical focus order, visible focus indicators, correct heading structure, meaningful link text, error messages that are announced, form fields tied to their labels, sufficient colour contrast, sensible ARIA roles and states, alt text for images, and accessible names for icon buttons. Please do not add ARIA where native HTML would do the job better.
Deliverables we are looking for: a clear report listing each issue with its WCAG success criterion, severity and where it appears, a prioritised remediation plan, the actual code fixes applied to the site (or a detailed diff we can apply), and a short verification pass confirming the fixes work. A screen-recording of the main flows with a screen reader would help us and our stakeholders understand the result. Ongoing guidance so our developers do not reintroduce the same problems is a plus.
What matters to us:
— Manual testing with a screen reader and keyboard, not just Lighthouse or axe output
— Contrast, focus order, ARIA, forms, headings and alt text all covered
— A compliance report mapped to WCAG 2.1 AA criteria
— Real fixes delivered, then re-tested to confirm they pass
The audit should cover the real user journeys: the home page, catalogue and search, a product or service page, registration and login, the contact and checkout forms, and the account area. We expect testing with actual assistive technology (NVDA or VoiceOver plus keyboard-only navigation), not only an automated scanner. We care about the things automated tools miss: logical focus order, visible focus indicators, correct heading structure, meaningful link text, error messages that are announced, form fields tied to their labels, sufficient colour contrast, sensible ARIA roles and states, alt text for images, and accessible names for icon buttons. Please do not add ARIA where native HTML would do the job better.
Deliverables we are looking for: a clear report listing each issue with its WCAG success criterion, severity and where it appears, a prioritised remediation plan, the actual code fixes applied to the site (or a detailed diff we can apply), and a short verification pass confirming the fixes work. A screen-recording of the main flows with a screen reader would help us and our stakeholders understand the result. Ongoing guidance so our developers do not reintroduce the same problems is a plus.
What matters to us:
— Manual testing with a screen reader and keyboard, not just Lighthouse or axe output
— Contrast, focus order, ARIA, forms, headings and alt text all covered
— A compliance report mapped to WCAG 2.1 AA criteria
— Real fixes delivered, then re-tested to confirm they pass
