Freelance › Projects › Web development › Web programming › Web accessibility (WCAG) audit and fixes for an existing site
Web accessibility (WCAG) audit and fixes for an existing site
Employer
Dmytro
Project parameters
Type of cooperationOne-time project
SectionWeb development, Web programming
Prepaymentwithout prepayment
Payment methodsCash, Bank transfer
Acceptance of requestsfrom today, 00:47 until Aug 31, 2026
Project description
We run a live marketing website with a few interactive sections (forms, a filterable catalog, a modal cart) and we have never checked it for accessibility. Recently a customer using a screen reader told us they could not complete checkout, and that pushed accessibility to the top of our list. I am looking for a specialist who can audit the site against WCAG 2.1 AA, tell us plainly where we fall short, and then actually fix the problems rather than just handing over a spreadsheet of complaints.
The work has two clear phases. First, a structured audit: automated scanning plus manual testing with a keyboard and at least one real screen reader, covering the templates that matter (home, catalog, product, a content page, and the full checkout flow). I want a prioritized report that separates blockers from minor issues, references the specific success criteria, and includes reproduction notes so my developers understand each finding. Second, the implementation: you apply the fixes directly in our templates and confirm the result. Please keep the visual design intact and avoid regressions on existing behavior.
The front end is plain HTML, CSS and a bit of vanilla JavaScript, so no heavy framework knowledge is required, but I do expect solid judgement about when ARIA is appropriate and when native semantics are the better answer. Share a short example of a past audit or a before/after you have done, and tell me how you verify a fix actually works for assistive technology.
— Audit against WCAG 2.1 AA with both automated tools and manual keyboard/screen-reader testing
— Prioritized report: blockers vs minor, mapped to success criteria, with reproduction steps
— Fix semantic structure, heading order, landmarks and form labels
— Ensure full keyboard operability, visible focus, and logical focus order in modals
— Correct color contrast and add sensible text alternatives
— Apply ARIA only where native HTML cannot express the pattern
The work has two clear phases. First, a structured audit: automated scanning plus manual testing with a keyboard and at least one real screen reader, covering the templates that matter (home, catalog, product, a content page, and the full checkout flow). I want a prioritized report that separates blockers from minor issues, references the specific success criteria, and includes reproduction notes so my developers understand each finding. Second, the implementation: you apply the fixes directly in our templates and confirm the result. Please keep the visual design intact and avoid regressions on existing behavior.
The front end is plain HTML, CSS and a bit of vanilla JavaScript, so no heavy framework knowledge is required, but I do expect solid judgement about when ARIA is appropriate and when native semantics are the better answer. Share a short example of a past audit or a before/after you have done, and tell me how you verify a fix actually works for assistive technology.
— Audit against WCAG 2.1 AA with both automated tools and manual keyboard/screen-reader testing
— Prioritized report: blockers vs minor, mapped to success criteria, with reproduction steps
— Fix semantic structure, heading order, landmarks and form labels
— Ensure full keyboard operability, visible focus, and logical focus order in modals
— Correct color contrast and add sensible text alternatives
— Apply ARIA only where native HTML cannot express the pattern
