Accessibility Compliance Report
The Equal Access Accessibility Compliance Report (ACR) is based on WCAG 2.1 conformance requirements; however, it is not a comprehensive evaluation of all applicable success criteria found within WCAG 2.1. Only specific criteria have been selected for use in this report.
Selected criteria have been grouped into the following benchmarks to streamline testing results and improve readability:
EVALUATION CRITERIA
-
Keyboard Navigation
The Keyboard Navigation benchmark evaluates how effectively a user can navigate and interact with various elements and components of an interface using only a keyboard. This is tested using common keyboard navigation controls, such as using the TAB and ARROW keys to navigate between interactive elements and using the SPACE and ENTER keys to activate elements such as links, buttons, and select options.
Conformance with this benchmark supports a wide range of disabilities and conditions, such as users with low vision or no vision, users with limited mobility or limited dexterity in their hands or fingers, and users who require alternate input devices or keyboard emulators such as speech input software or on-screen keyboard controls. Accessible keyboard navigation eliminates the need for precision hand movements or gestures that are required of a mouse, trackpad, or touchscreen.
Applicable WCAG 2.1 Success Criteria Criteria Name Criteria Description 2.1.1 Keyboard All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints. 2.1.2 No Keyboard Trap If keyboard focus can be moved to a component of the page using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, the user is advised of the method for moving focus away. 2.4.3 Focus Order If a Web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability. 2.4.7 Focus Visible Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible. -
Headings and Labels
The Headings and Labels benchmark evaluates the use of semantic headings and labels throughout an interface as a means of identifying logical sections and subsections of content, as well as identifying where user input might be required. This is tested by reviewing the underlying markup of the headings and labels that appear on the page to ensure that they can be programmatically identified by assistive technologies, and that any instructions or alerts essential to the completion of any forms or multi-step processes required by the user are described clearly in text and can be perceived by assistive technologies.
Conformance with this benchmark supports sighted users who perceive structure and relationships through visual cues such as headings, which are typically styled to set them apart from surrounding text, and assistive technology users who rely on programmatic headings and labels to effectively navigate between sections of content and input fields, even if the presentation or style of the interface is modified. The ability to reliably identify instructions or input field errors helps all users, especially those with limited vision or cognitive disabilities.
Applicable WCAG 2.1 Success Criteria Criteria Name Criteria Description 2.4.2 Page Titled Web pages have titles that describe topic or purpose. 2.4.6 Headings and Labels Headings and labels describe topic or purpose. 3.3.1 Error Identification If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text. 3.3.2 Labels or Instructions Labels or instructions are provided when content requires user input. -
Multimedia Alternatives
The Multimedia Alternatives benchmark evaluates whether non-text content that relies on visual or auditory senses (such as images or videos) has been given an accessible text alternative (such as image alternative “alt” text or video captions). This is tested by reviewing the type of non-text content used and determining if an accessible text alternative for the content has been provided, either as visible text content or underlying markup, or made available via the use of multimedia player controls.
Conformance with this benchmark supports users that have special sensory needs (such as visual, auditory, or tactile), as providing accessible text alternatives to non-text content allows the information to be rendered in a variety of ways to a variety of different users and assistive technologies. Users who are unable to see or have limited vision can have the text alternative for an image read aloud using synthesized speech, and users who are unable to hear or have limited hearing can reference captions or a text transcript for auditory content.
Applicable WCAG 2.1 Success Criteria Criteria Name Criteria Description 1.1.1 Non-text Content All non-text content that is presented to the user has a text alternative that serves the equivalent purpose. 1.2.1 Audio-only and Video-only (Prerecorded) For prerecorded audio-only and prerecorded video-only media, an alternative for time-based media is provided that presents equivalent information. 1.2.2 Captions (Prerecorded) Captions are provided for all prerecorded audio content in synchronized media, except when the media is a media alternative for text and is clearly labeled as such. 1.4.5 Images of Text If the technologies being used can achieve the visual presentation, text is used to convey information rather than images of text. -
Resize and Reflow
The Resize and Reflow benchmark evaluates how well content in an interface can adapt to user preferences such as text size, text spacing, and screen orientation. This is tested using built-in browser and device settings to modify the presentation of the content within the interface and verifying that any modifications made do not impede readability or render any of the content unusable.
Conformance with this benchmark supports users who require the ability to modify how text and other content is displayed in an interface to read or interact with it, such as users with low vision, users who are dyslexic, and users who require a fixed orientation for their device (such as a mobile device attached to a mount). Text and other content that can be resized and reflows appropriately is also compatible with a wider range of devices and viewports.
Applicable WCAG 2.1 Success Criteria Criteria Name Criteria Description 1.3.4 Orientation Content does not restrict its view and operation to a single display orientation, such as portrait or landscape, unless a specific display orientation is essential. 1.4.4 Resize Text Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality. 1.4.10 Reflow Content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions for: vertical scrolling content at a width equivalent to 320 CSS pixels; horizontal scrolling content at a height equivalent to 256 CSS pixels. 1.4.12 Text Spacing In content implemented using markup languages that support the following text style properties, no loss of content or functionality occurs by setting all of the following and by changing no other style property: line height (line spacing) to at least 1.5 times the font size; spacing following paragraphs to at least 2 times the font size; letter spacing (tracking) to at least 0.12 times the font size; word spacing to at least 0.16 times the font size. -
Contrast and Readability
The Contrast and Readability benchmark evaluates how easily users can read text content and distinguish which elements of an interface are interactive. This is tested by evaluating the contrast of foreground text with its background using built-in browser tools and third-party apps to ensure that it meets sufficient contrast ratio requirements, and evaluating links and other interactive elements of an interface to ensure that they are visually and programmatically distinguishable to the user as interactive.
Conformance with this benchmark supports users with low vision or no vision, as well as users with varying levels of color blindness. Text content and interactive elements with sufficient contrast are easier to read for users with low vision and varying levels of color blindness, and information presented to the user without relying on color alone helps users who cannot perceive differences in color. Text content and interactive elements that meet sufficient contrast requirements also adapt more easily to high-contrast settings common in most browser and device settings. Links and other interactive elements that can be programmatically determined by distinguishable text help users who require assistive technology such as screen readers or voice-input software to navigate.
Applicable WCAG 2.1 Success Criteria Criteria Name Criteria Description 1.4.1 Use of Color Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. 1.4.3 Contrast (Minimum) The visual presentation of text and images of text has a contrast ratio of at least 4.5:1; large-scale text has a contrast ratio of at least 3:1. 1.4.11 Non-text Contrast The visual presentation of user interface components and graphical objects have a contrast ratio of at least 3:1 against adjacent color(s). 2.4.4 Link Purpose (In Context) The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general. -
Screen Reader Compatibility
The Screen Reader Compatibility benchmark evaluates how well the content of an interface accommodates the use of a screen reader, such as JAWS, NVDA, or VoiceOver. This is tested by navigating through the interface with a screen reader, and ensuring that all important information and functions of the interface can be programmatically determined and described correctly to the user. Additional criteria of this benchmark include checking that the interface have provided a mechanism to bypass blocks of content that repeat on multiple pages, such as navigation, and ensuring that any status messages or alerts displayed on the interface can also be programmatically determined and described to the user without receiving focus, such as session timeout warnings.
Conformance with this benchmark supports users that rely on assistive technology such as screen readers or speech input software to navigate and interact with elements of an interface.