Baseline Tests

Keyboard navigation
Keyboard access and control must be available for all interactive interface components and frames that can be accessed or controlled with a mouse. Where non-standard keyboard commands are employed, notify users of the existence and use of Alternate keyboard commands through the interface, application help, and/or documentation.
Focus (visible)
There must be a visible indication of the currently focused interactive component.
Focus (order)
When the sequence of interface components has meaning or requires an order of operation, the focus/TAB order must logically flow with the application/content.
Focus (Revealing hidden content)
Components that reveal hidden content (dialog boxes, light boxes, popups, content accordions, drop-down menus etc.) must either (i) shift focus to the content they reveal, or (ii) the component must describe that a change to the content will occur if selected.
Skip links
A method must be provided to skip blocks of repeated content or links on pages, allowing a user to move directly to page-specific content.
Multi-state components
Components that can change their state must reveal their current state and function to Assistive Technology.
Images
All images must have associated text describing the purpose and/or function of the image. Decorative images do not require a description.
Color (meaning)
Color must not be the only means of conveying information, indicating an action, prompting a response, or indicating status. Information conveyed through color must also be provided in text displayed on the screen or by visual differentiation.
Color (contrast)
There must be contrasting colors/shades at a ratio of 4.5:1 for discerning between background and foreground content.
Flashing (reserved)
Sections(s) of the screen should not flash at or above 3Hz.
Forms (associated instructions)
Labels, instructions, directions and cues necessary to complete a form must be programmatically associated with their respective input control.
Page Titles
Programmatically identify Page Titles.
Data Tables (headers)
Column and row header cells of data tables must be programmatically identified.
Data Tables (cell-header association)
Data cells on complex tables must include markup to associate the data cell with the correct header.
Headings
Headings must be programmatically identified and must match the visual outline level.
Links and User controls
Links and/or user controls must have meaningful names that describe the unique destination, function, and/or purpose of the control for assistive technology.
Language
A default language must be programmatically identified for each page, and for passages that use a language other than the default. Exceptions: proper names, technical terms, or foreign words that have become part of the vernacular.
Audio (transcripts)
Audio-only content must be accompanied by transcripts.
Video (descriptions)
Video-only content must be accompanied by descriptions.
Synchronized media (captions)
Synchronized media must have captions that are time-synchronized with the dialog and relevant sounds.
Synchronized media (descriptions)
Synchronized media must have audio descriptions that are timesynchronized with the video.
Style-sheet non-dependence
Web pages must be structured so that their reading order is consistent whether they are viewed with or without an associated style sheet. Layout and appearance of the page may change visually, as long as the logical reading order is maintained.
Frames
Frames and iframes must have a meaningful description using the title or name attribute.
Alternate pages
When the primary page/site cannot be made accessible, an Alternative page/site must contain equivalent and up-to-date content.
Time outs
Users of assistive technology must be alerted about a pending time out, and users must be able to request more time to complete their task.
Image maps
Server-side image maps may not be used. Client-side image-maps must be used instead.
Plug-in Links
When public-facing pages utilize content delivered via plugins, or contain downloadable content that must be opened with a separate application, a link to obtain the plug-in and/or application must be provided.
Built-in accessibility features
Operating System (OS) user-configurable accessibility appearance settings and functions must not be disrupted or disabled by the software application.