| The level of detail setting for the report is to show all detail. |
| Checkpoints | Passed | ||
|---|---|---|---|
| Basic Settings | Yes | No | Other |
1.1 / (a) Provide a text equivalent for every non-text element (e.g., via "alt", "longdesc", or in element content). This includes:
images, graphical representations of text (including symbols), image
map regions, animations (e.g., animated GIFs), applets and programmatic
objects, ascii
art, frames, scripts, images used as list bullets, spacers, graphical
buttons, sounds (played with or without user interaction), stand-alone
audio files, audio tracks of video, and video.
|
Yes | ||
7.1 / (j) Until user agents allow users to control flickering, avoid causing the screen to flicker.
Verified by: A.N. Other |
Yes | ||
| 2.1 / (c) Ensure that all information conveyed with color is also available without color, for example from context or markup.
Verified by: A.N. Other |
Yes | ||
6.1 / (d) Organize
documents so they may be read without style sheets. For example, when
an HTML document is rendered without associated style sheets, it must
still be possible to read the document.
Verified by: A.N. Other |
Yes | ||
| Image Maps | Yes | No | Other |
| 1.2 / (e) Provide redundant text links for each active region of a server-side image map.
Verified by: A.N. Other |
N/A | ||
| 9.1 / (f) Provide client-side image maps instead of server-side image maps except where the regions cannot be defined with an available geometric shape. | N/A | ||
| Tables | Yes | No | Other |
5.1 / (g) For data tables, identify row and column headers.
Verified by: A.N. Other |
N/A | ||
5.2 / (h) For
data tables that have two or more logical levels of row or column
headers, use markup to associate data cells and header cells.
Verified by: A.N. Other |
N/A | ||
| Frames, Scripts & Multimedia | Yes | No | Other |
| 12.1 / (i) Title each frame to facilitate frame identification and navigation. | N/A | ||
6.3 / (l),(m) Ensure
that pages are usable when scripts, applets, or other programmatic
objects are turned off or not supported. If this is not possible,
provide equivalent information on an alternative accessible page.
Verified by: A.N. Other |
No | ||
| 1.4 / (b) For
any time-based multimedia presentation (e.g., a movie or animation),
synchronize equivalent alternatives (e.g., captions or auditory
descriptions of the visual track) with the presentation.
Verified by: A.N. Other |
N/A | ||
| 11.4 / (k) If,
after best efforts, you cannot create an accessible page, provide a
link to an alternative page that uses W3C technologies, is accessible,
has equivalent information (or functionality), and is updated as often
as the inaccessible (original) page.
Verified by: A.N. Other |
Yes | ||
| 4.1 Clearly identify changes in the natural language of a document's text and any text equivalents (e.g., captions).
Verified by: A.N. Other |
No | ||
| 14.1 Use the clearest and simplest language appropriate for a site's content.
Verified by: A.N. Other |
Yes | ||
| 1.3 Until
user agents can automatically read aloud the text equivalent of a
visual track, provide an auditory description of the important
information of the visual track of a multimedia presentation.
Verified by: A.N. Other |
N/A | ||
| 6.2 Ensure that equivalents for dynamic content are updated when the dynamic content changes.
Verified by: A.N. Other |
N/A | ||
| Checkpoints | Passed | ||
|---|---|---|---|
| Priority 2 - Basic | Yes | No | Other |
| 2.2 Ensure
that foreground and background color combinations provide sufficient
contrast when viewed by someone having color deficits or when viewed on
a black and white screen.
Verified by: A.N. Other |
Yes | ||
| 3.1 When an appropriate markup language exists, use markup rather than images to convey information.
Verified by: A.N. Other |
No | ||
3.2 Create documents that validate to published formal grammars.
Verified by: A.N. Other |
No | ||
3.3 Use style sheets to control layout and presentation.
Verified by: A.N. Other |
Yes | ||
3.4 Use relative rather than absolute units in markup language attribute values and style sheet property values.
Verified by: A.N. Other |
Yes | ||
3.5 Use header elements to convey document structure and use them according to specification.
Verified by: A.N. Other |
Yes | ||
3.6 Mark up lists and list items properly.
Verified by: A.N. Other |
Yes | ||
3.7 Mark up quotations. Do not use quotation markup for formatting effects such as indentation.
Verified by: A.N. Other |
No | ||
| 6.5 Ensure that dynamic content is accessible or provide an alternative presentation or page. In addition to the rules specified below, refer to the detail of checkpoints 6.3 / (l),(m) and 1.1 / (a) for locations of elements that apply to this checkpoint.
Verified by: A.N. Other |
Yes | ||
| 7.2 Until
user agents allow users to control blinking, avoid causing content to
blink (i.e., change presentation at a regular rate, such as turning on
and off). To assist with visual verification, we recommend that you refer to the detail of checkpoint 7.1 / (j) for locations of elements that apply to this checkpoint. Verified by: A.N. Other |
Yes | ||
7.4 Until user agents provide the ability to stop the refresh, do not create periodically auto-refreshing pages.
Verified by: A.N. Other |
Yes | ||
| 7.5 Until
user agents provide the ability to stop auto-redirect, do not use
markup to redirect pages automatically. Instead, configure the server
to perform redirects. To assist with visual verification, we recommend that you refer to the detail of checkpoint 7.4 for potential violations that apply to this checkpoint. Verified by: A.N. Other |
Yes | ||
| 10.1 Until
user agents allow users to turn off spawned windows, do not cause
pop-ups or other windows to appear and do not change the current window
without informing the user. To assist with visual verification, we recommend that you refer to the detail of checkpoints 6.3 / (l),(m) and 7.4 for locations of elements and potential violations that apply to this checkpoint. Verified by: A.N. Other |
No | ||
| 11.1 Use W3C technologies when they are available and appropriate for a task and use the latest versions when supported.
Verified by: A.N. Other |
Yes | ||
11.2 Avoid deprecated features of W3C technologies.
|
No | ||
| 12.3 Divide large blocks of information into more manageable groups where natural and appropriate.
Verified by: A.N. Other |
Yes | ||
| 13.1 Clearly identify the target of each link. | Yes | ||
13.2 Provide metadata to add semantic information to pages and sites.
|
No | ||
13.3 Provide information about the general layout of a site (e.g., a site map or table of contents).
|
Yes | ||
| 13.4 Use navigation mechanisms in a consistent manner.
Verified by: A.N. Other |
Yes | ||
| Priority 2 - Tables | Yes | No | Other |
5.3 Do
not use tables for layout unless the table makes sense when linearized.
Otherwise, if the table does not make sense, provide an alternative
equivalent (which may be a linearized version).
Verified by: A.N. Other |
Yes | ||
| 5.4 If a table is used for layout, do not use any structural markup for the purpose of visual formatting. To assist with visual verification, we recommend that you refer to the detail of checkpoint 5.3 for locations of elements that apply to this checkpoint. Verified by: A.N. Other |
Yes | ||
| Priority 2 - Frames | Yes | No | Other |
| 12.2 Describe the purpose of frames and how frames relate to each other if it is not obvious by frame titles alone. | N/A | ||
| Priority 2 - Forms | Yes | No | Other |
| 10.2 Until
user agents support explicit associations between labels and form
controls, for all form controls with implicitly associated labels,
ensure that the label is properly positioned.
Verified by: A.N. Other |
N/A | ||
| 12.4 Associate labels explicitly with their controls. | N/A | ||
| Priority 2 - Applets, Objects and Scripts | Yes | No | Other |
| 6.4 For scripts and applets, ensure that event handlers are input device-independent. To assist with visual verification, we recommend that you refer to the detail of checkpoint 6.3 / (l),(m) for locations of elements that apply to this checkpoint. Verified by: A.N. Other |
No | ||
| 7.3 Until user agents allow users to freeze moving content, avoid movement in pages. To assist with visual verification, we recommend that you refer to the detail of checkpoint 7.1 / (j) for locations of elements that apply to this checkpoint. Verified by: A.N. Other |
No | ||
| 8.1 Make programmatic elements such as scripts and applets directly accessible or compatible with assistive technologies. To assist with visual verification, we recommend that you refer to the detail of checkpoint 6.3 / (l),(m) for locations of elements that apply to this checkpoint. Verified by: A.N. Other |
N/A | ||
| 9.2 Ensure that any element that has its own interface can be operated in a device-independent manner. To assist with visual verification, we recommend that you refer to the detail of checkpoint 6.3 / (l),(m) for locations of elements that apply to this checkpoint. Verified by: A.N. Other |
No | ||
| 9.3 For scripts, specify logical event handlers rather than device-dependent event handlers. To assist with visual verification, we recommend that you refer to the detail of checkpoint 6.3 / (l),(m) for locations of elements that apply to this checkpoint. Verified by: A.N. Other |
No | ||
Checkpoint Result Legend: Yes = Passed Automated Verification, No = Failed Automated Verification, Warning = Failed Automated Verification, however, configured not to cause page to fail (Priority 2 or 3 only), N/V = Not selected for verification, N/A = No related elements were found in document (Visual only), No Value = Visual Checkpoint