Web Content Accessibility Guidelines (WCAG) 2.1 AA are the technical standards required of public institutions through new digital accessibility regulations. They are widely accepted and have been developed by experts through intense research and a lengthy detailed process.
There are four guiding principles for accessible web design within WCAG 2.1: perceivable, operable, understandable and robust. Deeper within those four guiding principles are Success Criteria for conformance with the guidelines; A (lowest), AA, and AAA (highest).
WCAG 2.1 A and AA will be an official procedure to meet the OSU Digital Accessibility Policy at some point. This does not mean that you should not try to achieve AAA level of conformance where possible, only that the first two levels; A and AA are required by policy.
Within this website you will find help on these success criteria, and they are broken down as much as possible by type of content that you'll be using on your websites. Since this site is meant as education and tools for the broader OSU community, including the many of us without technical expertise, this site is geared more towards these individuals. Not all success criteria are found within the individual pages on this site, since in many instances the offices with technical expertise and responsibilities control many of the very technical success criteria within theme/template design. If you are a unit that does not utilize those offices services and have your own separate theme/template, you are encouraged to use standard themes/templates, as they can help you not only conform to OSU Brand Guidelines, but they can help make certain your site is also as accessible as possible and receives updates on a frequent basis.
WCAG 2.1 A & AA Success Criteria
Most of the following success criteria are referenced within the pages on this website. In addition to these points, the official WCAG 2.1 website gives us a lot of educational tools to help guide us. You will find links within each specific success criteria that will help guide you in understanding why the particular success criteria is important and how to meet each success criteria.
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, except for [some exceptions]. (Level A)
1.2.1 Audio-only and Video-only (Prerecorded): For prerecorded audio-only and prerecorded video-only media, the following are true, except when the audio or video is a media alternative for text and is clearly labeled as such: (Level A)
- Prerecorded Audio-only: An alternative for time-based media is provided that presents equivalent information for prerecorded audio-only content.
- Prerecorded Video-only: Either an alternative for time-based media or an audio track is provided that presents equivalent information for prerecorded video-only content.
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. (Level A)
1.2.3 Audio Description or Media Alternative (Prerecorded): An alternative for time-based media or audio description of the prerecorded video content is provided for synchronized media, except when the media is a media alternative for text and is clearly labeled as such. (Level A)
1.2.4 Captions (Live): Captions are provided for all live audio content in synchronized media. (Level AA)
1.2.5 Audio Description (Prerecorded): Audio description is provided for all prerecorded video content in synchronized media. (Level AA)
1.3.1 Info and Relationships: Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. (Level A)
1.3.2 Meaningful Sequence: When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined. (Level A)
1.3.3 Sensory Characteristics: Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, size, visual location, orientation, or sound. (Level A)
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. (Level AA)
1.3.5 Identify Input Purpose: The purpose of each input field collecting information about the user can be programmatically determined. (Level AA)
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. (Level A)
1.4.2 Audio Control: If any audio on a Web page plays automatically for more than 3 seconds, either a mechanism is available to pause or stop the audio, or a mechanism is available to control audio volume independently from the overall system volume level. (Level A)
1.4.3 Contrast (Minimum): The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, except for [exceptions]. (Level AA)
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. (Level AA)
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 (with exceptions). (Level AA)
1.4.10 Reflow: Content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions for [certain content]. (Level AA)
1.4.11 Non-text Contrast: The visual presentation of the following have a contrast ratio of at least 3:1 against adjacent color(s): user interface components, graphical objects. (Level AA)
1.4.12 Text Spacing: In content implemented using markup languages that support [certain] text style properties, no loss of content or functionality occurs by setting [certain properties]. (Level AA)
1.4.13 Content on Hover or Focus: Where receiving and then removing pointer hover or keyboard focus triggers additional content to become visible and then hidden, [certain conditions must be met]. (Level AA)
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. (Level A)
2.1.2 No Keyboard Trap: If the 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. (Level A)
2.1.4 Character Key Shortcuts: If a keyboard shortcut is implemented in content using only letter (including upper- and lower-case letters), punctuation, number, or symbol characters, then at least one of the following is true: a mechanism is available to turn off the shortcut, a mechanism is available to remap the shortcut, the keyboard shortcut is only active when focused. (Level A)
2.2.1 Timing Adjustable: For each time limit that is set by the content, [the user has a mechanism to control the timing unless it is essential or longer than 20 hours]. (Level A)
2.2.2 Pause, Stop, Hide: For moving, blinking, scrolling, or auto-updating information [unless essential, the user has a mechanism to control any content that starts automatically, is presented in parallel with other content, and lasts more than five seconds]. (Level A)
2.3.1 Three Flashes or Below Threshold: Web pages do not contain anything that flashes more than three times in any one second period, or the flash is below the general flash and red flash thresholds. (Level A)
2.4.1 Bypass Blocks: A mechanism is available to bypass blocks of content that are repeated on multiple Web pages. (Level A)
2.4.2 Page Titled: Web pages have titles that describe topic or purpose. (Level A)
2.4.3 Focus Order: If a web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable compenents receive focus in an order that preserves meaning and operability. (Level A)
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. (Level A)
2.4.5 Multiple Ways: More than one way is available to locate a web page within a set of web pages except where the web page is the result of, or a step in, a process. (Level AA)
2.4.6 Headings and Labels: Headings and labels describe topic or purpose. (Level AA)
2.4.7 Focus Visible: Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible. (Level AA)
2.5.1 Pointer Gestures: All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture, unless a multipoint or path-based gesture is essential. (Level A)
2.5.2 Pointer Cancellation: For functionality that can be operated using a single pointer, at least one of the following is true; no down-event, abort or undo is available, up reversal, or completing the down-event is essential. (Level A)
2.5.3 Label in Name: For user interface components with labels that include text or images of text, the name contains the text that is presented visually. (Level A)
2.5.4 Motion Actuation: Functionality that can be operated by device motion or user motion can also be operated by user interface components and responding to the motion can be disabled to prevent accidental actuation [with certain exceptions]. (Level A)
3.1.1 Language of Page: The default human language of each Web page can be programmatically determined. (Level A)
3.1.2 Language of Parts: The human language of each passage or phrase in the content can be programmatically determined except for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text. (Level AA)
3.2.1 On Focus: When any user interface component receives focus, it does not initiate a change of context. (Level A)
3.2.2 On Input: Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component. (Level A)
3.2.3 Consistent Navigation: Navigational mechanisms that are repeated on multiple Web pages within a set of Web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user. (Level AA)
3.2.4 Consistent Identification: Components that have the same functionality within a set of web pages are identified consistently. (Level AA)
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. (Level A)
3.3.2 Labels or Instructions: Labels or instructions are provided when content requires user input. (Level A)
3.3.3 Error Suggestion: If an input error is automatically detected and suggestions for correction are known, then the suggestions are provided to the user, unless it would jeopardize the security or purpose of the content. (Level AA)
3.3.4: Error Prevention (Legal, Financial, Data): For web pages that cause legal commitments or financial transactions for the user to occur, that modify or delete user-controllable data in data storage systems, or that submit user test responses [submissions are reversible, checked for errors, or confirmation is provided before finalizing the submission]. (Level AA)
4.1.1 Parsing: In content implemented using markup languages elements have complete start and end tags, elements are nested according to specifications, elements do not contain duplicate attributes, and any IDs are unique, except where the specifications allow these features. (Level A)
4.1.2 Name, Role, Value: For all user interface components...the name and role can be programmatically determined.... (Level A)
4.1.3 Status Messages: In content implemented using markup languages, status messages can be programmatically determined through role or properties such that they can be presented to the user by assistive technologies without receiving focus. (Level AA)