-
Home
Accessibility Audit
Back to the Accessibility statement page
1. Perceivable
Information and user interface components must be presentable to users in ways they can perceive.
1.1 Text Alternatives
Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language.
1.1.1 Non-text Content
| Description |
Pages |
Errors |
Ref(s) |
| Providing text alternatives for the area elements of image maps |
0 |
0 |
H24 |
| Providing link text that describes the purpose of a link for anchor elements |
0 |
0 |
H30 |
| Using alt attributes on img elements |
1 |
1 |
H37 |
| Using null alt text and no title attribute on img elements for images that Assistive Technology should ignore |
0 |
0 |
H67 |
| Using alt attributes on images used as submit buttons |
0 |
0 |
H36 |
| Combining adjacent image and text links for the same resource |
0 |
0 |
H2 |
| Using the body of the object element |
0 |
0 |
H53 |
| Providing link text that describes the purpose of a link for anchor elements |
0 |
0 |
H35 |
1.3 Adaptable
Create content that can be presented in different ways (for example simpler layout) without losing information or structure.
1.3.1 Info and Relationships
| Description |
Pages |
Errors |
Ref(s) |
| Using semantic markup to mark emphasized or special text |
7 |
49 |
H49 |
| Using the scope attribute to associate header cells and data cells in data tables |
0 |
0 |
H63 |
| Using id and headers attributes to associate data cells with header cells in data tables |
0 |
0 |
H43 |
- Using id and headers attributes to associate data cells with header cells in data tables
- Using the scope attribute to associate header cells and data cells in data tables
|
0 |
0 |
H43 H63 |
| Using the summary attribute of the table element to give an overview of data tables |
0 |
0 |
H73 |
| Using caption elements to associate data table captions with data tables |
0 |
0 |
H39 |
- Using caption elements to associate data table captions with data tables
- Using the summary attribute of the table element to give an overview of data tables
|
0 |
0 |
H39 H73 |
| Providing a description for groups of form controls using fieldset and legend elements |
0 |
0 |
H71 |
| Using h1-h6 to identify headings |
0 |
0 |
H42 |
| Failure of Success Criterion 1.3.1 due to the use of role presentation on content which conveys semantic information |
0 |
0 |
F92 |
| Using label elements to associate text labels with form controls |
0 |
0 |
H44 |
| Failure of Success Criterion 4.1.2 due to a user interface control not having a programmatically determined name |
115 |
115 |
F68 |
1.4 Distinguishable
Make it easier for users to see and hear content including separating foreground from background.
1.4.3 Contrast (Minimum)
| Description |
Pages |
Errors |
Ref(s) |
| Ensuring that a contrast ratio of at least 3:1 exists between text (and images of text) and background behind the text |
0 |
0 |
G145 |
| Ensuring that a contrast ratio of at least 4.5:1 exists between text (and images of text) and background behind the text |
115 |
460 |
G18 |
2. Operable
User interface components and navigation must be operable.
2.2 Enough Time
Provide users enough time to read and use content.
2.2.1 Timing Adjustable
| Description |
Pages |
Errors |
Ref(s) |
| Failure of Success Criterion 2.2.1 and 2.2.4 due to using meta redirect with a time limit |
0 |
0 |
F40 |
| Failure of Success Criterion 2.2.1, 2.2.4, and 3.2.5 due to using meta refresh to reload the page |
0 |
0 |
F41 |
2.2.2 Pause, Stop, Hide
| Description |
Pages |
Errors |
Ref(s) |
| Failure of Success Criterion 2.2.2 due to using the blink element |
0 |
0 |
F47 |
2.4 Navigable
Provide ways to help users navigate, find content, and determine where they are.
2.4.1 Bypass Blocks
| Description |
Pages |
Errors |
Ref(s) |
| Using the title attribute of the frame and iframe elements |
0 |
0 |
H64 |
- Adding a link at the top of each page that goes directly to the main content area
- Adding a link at the beginning of a block of repeated content to go to the end of the block
- Adding links at the top of the page to each area of the content
|
1 |
7 |
G1 G123 G124 |
2.4.2 Page Titled
| Description |
Pages |
Errors |
Ref(s) |
| Providing a title using the title element |
0 |
0 |
H25 |
2.4.8 Location
| Description |
Pages |
Errors |
Ref(s) |
| Using the link element and navigation tools |
0 |
0 |
H59 |
3. Understandable
Information and the operation of the user interface must be understandable.
3.1 Readable
Make text content readable and understandable.
3.1.1 Language of Page
| Description |
Pages |
Errors |
Ref(s) |
| Using the language attribute on the HTML element |
0 |
0 |
H57 |
3.1.2 Language of Parts
| Description |
Pages |
Errors |
Ref(s) |
| Using language attributes to identify changes in the human language |
0 |
0 |
H58 |
3.1.6 Pronunciation
| Description |
Pages |
Errors |
Ref(s) |
| Using the ruby element |
0 |
0 |
H62 |
3.2 Predictable
Make Web pages appear and operate in predictable ways.
3.2.2 On Input
| Description |
Pages |
Errors |
Ref(s) |
| Providing submit buttons |
115 |
115 |
H32 |
4. Robust
Content must be robust enough that it can be interpreted by a wide variety of user agents, including assistive technologies.
4.1 Compatibel
Maximize compatibility with current and future user agents, including assistive technologies.
4.1.1 Parsing
| Description |
Pages |
Errors |
Ref(s) |
| Failure of Success Criterion 4.1.1 due to duplicate values of type ID |
0 |
0 |
F77 |
4.1.2 Name, Role, Value
| Description |
Pages |
Errors |
Ref(s) |
| Using HTML form controls and links |
116 |
119 |
H91 |