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: Can all functionality and content be accessed and operated through the use of a keyboard or keyboard interface? (Success Criterion 2.1.1 – Level A)
  • No Keyboard Trap: If keyboard focus can be moved from the main web page content into a component of the page, can the focus also be moved away from the component using only the keyboard? (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: Have you ensured that your website/application does not contain content that flashes? (Success Criterion 2.3.1 – Level A)
  • Bypass Blocks: Is there a way for users to bypass content that is repeated on multiple web pages (e.g., setting controls, navigation areas, user menu, etc.)? (Success Criterion 2.4.1 – Level A)
  • Page Titled: Do all pages on your website have unique descriptive page titles? (Success Criterion 2.4.2 – Level A)
  • Focus Order: If page content is designed to be navigated sequentially, do the focusable parts receive focus in a sequential order that maintains the meaning and operation of the content? (Success Criterion 2.4.3 – Level A)
  • Link Purpose (In Context): Is all link text contextual and provide users with a clear indication of the link destination and content? (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: Have you ensured that user interface components contained within your site or application do not initiate a change of context when they receive focus? (Success Criterion 3.2.1 – Level A)
  • On Input: In your site or application, are there controls (e.g., form fields, radio buttons or checkboxes) that cause an unexpected change in context when answered? If so, are you providing users with notification of changes? (Success Criterion 3.2.2 – Level A)
  • Error Identification: If an input error occurs in your site or 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 site or 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 your site or application code complete and schematically correct according to specifications? For example: are elements nested correctly, free of duplicate attributes, attributes are properly used, and are all IDs unique? (Success Criterion 4.1.1 – Level A)
  • Name, Role, Value: Does your site or application deviate from using standard HTML controls according to the specification? If so, are you ensuring that the name, role and value of any developed custom controls or scripted interface element can be determined and controlled by assistive technology? (Success Criterion 4.1.2 – Level A)