Web accessibility - Accessibility Standards and Guidelines

Guidelines and Standards for Accessible Web Design Introduction Web accessibility is guided by a comprehensive set of standards and guidelines developed by the World Wide Web Consortium (W3C) and its Web Accessibility Initiative (WAI). These standards ensure that websites and web applications are usable by everyone, including people with disabilities. The guidelines cover not just the websites themselves, but also the tools used to create them and the browsers that display them. Web Content Accessibility Guidelines (WCAG) The Web Content Accessibility Guidelines form the foundation of web accessibility standards. They were first published in 1999 and have been updated multiple times as web technology has evolved. Historical Development and Current Standards The 2008 release of Web Content Accessibility Guidelines 2.0 (often abbreviated as WCAG 2.0) became the definitive standard for accessible website creation. Because of its widespread adoption and comprehensive nature, WCAG 2.0 was formally recognized as an International Organization for Standardization / International Electrotechnical Commission (ISO/IEC) standard, officially designated as ISO/IEC 40500:2012. In 2018, the Web Content Accessibility Guidelines 2.1 extended WCAG 2.0 by adding new success criteria specifically addressing mobile accessibility and the needs of people with low vision. This means that WCAG 2.1 builds upon the previous standard rather than replacing it—it maintains all of WCAG 2.0's requirements and adds additional ones. The Four Foundational Principles WCAG 2.0 and 2.1 organize their requirements around four foundational principles. Websites and web content should be: Perceivable: Information and user interface components must be presented in ways that users can perceive them, regardless of their sensory abilities. For example, images need text descriptions, and videos need captions. Operable: Users must be able to navigate and interact with websites using a keyboard, mouse, voice control, or other input methods. All functionality should be accessible to people who cannot use a mouse. Understandable: Text must be readable and comprehensible, and websites should operate in predictable ways. Users should be able to understand how to use the site and what information is presented. Robust: Websites should work reliably with assistive technologies (such as screen readers) and be compatible across different browsers and devices. This means using proper HTML and following web standards. Success Criteria and Testing WCAG 2.0 and 2.1 include success criteria—testable statements that developers can use to verify whether their website meets the guidelines. These criteria are specific, measurable requirements that eliminate ambiguity about what "accessible" means. For example, rather than saying "images should be accessible," a success criterion might specify "all images must have alternative text that describes the image's content and function." Accessible Rich Internet Applications (ARIA) As modern websites have become more complex with dynamic content, scripts, JavaScript, and Ajax (which update web pages without requiring a full page reload), there's a need for websites to communicate additional information to assistive technologies like screen readers. This is where Accessible Rich Internet Applications (ARIA) comes in. ARIA is a technical specification that adds semantic information to dynamic web content. Semantic information describes the meaning and purpose of content in ways that machines can understand. What ARIA Does ARIA allows authors to add special attributes to HTML code that describe: Component behavior: What an interactive element does (for example, whether a button opens a menu or submits a form) Current states: Whether a checkbox is checked, whether a section is expanded or collapsed Properties: Characteristics of elements that don't change frequently Relationships: How elements relate to each other (for example, which labels belong to which form inputs) By providing this additional context, ARIA helps assistive technologies convey the full picture of what's on the page to users with disabilities. Additional Benefits ARIA also solves practical technical problems in complex web applications. It addresses focus management issues (making sure keyboard users can navigate logically through interactive elements) and resolves problems with tab-index (which controls the keyboard navigation order on a page). These capabilities are particularly important for interactive widgets like dropdown menus, dialog boxes, and data tables. Authoring Tool Accessibility Guidelines While WCAG focuses on the accessibility of websites themselves, the Authoring Tool Accessibility Guidelines address a different problem: ensuring that the tools used to create web content are accessible and produce accessible output. These guidelines contain checkpoints (specific requirements) that address three main areas: Producing accessible output: The tools must help creators build accessible websites—for example, by providing options to add alternative text to images or by enforcing proper HTML structure. Providing accessibility information: The tools should provide creators with information about accessibility, such as alerts about potential accessibility problems or tutorials on creating accessible content. Integrating accessibility features: Accessibility considerations should be built into the overall look and feel of the authoring tool itself, not treated as an afterthought. Importantly, the authoring tool itself must also be accessible to people with disabilities. A web designer who uses a screen reader or keyboard navigation should be able to use the tool effectively. User Agent Accessibility Guidelines User Agents are the applications that display web content—primarily web browsers like Chrome, Firefox, and Safari, but also media players and other software that renders web content. The User Agent Accessibility Guidelines define requirements that ensure these applications provide access to all content. These guidelines establish checkpoints focused on three key areas: User control over content rendering: Users should be able to control how content is displayed, such as increasing font sizes or changing text colors for better readability. User control over the user interface: Users should be able to customize the controls and interface elements of the browser itself to suit their needs. Provision of standard programming interfaces: Browsers must provide standard ways for assistive technologies to access and interact with web content. Supporting Resources To help developers implement these guidelines, the World Wide Web Consortium provides a techniques document that lists concrete, practical methods for meeting each WCAG success criterion. Rather than stating requirements in abstract terms, these techniques provide step-by-step approaches that developers can follow to ensure their websites are accessible.