List of Accessibility Issues Summary
| FAE Rule | Violations | Message | Class |
|---|---|---|---|
| Check | 1 | Heading content should be concise (usually 65 or fewer characters in length). | Headings |
| Fail | 1 | Every frame element must have a title attribute with content that describes the purpose of the frame. | Frames |
| Fail | 1 | The b element must not be used to bold text content, instead use heading (h1-h6) elements for heading text or the strong element for emphasizing words, phrases or sentences. | Text Styling |
| Fail | 1 | Two or more levels of nesting. Use CSS properties instead of tables and nested tables to visually layout blocks of related content for graphical renderings. | Tables |
| Fail | 2 | The font and center elements must not be used for text styling, instead use structural markup should be used with CSS for styling. | Text Styling |
| Fail | 5 | Each page must have a lang attribute on its html element whose value or initial subtag is a valid two-character language code. | Language Changes |
| Warn | 1 | The words contained in each h1 element should match a subset of the words contained in the title element. Words (%1) in h1 elements should also be in the title element. | Title |
| Warn | 1 | Hidden or empty frames should not be used. | Frames |
| Warn | 1 | Every onClick event handler should be on a focusable element. | Events |
| Warn | 1 | One level of nesting. Use CSS properties instead of tables and nested tables to visually layout blocks of related content for graphical renderings. | Tables |
| Warn | 1 | The character encoding was not specified. | W3C Specifications |
| Warn | 2 | Each map, ul or ol element that precedes the last h1 element and appears to be a navigation bar should be immediately preceded by a heading element, preferably an h2. | Menu and Navigation Bars |
| Warn | 2 | Ensure that links that point to the same HREF use the same link text. | Links |
| Warn | 16 | Avoid using text links that are shorter than four 4 characters in length. | Links |
2.
沒有留言:
張貼留言