The Department of Justice (DOJ) has issued a new ruling that updates web accessibility standards to WCAG 2.1, expanding on the previous WCAG 2.0 guidelines¹. These new standards address the needs of an aging population and the widespread use of new devices, introducing criteria aimed at improving accessibility on mobile devices, enhancing readability for low vision users, and supporting users with cognitive disabilities.
Let’s break down the changes between WCAG 2.0 and 2.1 and explore what’s new in this latest version, focusing on the specific requirements and recommendations that enhance web accessibility compliance.
Perceivable
Adaptable
Orientation
Content should work in both portrait and landscape orientations unless essential.
(1.3.4, AA)
Identify Input Purpose
Form fields should be coded so screen readers can identify their purpose.
(1.3.5, AA)
Identify Purpose
Buttons, icons, and page sections should be coded so screen readers can identify them.
(1.3.6, AAA)
Distinguishable
Reflow
Content should be viewable without horizontal/vertical scrolling, except for essential 2D layouts.
(1.4.10, AA)
Non-Text Contrast:
Visual elements must have a contrast ratio of at least 3:1 with their background.
(1.4.11, AA)
Text Spacing
Adjusting text spacing should not cause loss of content or functionality.
(1.4.12, AA)
Content on Hover or Focus
Additional content appearing on hover or focus must be dismissible, hoverable, and persistent.
(1.4.13, AA)
Operable
Keyboard Accessible
Character Key Shortcuts
Allow turning off, remapping, or making keyboard shortcuts active only on focus.
(2.1.4, A)
Enough Time
Timeouts
Alert users if inactivity might cause data loss, unless data is saved for over 20 hours.
(2.2.6, AAA)
Seizure & Physical Reactions
Animation from Interactions
Users should be able to disable motion animations, unless essential.
(2.3.3, AAA)
Input Modalities
Pointer Gestures
Functions using multipoint gestures must also work with a single pointer unless essential.
(2.5.1, AA)
Pointer Cancellation
Functions must meet one of the following: no down-event, abort or undo, up reversal, or essential.
(2.5.2, AA)
Label in Name
The accessible name for UI components must include the visible text.
(2.5.3, AA)
Motion Actuation
Features controllable by motion must also be operable by standard UI components and have a disable option unless essential.
(2.5.4, AA)
Target Size
Clickable areas must be at least 44x44 CSS pixels unless exceptions apply.
(2.5.5, AAA)
Concurrent Input Mechanisms
Allow users to use any input methods unless restricted for essential reasons, security, or user settings.
(2.5.6, AAA)
Robust
Compatible
Status Messages
Status messages should be coded so assistive technologies can recognize and announce them without needing focus.
(4.1.3, AA)
Who This Ruling Affects and By When
This ruling impacts all public sector organizations, including state and local governments, educational institutions, and any entities receiving federal funding. Larger public entities with populations of 50,000 or more must comply by April 24, 2026. Smaller entities with populations under 50,000 have until April 26, 2027, to meet these requirements. Compliance ensures that digital content is accessible to individuals with disabilities, helping organizations avoid potential legal repercussions while providing an inclusive experience for all users².
References
1 U.S. Department of Justice. (2024). Nondiscrimination on the Basis of Disability; Accessibility of Web Information and Services of State and Local Government Entities. Federal Register, 89(78), 24341-24379. Link to the ruling.
2 Accessibility of Web Content and Mobile Apps Provided by State and Local Government Entities: A Small Entity Compliance Guide. ADA.gov. Link to the guide.
Ensure Your Website Meets the Latest Accessibility Standards
Don’t wait until the compliance deadlines are upon you. Take proactive steps to make your website accessible to everyone. PixelMongers is here to help with comprehensive web accessibility audits, remediation services, and site redesigns tailored to meet WCAG 2.1 standards.