Web Accessibility and Standards

Web accessibility ensures that websites and web applications can be perceived, operated, and understood by people with disabilities, guided by standards such as the Web Content Accessibility Guidelines.

Definition

Web accessibility is the practice of designing and coding web content so that it can be used by people with disabilities, typically by conforming to standardized guidelines that specify requirements for content being perceivable, operable, understandable, and robust.

Scope

This topic covers the standards and practices for accessible web content: the principles and conformance levels of the Web Content Accessibility Guidelines, techniques such as text alternatives, keyboard operability, sufficient contrast, and semantic structure, and the policy context that mandates accessibility. It does not cover the assistive technologies that consume accessible content, treated separately, nor general inclusive design philosophy, treated under universal and inclusive design.

Core questions

• What principles and conformance levels does WCAG define?
• What techniques make web content perceivable and operable for disabled users?
• How are accessibility requirements enforced through policy and law?
• How are accessibility and usability related but distinct?

Key concepts

• Web Content Accessibility Guidelines (WCAG)
• perceivable, operable, understandable, robust
• conformance levels A, AA, AAA
• text alternatives (alt text)
• keyboard accessibility
• colour contrast
• semantic markup and ARIA
• accessibility policy and law

Key theories

POUR principles of WCAG

The Web Content Accessibility Guidelines organize requirements under four principles, content must be perceivable, operable, understandable, and robust, with testable success criteria at conformance levels A, AA, and AAA.

Accessibility through process and policy

Achieving and sustaining accessibility requires embedding it into development processes and supporting it with organizational policy and law, not just one-time fixes.

Accessibility and usability overlap

Empirical work shows accessibility and usability problems overlap substantially: many barriers for disabled users also impede others, and meeting guidelines does not automatically guarantee a usable experience.

Clinical relevance

Web accessibility lets people with visual, motor, hearing, and cognitive disabilities use online services that are central to daily life, including government, banking, education, and health information; conformance to standards such as WCAG is often a legal requirement and a basis for procurement.

History

The W3C launched the Web Accessibility Initiative in the late 1990s and published WCAG 1.0 in 1999, followed by WCAG 2.0 in 2008 and 2.1 in 2018. Legislation in many jurisdictions adopted these guidelines, and research, such as Petrie and Kheir's study, clarified the relationship between accessibility conformance and real usability for disabled users.

Key figures

• Jonathan Lazar
• Helen Petrie
• Ben Shneiderman

Seminal works

• wcag21
• lazar2015
• petrie2007

Frequently asked questions

What are the WCAG conformance levels?

WCAG defines three levels: A is the minimum, AA addresses the major and common barriers and is the level most laws and policies target, and AAA is the highest and not always achievable for all content. Most organizations aim for AA conformance as a practical and widely accepted target.

Does meeting WCAG guarantee a site is usable for disabled people?

Not entirely. Meeting WCAG removes many technical barriers and is essential, but a site can conform yet still be confusing or awkward to use. Real usability for disabled users is best confirmed by testing with people who use assistive technologies, alongside guideline conformance.