Back to index

Comp Accessibility Checklist

This accessibility evaluation was conducted using the WCAG 2.0 AA standard. All criteria that were deemed relevant for this evaluation have been documented below. The table also shows how many occurences of each

# WCAG Short Name Recommendations Occurences
1 1.1.1 Active Images Graphics or images that are controls or accept user input provide a description of their function, rather than their visual representation.  
2 1.1.1 Informational Images Informative graphics and images presented to the user have a text alternative serving an equivalent purpose.  
3 1.1.1 Formatting or Decorative Images Purely decorative graphics or images or images used for visual formatting of content are implemented in a way that allows screen readers and other assistive technologies to ignore them.  
4 1.2.1 Prerecorded Audio-only and Video-only Content Except when the audio or video is an alternative for text and is clearly labeled as such, an equivalent text alternative is provided for prerecorded audio-only or video-only content.  
5 1.2.2 Captions (pre-recorded) Except when the media is an alternative for text and is clearly labeled as such, closed captions are provided.  
6 1.2.3 Audio Description or Media Alternative (pre-recorded) A descriptive text transcript OR audio description audio track is provided for non-live, web-based video  
7 1.2.4 Captions (live) Synchronized captions are provided for all live multimedia that contains audio (audio-only broadcasts, web casts, video conferences, Flash animations, etc.)  
8 1.2.5 Audio Description (pre-recorded) Audio descriptions are provided for all video content in synchronized media.  
9 1.3.1 Info and Relationships: Overall Structure Information, structure, and relationships conveyed through presentation are available in text or can be handled in different, reliable ways by assistive technologies.  
10 1.3.1 Info and Relationships: Section Headings The structure of section headings is marked up using the appropriate semantic elements according to their meaning, not because of the way they are visually rendered.  
11 1.3.1 Info and Relationships: Forms The structure of forms is marked up using the appropriate semantic elements according to their meaning, not because of the way they are visually rendered.  
12 1.3.1 Info and Relationships: Data Tables The structure of data tables is marked up using the appropriate semantic elements according to their meaning, not because of the way they are visually rendered.  
13 1.3.1 Info and Relationships: Lists The structure of lists is marked up using the appropriate semantic elements according to their meaning, not because of the way they are visually rendered.  
14 1.3.2 Meaningful Sequence When the sequence in which content is presented affects it’s meaning, a correct reading sequence can be reliably determined by assistive technologies.  
15 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.  
16 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.  
17 1.4.2 Audio Control A mechanism is provided to stop, pause, mute, or adjust volume for audio that automatically plays on a page for more than 3 seconds.  
18 1.4.3 Color Contrast The visual presentation of text and images of text has a contrast ratio of at least 4.5 to 1 except for large text, incidental and logotypes. Large text has a contrast ratio of at least 3 to 1.  
19 1.4.5 No Images of Text If the same visual presentation can be made using text alone, an image is not used to present that text  
20 2.1.1 Keyboard Navigation All functionalities of the content are fully operable using only a keyboard.  
21 2.4.1 Bypass Blocks A mechanism is available to bypass blocks of content such as headers and navigation menus that are repeated on multiple Web pages.  
22 2.4.3 Focus Order If a Web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable elements receive focus in an order that preserves meaning and operability.  
23 2.4.4 Link Purpose The purpose of each link (or form image button or image map hotspot) can be determined from the link text alone, or from the link text and the context (e.g., surrounding paragraph, list item, table cell, or table headers).  
24 2.4.5 Multiple Options More than one option is available to locate a Web page within a set of pages, except where the page is the result of, or a step in, a process.  
25 2.4.6 Headings and Labels Page headings and labels for form and interactive controls are informative.  
26 2.4.7 Focus Visible Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is clearly visible.  
27 3.2.1 On Input When a user inputs information or interacts with a control, it does not result in a substantial change to the page, the spawning of a pop-up window, an additional change of keyboard focus, or any other change that could confuse or disorient the user unless the user is informed of the change ahead of time.  
28 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 users initiate a change.  
29 3.2.4 Consistent Identification Components that have the same functionality within a set of Web pages are identified consistently throughout all Web pages where they appear.  
30 3.3.1 Error Identification Form validation cues and errors (client-side or server-side) alert users to errors in an efficient, intuitive, and accessible manner. The error is clearly identified, quick access to the problematic element is provided, and user is allowed to easily fix the error and resubmit the form.  
31 3.3.2 Labels or Instructions Sufficient labels, cues, and instructions for required interactive elements are provided via instructions, examples, properly positioned form labels, and/or fieldsets/legends.  
32 4.1.2 Name, Role, Value For all user interface components, the name and role can be programmatically determined, states, properties, and values that can be set by the user can be programmatically set and notification of changes to these items is available to user agents, including assistive technologies.