Skip to content

Compare methods

Compare source explanations, strengths, limitations and references for up to four methods.

7 results
Criterion Web Accessibility Evaluation Accessibility Audit Universal Design Evaluation
Overview
  • Web accessibility evaluation assesses how well digital content conforms to the Web Content Accessibility Guidelines so that it can be used by people with a wide range of disabilities. WCAG 2.0, published as a W3C Recommendation in 2008 by Caldwell, Cooper, Reid, and Vanderheiden, organizes requirements under four principles—content must be Perceivable, Operable, Understandable, and Robust (POUR)—each broken into testable success criteria graded at conformance levels A, AA, and AAA. A rigorous evaluation combines three complementary methods: automated tools that scan for machine-detectable issues, manual expert inspection against the success criteria, and testing with assistive technologies such as screen readers and keyboard-only navigation. The evaluation determines whether the content satisfies all success criteria up to a target level and yields a conformance claim. Because no single method catches every barrier, the strength of the assessment lies in layering all three.
  • An accessibility audit is a systematic survey of a built environment that measures its features against accessibility standards or codes to identify, classify, and prioritize barriers facing disabled people. The auditor inspects elements along the chain of use—approach and parking, the entrance, internal circulation, sanitary facilities, signage, and controls—taking concrete measurements such as door clear widths, ramp gradients, and reach ranges. These measurements are checked against the criteria in the governing standard, and any element that falls outside the required range is recorded as a barrier. Barriers are then classified by severity and turned into a ranked remediation plan. Framed by the WHO International Classification of Functioning, Disability and Health, the audit treats the physical environment as an environmental factor that can either enable participation or, when it imposes barriers, produce disability.
  • Universal design evaluation appraises products, environments, and systems against the seven principles of universal design so that they are usable by the widest possible range of people without the need for adaptation or specialized design. The framework was codified in 1998 by Molly Follette Story, James Mueller, and Ronald Mace at the Center for Universal Design, who paired each principle with concrete guidelines and performance-measure checklists. Rather than retrofitting accommodations for a presumed average user, the method treats the full spectrum of human ability, age, size, and circumstance as the design target from the outset. Evaluation proceeds by specifying that user range, checking the design against the seven principles, observing diverse users in realistic tasks, and rating conformance principle by principle. The result is a prioritized set of design revisions that move a product toward inclusive, equitable use.
Use and interpretation
  • Use web accessibility evaluation whenever digital content—websites, web applications, documents, or software interfaces—must be usable by disabled people or must meet legal, procurement, or policy requirements that reference WCAG. It is the appropriate method when you need a defensible conformance claim at a stated level (most often Level AA), when remediating an existing product, or when verifying that new development meets accessibility acceptance criteria. The approach assumes you can sample representative pages and states and that you have access to automated tools and assistive technologies for testing. It is less suited to evaluating physical environments (use an accessibility audit), to appraising broad inclusive-design quality beyond conformance (universal design evaluation), or to arranging an individual adjustment for a specific person (reasonable accommodation assessment). Even a perfect conformance result should be complemented by usability testing with disabled users for the most important journeys.
  • Use an accessibility audit when you need to determine, with measurable evidence, how well a physical environment serves disabled people and which barriers to remove first. It is the right method for existing buildings, public spaces, transit facilities, workplaces, and venues that must be checked against an accessibility code or standard, whether to demonstrate compliance, plan capital improvements, or respond to a complaint. The approach depends on physical access to the site and the right measuring tools, and it is most useful when a clear governing standard exists to define the criteria. It is less suited to appraising aspirational inclusiveness beyond code minimums (universal design evaluation fits better), to evaluating digital content (use web accessibility evaluation), or to arranging an adjustment for one specific individual (reasonable accommodation assessment).
  • Use universal design evaluation when you want a single product, space, service, or interface to be usable by the broadest range of people without separate adaptations, and you can characterize that intended user range. It is well suited to early and iterative design review, procurement decisions, and post-occupancy or post-launch appraisal where the seven principles give a shared, structured vocabulary for judging inclusiveness. The method is strongest when you can recruit genuinely diverse users—including disabled people and older adults—to test the design, because lived use exposes barriers that checklists alone miss. It is less appropriate when the relevant standard is a specific legal code (an accessibility audit against that code fits better), when only digital conformance to WCAG is at stake (use web accessibility evaluation), or when individualized adjustment for one person is the goal (reasonable accommodation assessment).
