How to Audit a Large Site for Accessibility with Disabled Users

The short answer

Auditing a large site for accessibility with disabled users means treating the audit as a co-design exercise rather than a one-off compliance check. You select a representative sample of journeys or pages, train a diverse panel of disabled participants to observe and record, run structured walkthroughs with support (interpreters, transport, breaks), and convert findings into prioritised, fixable defects with an owner and a review date. Success depends less on covering everything and more on sampling well, recruiting people across impairment groups, making participation genuinely accessible, and feeding results into a formal mechanism such as an accessibility statement or an accessibility passport.

Key takeaways

User-led audits catch barriers that pure technical checks miss, such as a compliant ramp that is slippery or lacks resting points.
You cannot test everything on a large site: pick a representative sample of user journeys or pages and audit those deeply.
Recruit across impairment groups (mobility, vision, hearing, neurodivergence) and budget for interpreters, transport and compensation.
Capture each finding as a discrete, actionable defect with evidence and priority, not as a vague list of improvements.
Pair participatory sessions with a formal instrument: an accessibility passport for campuses or an accessibility statement for websites.
Schedule re-audits with the same participants to verify that fixes actually work, and publish an owner and timeline for each defect.

What a user-led or co-designed audit actually changes

Traditional audits, run by facilities teams or external consultants, tend to check whether a ramp meets the gradient standard or a doorway meets the width requirement. A user-led audit inverts the question: instead of “does this element comply?” it asks “can this person complete the whole journey comfortably, every day?” The User-Led Accessibility Audit Tool developed at Trinity College Dublin shows why this matters: a ramp can pass the legal gradient test yet be unusable for a wheelchair user because the surface is slippery or there is no resting point, and compliance-focused reviews often miss tactile paving, sensory-friendly lighting or handrails on both sides.

At scale, co-designed audits work because people with different impairments see different barriers, and no automated scanner or single expert can reproduce that range. In the Islington public-realm project, twelve disabled residents were trained in an inclusive-design workshop, then walked and wheeled a route designed by accessibility specialists, applying a pan-disability lens they had learned from each other. The result was a richer, more credible picture of the neighbourhood than a consultant report alone, and it changed how the council runs future audits.

Co-design is a complement to compliance, not a replacement: keep the technical benchmark and add lived-experience evidence.
Different impairment groups reveal different barriers, so build a mixed panel rather than a single-user check.
Treat the audit as a repeatable cycle, not a one-off report.

Sample the site before you audit it

A large website can have thousands of pages and a large campus thousands of square metres, so exhaustive coverage is unrealistic. Standards-based evaluation methods therefore select a representative sample: for digital services this means choosing structured and random pages that cover the main templates and user journeys; for physical sites it means choosing a set of “through routes” from public transport or parking to the core destinations.

On a territory, map five to ten end-to-end routes that cover typical scenarios: arrival and parking to the main entrance; entrance to reception and an office or classroom; entrance to a toilet and a canteen; entrance via lift to an upper floor; and an evacuation path. Then identify points that every participant group must check: kerb transitions, sloping paths without handrails, doors without automation, areas of poor contrast or lighting, and high-noise zones. The Trinity audit began with 36 accessible rooms in student accommodation and then extended to academic buildings, using a modular tool that separated standard units such as entrances and pathways from facility-specific ones such as laboratories.

Define the boundary of the audit explicitly: what is in scope, what is out, and why.
Cover the journey, not isolated features: a compliant ramp at the end of an inaccessible route still fails.
Repeat key routes at different times of day and in different weather, since lighting and surface conditions change.

Recruit a diverse panel and remove barriers to participation

The quality of a co-designed audit depends on who can actually take part. Budget explicitly for interpreters (for example British Sign Language), transport, refreshments and recognition of participants' time; the Islington project treated these as essential costs rather than optional extras, and the organisers credited them for the project's success. Recruitment should span mobility, low vision and blindness, hearing, and cognitive or neurodivergent users, because each group perceives a different environment.

Before the first walkthrough, hold a training session so participants understand what to look for, how to record evidence, and what 'lived experience' means in practice. Prepare materials in accessible formats, allow flexible pacing and breaks, and arrange for staff on site to open the rooms being checked. When the Trinity team audited buildings, close cooperation with the estates and facilities team was decisive: staff understood the purpose, helped access spaces, and later used the findings to build a funded five-year accessibility improvement plan.

Recruit through disability organisations and networks, not only through the organisation's own channels.
Make the audit event itself accessible, or you will lose precisely the users you need.
Bring site staff into the process early so they can enable access and later champion fixes.

Design tasks, collect evidence and turn it into a prioritised plan

Structured observation beats informal wandering. Give each participant a short set of real tasks, such as “get from the entrance to the lift and to a specific floor” or “complete this form and submit it”, and ask them to record barriers as they meet them. Evidence should be concrete and self-contained: a photo or video with location, a plain-language description, the impairment group affected and the severity. For digital sites this maps to testing the production service with assistive technology along defined user journeys before it goes to public beta.

After the walkthrough, run a triage session with the site owner. Sort findings by a two-by-two matrix of “critical versus easy to fix” against “costly and phased”, so that blocking barriers on the main route come first and cosmetic improvements second. Publish an owner and a target date for each defect, and put the outcome into a formal instrument such as an accessibility statement for a website or an accessibility passport for a campus, so progress is verifiable rather than verbal.

One finding equals one discrete defect: location, evidence, affected users, severity, owner, deadline.
Prioritise critical user journeys first; push aesthetic issues into later phases.
Re-test with the same participants after fixes to confirm the change works in practice.

Limitations and how to stay honest

