Site Report
This tab shows accessibility issues, indicating problems for older users, people with disabilities or accessibility needs. Automated testing cannot detect all accessibility issues, so should be used alongside human testing.
| Level | WCAG 2.1 | Section 508 - 2017 | Key |
|---|
| A |  | | Pages with level A issues are unusable for some people |
|---|
| AA |  | | Pages with level AA issues are very difficult to use |
|---|
| AAA | | |  Pages with level AAA issues can be difficult to use |
|---|
| Priority | Description and URL | Guideline and Line# | Count |
|---|
Level A
9 issues on 2 pages | |
| | Clickable controls should be keyboard accessible. | WCAG 2.1 A F15 Section 508 (2017) A F15 | 1 pages |
|
Add tabindex=0 to allow keyboard users to tab to the control. | | |
| https://www.swc.ac.uk/ | Line 341 497 591 1796 | |
| | Clickable controls should have an ARIA role. | WCAG 2.1 A F54 Section 508 (2017) A F54 | 1 pages |
|
Controls that respond to clicks should be given an ARIA role such as role=button or role=link. | | |
| https://www.swc.ac.uk/ | Line 341 497 591 1796 | |
| | Content inserted with CSS is not read by some screen readers, and not available to people who turn off style sheets. | WCAG 2.1 A F87 Section 508 (2017) A F87 | 1 pages |
|
Move the content from CSS to the HTML page so that all users can see it. Impact on users: - NVDA 2019.2 IE11 Windows 10 Reading: Text inserted by CSS content property not read.
- NVDA 2018.4 IE11 Windows 10 Reading: Text inserted by CSS content property not read.
- NVDA 2017.3 IE11 Windows 10 Reading: Text inserted by CSS content property not read.
- NVDA 2016.2 IE11 Windows 10 Reading: Text inserted by CSS content property not read.
- JAWS 2019.1912.1 IE11 Windows 10 Reading: Text inserted by CSS content property not read.
- JAWS 2018.1811.2 IE11 Windows 10 Reading: Text inserted by CSS content property not read.
- JAWS 18.0.5038 IE11 Windows 10 Reading: Text inserted by CSS content property not read.
- JAWS 17.0.2619 IE11 Windows 10 Reading: Text inserted by CSS content property not read.
| | |
| https://www.swc.ac.uk/siteStyle/swc.min.css?frameX | Line 722 | |
| | Duplicate id - the same ID is used on more than one element. | HTML5 WCAG 2.1 A 4.1.1 Section 508 (2017) A 4.1.1 | 1 pages |
|
| | |
| id=image id=image id=headingLink id=headingLink id=buttonLink
https://www.swc.ac.uk/ | Line 1071 1077 1088 1103 1109
...
| |
| | Link uses general text like 'Click Here' with no surrounding text explaining link purpose. | WCAG 2.1 A F63 Section 508 (2017) A F63 | 1 pages |
|
Screen reader users use text around links to help understand what the link does.
If the link text is very general, and there's no surrounding text, there's no way to work out what the link does.
Either use a descriptive link label (which helps all users) or add an aria-label or aria-describedby to the link (which helps screen reader users). | | |
| Link text:
Go
https://www.swc.ac.uk/ | Line 893 | |
| | The element a must not appear as a descendant of the a element. | HTML5 WCAG 2.1 A 4.1.1 Section 508 (2017) A 4.1.1 | 1 pages |
|
| | |
| https://www.swc.ac.uk/ | Line 1798 | |
| | The interactive element a must not
appear as a descendant of the a element. | HTML5 WCAG 2.1 A 4.1.1 Section 508 (2017) A 4.1.1 | 1 pages |
|
| | |
| https://www.swc.ac.uk/ | Line 1798 | |
| | The visual label must appear in the accessible name of links and controls. | WCAG 2.1 A F96 Section 508 (2017) A F96 | 1 pages |
|
People who use speech control rely on being able to select elements using the visual label displayed on screen.
If this isn't part of the accessible name, they can't select elements by name. | | |
| Visual label: Share to Facebook , Number of shares not in Share to Facebook Facebook , Number of shares More AddThis Share options , Number of shares1.1K not in More AddThis Share options AddThis , Number of shares1.1K
https://www.swc.ac.uk/ | Line 1723 1770 | |
| | Use semantic markup like strong instead of using the CSS font-weight property. | WCAG 2.1 A F2 Section 508 (2017) A F2 | 1 pages |
|
Use the strong element instead of the span element for bold text. | | |
| https://www.swc.ac.uk/ | Line 916 927 938 949 | |
Level AA
1 issues on 1 pages | |
| | The CSS outline or border style on this element makes it difficult or impossible to see the dotted link focus outline. | WCAG 2.1 AA F78 Section 508 (2017) AA F78 | 1 pages |
|
Change the style to avoid obscuring the focus outline around focusable elements.
Using a border or outline style that obscures the focus ring causes problems for keyboard-only users in:
- Chrome (obscures the focus indicator on links, buttons, dropdowns and range controls)
- Firefox (obscures the focus indicator on links)
- Internet Explorer (obscures the focus indicator on links, buttons and range controls)
Internet Explorer does not support the `outline-offset:` property, so using this does not reliably avoid focus outline overlap. | | |
| https://www.swc.ac.uk/App_Themes/swc/css/main.min.css | Line 1342 | |
| Expand all 10 issues | | |