Strengths
  • Tests against a stable, internationally adopted standard with testable success criteria, yielding precise, comparable, and legally referenced conformance claims.
  • Layers automated, manual-expert, and assistive-technology methods so that machine-detectable and judgment-dependent barriers are both caught.
  • Organizes requirements under the intuitive POUR principles, giving teams a shared structure for diagnosing and discussing accessibility.
  • Produces both a conformance determination and a prioritized, evidence-backed remediation list that feeds directly into development.
  • Produces objective, measurement-based evidence of barriers tied to explicit standard criteria, making findings defensible and repeatable.
  • Covers the whole chain of use—approach, entrance, circulation, facilities, signage, controls—so isolated 'accessible' features are not mistaken for an accessible environment.
  • Frames the physical environment through the ICF as an enabling or disabling factor, linking measured features to real participation.
  • Delivers a severity-ranked, cost-aware remediation plan that lets limited budgets remove the most disabling barriers first.
  • Targets the widest range of users from the outset, reducing the need for stigmatizing, costly retrofits and special-case accommodations.
  • Provides a structured, shared vocabulary—the seven principles with concrete guidelines—that makes inclusive-design appraisal systematic rather than impressionistic.
  • Combines expert checklist review with usability testing by diverse users, grounding conformance ratings in observed performance.
  • Yields a per-principle conformance profile that diagnoses exactly where a design succeeds and fails and supports prioritized revision.
Limitations
  • Conformance is technology-conformance, not a guarantee of usability; content can pass every success criterion yet still be hard for disabled users, so user testing remains necessary.
  • Automated tools cover only a minority of success criteria, so over-reliance on scanners produces a false sense of accessibility.
  • Sampling means untested pages and states may harbor barriers the evaluation never sees.
  • Manual judgments (for example, whether alternative text is adequate) vary between evaluators without shared rubrics and experienced reviewers.
  • Conformance to a code is a legal floor, not a guarantee of genuine usability, so an audit can pass an environment that disabled people still find hard to use.
  • Results depend on the chosen standard, which varies by jurisdiction and may lag behind current best practice or omit some impairments.
  • Physical measurement is labor-intensive and captures a snapshot; temporary obstructions, maintenance, and changing use are easily missed.
  • Standards emphasize mobility and sensory access and may under-represent cognitive, neurological, or other access needs.
  • The seven principles are qualitative ideals, so conformance scoring involves evaluator judgment and can vary between assessors without careful rubrics.
  • Truly diverse usability testing is resource-intensive, and shallow recruitment can let the evaluation quietly default to a narrow user base.
  • The principles describe usability but do not encode jurisdiction-specific legal requirements, so conformance does not guarantee regulatory compliance.
  • Trade-offs between principles (for example, low physical effort versus tolerance for error) are not resolved by the framework and require design judgment.
Common pitfalls
  • Treating an automated scan as a complete evaluation, when tools can reliably test only a fraction of WCAG success criteria.
  • Claiming conformance at a level while one or more applicable criteria fail—conformance is all-or-nothing per level, not a percentage.
  • Skipping assistive-technology testing, so content that is technically correct but unusable with a screen reader or keyboard passes undetected.
  • Sampling unrepresentatively—testing only static marketing pages and missing interactive forms, dialogs, and error states where most barriers live.
  • Auditing isolated features rather than the full journey, so a building with an accessible toilet but an inaccessible entrance is wrongly judged compliant.
  • Recording impressions instead of measurements, which undermines the objectivity and defensibility that distinguish an audit from a casual walkthrough.
  • Treating code compliance as the end goal and ignoring usability barriers the standard does not capture.
  • Producing an unranked list of every shortfall without severity and cost weighting, leaving owners unable to act sensibly on limited budgets.
  • Treating the seven principles as a pass/fail checkbox exercise rather than scoring conformance against guidelines and observed use.
  • Specifying an overly narrow user range so the design 'passes' for people who resemble the evaluators while excluding the populations universal design is meant to serve.
  • Skipping usability testing with disabled and older users and relying on expert inspection alone, which misses experiential barriers.
  • Producing a conformance report without prioritized, actionable revisions, so the evaluation never feeds back into the design.
Introduced by
  • Ben Caldwell, Michael Cooper, Loretta Guarino Reid & Gregg Vanderheiden (W3C WCAG Working Group)
  • Center for Universal Design (Story, Mueller & Mace); WHO ICF environmental-factors framework
  • Molly Follette Story, James L. Mueller & Ronald L. Mace (Center for Universal Design)
Year
  • 2008
  • 2001
  • 1998