Participatory audits have real limits. A small panel cannot represent all 1.3 billion disabled people worldwide, findings are time- and weather-dependent, and participants' views can conflict. Automated tools also have limits: on websites they catch only a fraction of issues, and on physical sites there is no substitute for a person on the route. Treat participatory evidence as one layer alongside automated scanning, expert manual review and compliance benchmarking against standards such as WCAG 2.2 at level AA and the EN 301 549 functional requirements used in public procurement.

For digital public services, regulators expect an audit to check both conformance and real-world assistive-technology performance, and to be reported in an accessibility statement aligned with an evaluation methodology. Note also that rules differ by jurisdiction: what is mandatory in the European Union or the UK may not apply elsewhere, and vice versa. Finally, avoid exaggerated certainty: report what was observed on specific routes on specific days, state the sampling limits, and let the site owner own the final decisions about budget and sequencing.

Combine automated scans, expert review and disabled-user testing; none alone is sufficient.
Separate general guidance from jurisdiction-specific legal advice.
Document sampling limits so the report cannot be mistaken for a guarantee of full conformance.

Put it into practice

Co-design Audit Field Kit: a 10-step run sheet

A reusable protocol that an estates team, product owner or disability service can hand to a working group before the first session. Each step closes a specific risk, from weak sampling to a report with no owner.

Scope the audit: list the routes, pages, buildings and services in scope and state explicitly what is excluded and why.
Build a diverse panel: at least one participant each from mobility, vision, hearing and cognitive or neurodivergent groups.
Confirm logistics: accessible transport, interpreters, refreshments, breaks and a fully accessible venue for briefings.
Run a training session so participants understand the evidence format and what 'lived experience' should capture.
Select the sample: 5-10 end-to-end routes for physical sites, or a structured plus random set of pages for websites.
Secure site access with staff in advance and obtain written confirmation for every room or function to be checked.
Conduct walkthroughs in real conditions during operating hours, at different times and, where possible, in varied weather.
Capture evidence in one table: photo or clip, location, plain-language description, affected users and severity.
Triage findings with the owner using a criticality-and-effort matrix and assign an owner and deadline to each defect.
File results in the formal instrument (accessibility statement or passport) and schedule a re-audit with the same panel.

Questions people ask

How is a user-led accessibility audit different from a technical compliance audit?

A technical audit checks whether an element meets a numeric or textual criterion, such as a ramp gradient, a doorway width or a WCAG success criterion. A user-led audit asks whether a person can actually complete a whole journey comfortably, which is a different question: in the Trinity College Dublin case, a ramp could meet the legal gradient yet be unusable because the surface was slippery or there were no resting points. In practice user-led audits add a layer of lived-experience evidence on top of the compliance benchmark, so findings often describe how multiple individual requirements combine to block a user even when each passes separately.

How many users and which impairment groups do I need for a credible audit?

There is no fixed number, but prioritise breadth over headcount. A workable minimum is one or two people each from mobility (including wheelchair use), vision (blind and low vision), hearing, and cognitive or neurodivergent groups. The Islington project treated twelve disabled residents as a significant and sufficient cohort. Because participants learn from each other, a mixed group tends to find more and confirm findings more reliably than the same number of people from one category. If budget is tight, start with mobility and vision users, who surface most physical barriers, and widen the panel in later audit cycles.

Which accessibility barriers typically escape technical checks but appear in co-designed audits?

Common blind spots include: a ramp that meets the gradient standard but is slippery, lacks resting points or has no handrail on both sides; a doorway of compliant width without automation or with an opening force above a comfortable level; a tactile path that stops short of the entrance; a call button positioned out of reach from a wheelchair; and noisy or low-contrast environments that hinder people with low vision or neurodivergent conditions. These cases share a pattern: each element passes its individual check, but the combined journey is still difficult, which is exactly what a participant walking the route discovers and a checklist cannot.

How do I make an accessibility audit itself accessible to the participants?

Treat the audit event as something that must itself be inclusive, or you will lose the very users you need. Budget early for sign-language interpreters, accessible transport, refreshments and recognition of participants' time; the Islington project cited these as decisive to its success. Prepare briefing materials in accessible formats such as large print, plain language or Braille, allow flexible pacing with rest breaks, and avoid framing the walkthrough as a race. Site staff should be briefed so they can open the rooms being checked and assist access. For digital audits, ensure the testing environment and consent forms are usable with the same assistive technologies you are evaluating.

Does a participatory audit guarantee that a site is fully accessible or legally compliant?

No. A panel of participants represents specific users on specific routes on specific days, so findings are a strong signal, not a universal guarantee. For digital public services, regulators typically expect an audit that checks conformance to a standard such as WCAG 2.2 at level AA together with real performance using assistive technology, and reporting through an accessibility statement. Compliance obligations also differ by jurisdiction, so participatory findings should sit alongside automated scanning, expert manual review and a check against the applicable standard or regulation. Report sampling limits honestly and let the site owner make final decisions about budget and sequencing.

Sources and further reading

Sources were checked when this page was generated. Confirm changing dates, rules and prices with the original publisher.

Creating a truly inclusive educational environment: a case studyEngineers Ireland
London Borough of Islington: Accessibility AuditIMPETUS (EU Horizon citizen-science project)
Accessibility auditsUK Government (Department for Education)
Эксперты «Перспективы» провели аудит доступности в Московском психолого-социальном университетеРООИ «Перспектива»
ПаспортизацияФедеральный ресурсный центр (frcds.ru)
Представитель общественной организации инвалидов участвует в согласовании паспорта доступности объекта социальной инфраструктурыПрокуратура Свердловской области
Новое в законодательстве в сфере цифровой доступностиФедеральный ресурсный центр (frcds.ru)