Conformance Level A Guidelines

25 Guidelines

  • Non-Text Content: Does your site or application provide text alternatives for images or other non-text content? (Success Criterion 1.1.1 – Level A)
  • Audio-only and Video-only (Prerecorded): Does your site or application provide transcripts for audio only files, and descriptions for what is happening in a video only file? (Success Criterion 1.2.1 – Level A)
  • Captions (Prerecorded): If your site or application has video content, are captions available? (Success Criterion 1.2.2 – Level A)
  • Audio Description or Media Alternative (Prerecorded): Are you providing an optional audio track or text alternative to describe what is happening visually in all video content? (Success Criterion 1.2.3 – Level A)
  • Info and Relationships: Is the information, structure, and relationships of the content on your site or application maintained when being accessed with assistive technology? (Success Criterion 1.3.1 – Level A)
  • Meaningful Sequence: Is the content on your site or application presented in a logical reading order when viewed with assistive technology, an alternate stylesheet, or by keyboard only navigation? (Success Criterion 1.3.2 – Level A)
  • Sensory Characteristics: Are you avoiding using sensory language or sounds as the only way to describe controls or provide directions on how to operate your site or application? (Success Criterion 1.3.3 – Level A)
  • Use of Color: Are you ensuring that color is not the only means of providing information or distinguishing visual content? (Success Criterion 1.4.1 – Level A)
  • Audio Control: Are you making sure audio does not play automatically when a page loads? (Success Criterion 1.4.2 – Level A)
  • Keyboard: Are all website/application controls and content fully operable through a keyboard interface? (Success Criterion 2.1.1 – Level A)
  • No Keyboard Trap: Can keyboard focus be moved into and out of web content and components without getting stuck in keyboard traps? (Success Criterion 2.1.2 – Level A)
  • Timing Adjustable: If web content uses time limits can a user turn off, adjust or extend those time limits? (Success Criterion 2.2.1 – Level A)
  • Pause, Stop, Hide: Can moving, blinking, scrolling or auto-updating content be paused, stopped or hidden by the user? (Success Criterion 2.2.2 – Level A)
  • Three Flashes or Below Threshold: Does any web content flash more than 3 times within a 1 second period, or the flash is below the general flash and red flash thresholds? (Success Criterion 2.3.1 – Level A)
  • Bypass Blocks: Is there a way for users to bypass blocks of content such as setting controls, large navigation areas, etc. that are repeated on multiple web pages? (Success Criterion 2.4.1 – Level A)
  • Page Titled: Does every webpage have it’s own descriptive title? (Success Criterion 2.4.2 – Level A)
  • Focus Order: Do focusable components of the content receive focus in a sequential order that is consistent and preserves meaning? (Success Criterion 2.4.3 – Level A)
  • Link Purpose (In Context): For each link in your web content, does the link text, or surrounding context provide definition of the purpose of the link? (Success Criterion 2.4.4 – Level A)
  • Language of Page: Is the language of each page properly identified in the code for your web site/application? (Success Criterion 3.1.1 – Level A)
  • On Focus: In your website/application, does any component initiate a change of context when it receives focus? (Success Criterion 3.2.1 – Level A)
  • On Input: In your website/application, are their controls that cause an unexpected change in context when modified or activated? (Success Criterion 3.2.2 – Level A)
  • Error Identification: If an input error occurs in your website/application, is the error identified and described to the user in text form? (Success Criterion 3.3.1 – Level A)
  • Labels or Instructions: In your website/application, do input fields have sufficient labeling and instructions describing what input data is expected? (Success Criterion 3.3.2 – Level A)
  • Parsing: To ensure proper parsing, is website/application code complete, according to specifications, nested correctly, free of duplicate attributes, and are all IDs unique? (Success Criterion 4.1.1 – Level A)
  • Name, Role, Value: In your platform/content, are there any interface components that have been developed or scripted internally that may not provide name, role, and value appropriately? (Success Criterion 4.1.2 – Level A)