|
Guideline 1. Provide equivalent alternatives to auditory and visual content. |
|
Checkpoint |
Priority |
Conformance |
|
1.1 |
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.
-This is done as a general rule, but with some exceptions. |
1 |
Partial |
|
1.2 |
Provide redundant text links for each active region of a server-side image map. |
1 |
N/A |
|
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. |
1 |
N/A |
|
1.4 |
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. |
1 |
N/A |
|
1.5 |
Until user agents render text equivalents for client-side image map links, provide redundant text links for each active region of a client-side image map. |
3 |
N/A |
|
Guideline 2. Don't rely on color alone. |
|
Checkpoint |
Priority |
Conformance |
|
2.1 |
Ensure that all information conveyed with color is also available without color, for example from context or markup. |
1 |
Yes |
|
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. [Priority 2 for images, Priority 3 for text]. |
2 |
Yes |
|
Guideline 3. Use markup and style sheets and do so properly. |
|
Checkpoint |
Priority |
Conformance |
|
3.1 |
When an appropriate markup language exists, use markup rather than images to convey information. |
2 |
Yes |
|
3.2 |
Create documents that validate to published formal grammars.
-Documents created by EPiServers sample templates follow formal grammars with some exceptions.
See the technical note “Accessibility of EPiServer's Sample Templates” for more details. |
2 |
Partial |
|
3.3 |
Use style sheets to control layout and presentation.
-Layout is generally controlled with style sheets, although some Web controls use attributes to modify layout. |
2 |
Partial |
|
3.4 |
Use relative rather than absolute units in markup language attribute values and style sheet property values.
-Relative units are used for most of the style sheet elements with a few exceptions. The portal templates mainly do not use relative units. |
2 |
Partial |
|
3.5 |
Use header elements to convey document structure and use them according to specification.
-Header elements are used for some of the templates, but not as a general rule. |
2 |
Partial |
|
3.6 |
Mark up lists and list items properly. |
2 |
Yes |
|
3.7 |
Mark up quotations. Do not use quotation markup for formatting effects such as indentation. |
2 |
No |
|
Guideline 4. Clarify natural language usage. |
|
Checkpoint |
Priority |
Conformance |
|
4.1 |
Clearly identify changes in the natural language of a document's text and any text equivalents (e.g., captions). |
1 |
No |
|
4.2 |
Specify the expansion of each abbreviation or acronym in a document where it first occurs. |
3 |
No |
|
4.3 |
Identify the primary natural language of a document. |
3 |
No |
|
Guideline 5. Create tables that transform gracefully. |
|
Checkpoint |
Priority |
Conformance |
|
5.1 |
For data tables, identify row and column headers.
- Column headers are used in some templates, but not as a general rule. |
1 |
Partial |
|
5.2 |
For data tables that have two or more logical levels of row or column headers, use markup to associate data cells and header cells.
-Conformance for normal data tables with up to two logical levels. |
1 |
Partial |
|
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).
-As a general rule tables are not used for layout purposes, but there are some exceptions where tables are used when they should not be. |
2 |
Partial |
|
5.4 |
If a table is used for layout, do not use any structural markup for the purpose of visual formatting. |
2 |
Yes |
|
5.5 |
Provide summaries for tables.
-Some tables specify a summary, but this is not done in general. |
3 |
Partial |
|
5.6 |
Provide abbreviations for header labels. |
3 |
No |
|
Guideline 6. Ensure that pages featuring new technologies transform gracefully. |
|
Checkpoint |
Priority |
Conformance |
|
6.1 |
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. |
1 |
Yes |
|
6.2 |
Ensure that equivalents for dynamic content are updated when the dynamic content changes. |
1 |
Yes |
|
6.3 |
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. |
1 |
No |
|
6.4 |
For scripts and applets, ensure that event handlers are input device-independent.
-As a general rule event handlers are device-independent. The portal templates, however, use drag-and-drop. |
2 |
Partial |
|
6.5 |
Ensure that dynamic content is accessible or provide an alternative presentation or page. |
2 |
No |
|
Guideline 7. Ensure user control of time-sensitive content changes. |
|
Checkpoint |
Priority |
Conformance |
|
7.1 |
Until user agents allow users to control flickering, avoid causing the screen to flicker. |
1 |
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).
- Slide show template uses client-side content updates. |
2 |
Partial |
|
7.3 |
Until user agents allow users to freeze moving content, avoid movement in pages. |
2 |
N/A |
|
7.4 |
Until user agents provide the ability to stop the refresh, do not create periodically auto-refreshing pages. |
2 |
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. |
2 |
Yes |
|
Guideline 8. Ensure direct accessibility of embedded user interfaces. |
|
Checkpoint |
Priority |
Conformance |
|
8.1 |
Make programmatic elements such as scripts and applets directly accessible or compatible with assistive technologies. |
1 |
Not tested |
|
Guideline 9. Design for device-independence. |
|
Checkpoint |
Priority |
Conformance |
|
9.1 |
Provide client-side image maps instead of server-side image maps except where the regions cannot be defined with an available geometric shape. |
1 |
N/A |
|
9.2 |
Ensure that any element that has its own interface can be operated in a device-independent manner. |
2 |
N/A |
|
9.3 |
For scripts, specify logical event handlers rather than device-dependent event handlers.
-As a general rule event handlers are device-independent. The portal templates, however, use drag-and-drop. |
2 |
Partial |
|
9.4 |
Create a logical tab order through links, form controls, and objects. |
3 |
Yes |
|
9.5 |
Provide keyboard shortcuts to important links (including those in client-side image maps), form controls, and groups of form controls. |
3 |
Yes |
|
Guideline 10. Use interim solutions. |
|
Checkpoint |
Priority |
Conformance |
|
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. |
2 |
No |
|
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. |
2 |
Yes |
|
10.3 |
Until user agents (including assistive technologies) render side-by-side text correctly, provide a linear text alternative (on the current page or some other) for all tables that lay out text in parallel, word-wrapped columns. |
3 |
N/A |
|
10.4 |
Until user agents handle empty controls correctly, include default, place-holding characters in edit boxes and text areas. |
3 |
N/A |
|
10.5 |
Until user agents (including assistive technologies) render adjacent links distinctly, include non-link, printable characters (surrounded by spaces) between adjacent links.
-This is done for some templates, but not as a general rule. |
3 |
Partial |
|
Guideline 11. Use W3C technologies and guidelines. |
|
Checkpoint |
Priority |
Conformance |
|
11.1 |
Use W3C technologies when they are available and appropriate for a task and use the latest versions when supported. |
2 |
Yes |
|
11.2 |
Avoid deprecated features of W3C technologies. |
2 |
Yes |
|
11.3 |
Provide information so that users may receive documents according to their preferences (e.g., language, content type, etc.). |
3 |
No |
|
11.4 |
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. |
1 |
N/A |
|
Guideline 12. Provide context and orientation information. |
|
Checkpoint |
Priority |
Conformance |
|
12.1 |
Title each frame to facilitate frame identification and navigation.
- Frames are not generally used. |
1 |
No |
|
12.2 |
Describe the purpose of frames and how frames relate to each other if it is not obvious by frame titles alone.
- Frames are not generally used. |
2 |
No |
|
12.3 |
Divide large blocks of information into more manageable groups where natural and appropriate. |
2 |
N/A |
|
12.4 |
Associate labels explicitly with their controls.
-Some templates specify labels, but not as a general rule. |
2 |
Partial |
|
Guideline 13. Provide clear navigation mechanisms. |
|
Checkpoint |
Priority |
Conformance |
|
13.1 |
Clearly identify the target of each link. |
2 |
Yes |
|
13.2 |
Provide metadata to add semantic information to pages and sites. |
2 |
Yes |
|
13.3 |
Provide information about the general layout of a site (e.g., a site map or table of contents). |
2 |
Yes |
|
13.4 |
Use navigation mechanisms in a consistent manner. |
2 |
Yes |
|
13.5 |
Provide navigation bars to highlight and give access to the navigation mechanism. |
3 |
Yes |
|
13.6 |
Group related links, identify the group (for user agents), and, until user agents do so, provide a way to bypass the group. |
3 |
No |
|
13.7 |
If search functions are provided, enable different types of searches for different skill levels and preferences. |
3 |
Yes |
|
13.8 |
Place distinguishing information at the beginning of headings, paragraphs, lists, etc. |
3 |
N/A |
|
13.9 |
Provide information about document collections (i.e., documents comprising multiple pages.). |
3 |
N/A |
|
13.10 |
Provide a means to skip over multi-line ASCII art. |
3 |
N/A |
|
Guideline 14. Ensure that documents are clear and simple. |
|
Checkpoint |
Priority |
Conformance |
|
14.1 |
Use the clearest and simplest language appropriate for a site's content. |
1 |
N/A |
|
14.2 |
Supplement text with graphic or auditory presentations where they will facilitate comprehension of the page. |
3 |
Yes |
|
14.3 |
Create a style of presentation that is consistent across pages. |
3 |
Yes |