Table of Contents
Website accessibility auditing is becoming a more visible freelance service, but it is not a shortcut based on running one automated scanner. A responsible audit combines automated checks, keyboard testing, screen-reader review, content inspection, and human judgment. It also communicates limitations clearly: an audit can identify barriers and support remediation, but a freelancer should not promise legal compliance unless qualified to provide jurisdiction-specific legal advice.
The standards landscape is moving. W3C recommends using WCAG 2.2, which adds nine success criteria to WCAG 2.1. In September 2026, an updated European accessibility standard, EN 301 549 v4.1.1, adopted WCAG 2.2 as its technical benchmark. AccessibleEU cautions that the new version is not yet the formal legal reference for demonstrating conformity with the European Accessibility Act until cited in the EU Official Journal. That distinction is exactly why audit reports should separate technical findings from legal conclusions.

What an accessibility audit delivers
A useful audit answers four questions:
- What barrier exists?
- Who may be affected?
- How can the issue be reproduced?
- What practical change should the team make?
The deliverable may include an executive summary, tested pages and components, methods and assistive technologies used, findings mapped to WCAG criteria, severity and priority, screenshots or code examples, remediation guidance, and a retest plan.
Avoid presenting a raw scanner export as an audit. Automated tools can quickly detect some missing labels, contrast failures, structural errors, and code patterns. They cannot reliably decide whether alternative text communicates the right meaning, whether focus order follows the intended task, or whether an error message is genuinely understandable.
Define the scope before quoting
The cost and effort depend less on the total number of URLs than on unique templates and interactions. A 500-page site built from five templates may be easier to sample than a 20-page application with complex dashboards, modals, charts, and authentication.
Ask the client:
- Which countries and policies apply to the organization?
- Is the target WCAG 2.1 or 2.2, and at which conformance level?
- Which user journeys are business-critical?
- Are logged-in pages, mobile layouts, PDFs, videos, and third-party widgets included?
- Can the client provide a staging environment and test account?
- Does the team want findings only, developer-ready tickets, or remediation support?
- Will a retest be included?
Write exclusions explicitly. If PDFs, native mobile apps, or legal interpretation are outside the assignment, say so.
A defensible testing workflow
Start with discovery. Identify templates, repeated components, forms, navigation patterns, and critical journeys such as registration, checkout, search, and account recovery. Select a representative sample instead of pretending that every URL received equal manual attention.
Run automated checks next, but record the tool and version. Treat results as leads, not final conclusions. Remove duplicates and verify each issue manually.
Perform keyboard-only testing. Check visible focus, logical focus order, skip links, menus, dialogs, form controls, and whether every function works without a mouse. Then test zoom and reflow at relevant viewport sizes. Inspect headings, landmarks, link purpose, labels, instructions, errors, captions, alternative text, and color reliance.
Use at least one screen reader appropriate to the platform you support. A beginner should start with a limited, transparent matrix rather than claiming universal coverage. Document browser, operating system, assistive technology, and version.
Finally, group systemic issues. If the same inaccessible button component appears 60 times, explain the shared root cause and list representative occurrences. This helps developers fix the design system rather than closing dozens of duplicate tickets.
How to write useful findings
Each issue should contain:
- a short descriptive title;
- affected page or component;
- steps to reproduce;
- observed result;
- expected accessible behavior;
- relevant WCAG success criterion;
- impact on users;
- severity and remediation priority;
- a concrete recommendation;
- evidence such as a screenshot or code excerpt.
Do not rely on severity alone. A high-impact issue in a rarely used legacy page may be scheduled differently from a medium barrier that blocks every checkout. Include both user impact and business priority.
Build a portfolio ethically
Audit a small open-source demo, your own website, or a site whose owner has given permission. Avoid publicly shaming small businesses. A portfolio case study can show a before-and-after component, a sample finding, a test matrix, and a remediation ticket.
Create three sample artifacts: a one-page executive summary for leadership, a detailed finding for developers, and a plain-language content recommendation for editors. This demonstrates that you can communicate with different audiences.
Packaging and pricing
Possible service tiers include:
- Focused review: one critical journey and a few shared components;
- Representative audit: selected templates, journeys, and manual tests;
- Audit plus remediation support: findings, developer consultation, and retest;
- Ongoing accessibility QA: review of new releases or components.
Quote according to scope, complexity, documentation, meetings, and retesting—not simply “price per page.” State how many rounds of questions and retests are included. If the client changes the sample or adds an application area, use a change request.
Boundaries that protect both sides
Never advertise a guaranteed “100% compliant” result. Accessibility is affected by changing content, third-party tools, browser behavior, and future releases. Do not copy an accessibility overlay’s marketing claims into your service. Do not collect disability information from testers without appropriate privacy and consent practices.
If the client needs a formal legal opinion, refer them to qualified counsel. If the audit requires expert testing across several assistive technologies or participation by disabled users, partner with specialists and budget for their work.
A 21-day learning plan
In the first week, learn the four WCAG principles—perceivable, operable, understandable, and robust—and practice navigating sites only by keyboard. In week two, study common issues in forms, focus management, headings, alternative text, contrast, zoom, and responsive layouts. In week three, create a sample audit and ask a developer or accessibility practitioner to critique it.
The goal is not to memorize every criterion. It is to build a repeatable method, know when you are uncertain, and report evidence without exaggeration.