Non-accessible content
4. The website is not yet fully compliant
-
Perceivable: The element main must not appear as a descendant of the main element.
Screen readers rely on landmarks to tell the user what is the relevant content, and which portions of the page are headers, footers etc. If the landmark appears multiple times, it can confuse the screen readers and therefore confuse users who rely on them.
Accessibility criteria that are not met
- 1.3.1 Information and relations
-
Perceivable: Alt text should not be a meaningless image file name, nor should it be a placeholder
Some images have alt text as "null"
Accessibility criteria that are not met
- 1.1.1 Non-textual content
-
Perceivable: Ensure that text and background colors have enough contrast.
Some users find it hard to read light gray text on a white background, dark gray text on a black background and white text on a red background. Some users have browser defaults set to white text on a black background, so setting one color without setting the others can result in white text on a white background.
Accessibility criteria that are not met
- 1.4.3 Contrast (Minimum)
-
Perceivable: User interface controls must have a contrast ratio of at least 3:1 against adjacent colors.
Without sufficient contrast, users might not see the text or user interface controls.
Accessibility criteria that are not met
- 1.4.11 Non-text Contrast
-
Operable: Several links on a page share the same link text and surrounding context, but go to different destinations.
Screen readers have difficulties understanding the true destination of a link if it doesn't have a unique label or unique context. Appears in places where text is "Read more", "here" and "Open Account"
Accessibility criteria that are not met
- 2.4.4 Link purpose (In Context)
-
Operable: Clickable controls should have an ARIA role.
Some links act as buttons which can confuse users who use screen readers.
Accessibility criteria that are not met
- 2.1.1 Keyboard
-
Operable: Radio buttons with very generic labels need to be enclosed in a fieldset with a legend explaining the label.
Screen reader users have difficulties understanding what the radio button does.
Accessibility criteria that are not met
- 2.4.6 Headings and labels
-
Operable: The CSS outline or border style on this element makes it difficult or impossible to see the link focus outline.
Removing the focus styling makes it impossible for users to tell which element is focused.
Accessibility criteria that are not met
- 2.4.7 Focus Visible
-
Robust: ARIA control has no label.
Screen readers can't voice the label correctly when reading the control.
Accessibility criteria that are not met
- 4.1.2 Name, Role, Value
-
Robust: Clickable controls should be keyboard accessible.
If controls aren't keyboard accessible, keyboard-only users have difficulties navigating the site.
Accessibility criteria that are not met
- 4.1.2 Name, Role, Value
-
Robust: HTML form control has no accessible name.
Screen readers can't voice the label correctly when reading the control.
Accessibility criteria that are not met
- 4.1.2 Name, Role, Value
-
Robust: iframe and frame elements must have a title attribute.
VoiceOver on macOS does not read frame contents automatically, and without a title the user does not know what the frame contains.
Accessibility criteria that are not met
- 4.1.2 Name, Role, Value