What is WCAG 2.1?
WCAG 2.1 stands for Web Content Accessibility Guidelines 2.1. It is a set of guidelines developed by the Web Accessibility Initiative (WAI) of the World Wide Web Consortium (W3C). These guidelines are designed to make web content more accessible to a wide range of people with disabilities, including those with visual, auditory, cognitive, and motor impairments.WCAG 2.1 builds upon the earlier version, WCAG 2.0, and introduces additional success criteria to address emerging digital accessibility challenges. The goal of WCAG 2.1 is to ensure that websites, web applications, and other digital content are perceivable, operable, understandable, and robust for all users, regardless of their abilities or disabilities.
Key principles of WCAG 2.1 include
Perceivable
Information and user interface components must be presented in a way that users can perceive, regardless of their abilities. This involves providing text alternatives for non-text content, offering captions and other alternatives for multimedia, and ensuring content can be presented in different ways.Operable
User interface components and navigation must be operable by all users. This includes keyboard accessibility, providing sufficient time for users to read and interact with content, avoiding content that could cause seizures or physical discomfort, and designing navigation that is easily understandable.Understandable
Information and operation of the user interface must be clear and straightforward. Users should be able to understand and navigate the content easily. This involves readable and predictable text, consistent navigation, and input assistance.Robust
Content must be robust enough to be reliably interpreted by a wide variety of user agents, including assistive technologies. This helps ensure long-term compatibility with evolving technologies.WCAG internationally
While WCAG itself is not a law, its guidelines are often referenced and adopted by various countries and regions in their accessibility-related legislation and standards. The specific laws and regulations that incorporate WCAG 2.1 can vary depending on the jurisdiction. Here are some examples:United States
In the United States, the Americans with Disabilities Act (ADA) and Section 508 of the Rehabilitation Act are key legal frameworks that address digital accessibility. Section 508 specifically references WCAG standards for federal agencies.European Union
The European Accessibility Act (EAA) is a directive of the European Union that aims to improve the accessibility of products and services, including digital services. While WCAG is not explicitly mentioned, its principles align with the EAA's objectives.Canada
In Canada, the Accessibility for Ontarians with Disabilities Act (AODA) references WCAG 2.0 Level AA for web accessibility compliance. Additionally, the Canadian Human Rights Act emphasizes the importance of digital accessibility.Australia
The Disability Discrimination Act (DDA) in Australia mandates that organizations ensure their online content is accessible. While it doesn't specifically mention WCAG 2.1, adherence to its guidelines is considered good practice.United Kingdom
In the UK, the Equality Act requires organizations to make reasonable adjustments to ensure accessibility. Public sector bodies are also required to meet accessibility standards, and the UK government has adopted WCAG 2.1 as the standard for public sector websites and apps. It's important to check the specific accessibility laws and standards in your jurisdiction to understand the requirements that apply to your digital content. Many countries around the world recognize the importance of digital accessibility and may refer to WCAG guidelines in their legal frameworks.Behind the scenes of WCAG 2.1 recommendations
WCAG provides principles and guidelines that developers can apply across different technologies to make their content accessible. There are some key considerations related to code that align with the principles of accessibility.Semantics
Use HTML (Hypertext Markup Language) and other markup languages in a way that provides the necessary structure and semantics to assistive technologies and users.Use appropriate HTML elements (e.g., <h1> to <h6> for headings) to convey document structure.Text Alternatives
Provide text alternatives for non-text content, such as images, using the `alt` attribute in HTML.Ensure that text alternatives convey the same information as the non-text content.Keyboard Accessibility
Ensure that all functionality is operable through a keyboard interface.Avoid relying solely on mouse events; make interactive elements keyboard accessible.Focus Management
Ensure that focus is visible and operable for keyboard users.Use semantic HTML to maintain a logical tab order and manage focus appropriately.Contrast and Readability
Ensure sufficient color contrast for text and interactive elements to improve readability.Use readable font sizes and provide options for users to adjust text size.Forms and Controls
Use accessible form controls and provide clear instructions.Ensure that form controls have associated labels and are programmatically linked.Adaptability and Responsiveness
Design content that is adaptable and responsive to different devices and screen sizes.Test and optimize the experience for users with disabilities across various devices.Error Handling
Provide clear error messages and suggestions for form validation errors.Ensure that users can identify, understand, and correct errors.Aria Roles and Attributes
Use ARIA (Accessible Rich Internet Applications) roles and attributes to enhance the accessibility of dynamic content.Apply ARIA landmarks to identify regions of a page.Testing and Validation
Conduct accessibility testing using tools and manual testing to identify and address issues.Validate code against accessibility standards, including WCAG.Note that WCAG is technology-agnostic, meaning its principles can be applied to various technologies, including HTML, CSS, JavaScript, and others. The goal is to create a more inclusive digital experience regardless of the underlying technologies used. Developers should follow best practices, use semantic HTML, and consider accessibility throughout the development process.
Accessibility as a way not a goal
While not a law itself, WCAG is often referenced in legal frameworks and regulations worldwide. It is an internationally recognised standard and is widely adopted to guide the development and evaluation of accessible digital content. It provides a comprehensive framework for creating a more inclusive online environment.WCAG 2.1 emphasises principles that contribute to creating digital content that is accessible to a diverse audience, including people with disabilities. This aligns with the concept of inclusive design, ensuring that websites and applications are usable by everyone, regardless of their abilities. WCAG adopts a user-centered approach. Therefore, understanding user needs, their physical and cognitive limitations, along with preferences and behaviours to create interfaces and content that are intuitive, enjoyable, and easy to use are strongly recommended.
Accessibility as company’s practices
Treat accessibility as a continuous improvement effort. Regularly monitor and conduct periodic audits to ensure ongoing accessibility compliance. Providing a training and raising awareness among development and design teams about accessibility best practices and standards shall be incorporated into company’s basis. Consider establishing or updating an accessibility policy, outlining your commitment and steps for inclusivity. You can also document changes for future reference and organisational transparency. Accessibility is a continuous journey, requiring sustained efforts to create an inclusive digital experience for all users.Our mission in Accessibility House is to help keep businesses accessibility compliant continuously. That’s we not only make changes in the code, but also provide documentation on accessibility-sensitive areas, that need to be taken care about by your development team. For fast paced companies, we’re ready to join you in the process of building the software, so all of us will do their job with highest efficiency.
