[Skip navigation links]

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.

LevelWCAG 2.1Section 508 - 2017Key
ALevel A, 8 issuesLevel A, 8 issuesCritical Pages with level A issues are unusable for some people
AALevel AA, 3 issuesLevel AA, 2 issuesVery Important Pages with level AA issues are very difficult to use
AAALevel AAA, 3 issuesLess Important Pages with level AAA issues can be difficult to use
PriorityDescription and URLGuideline and Line#Count

Level A

8 issues on 8 pages

CriticalClickable controls should be keyboard accessible. WCAG 2.1 A F15 Section 508 (2017) A F15 8 pages
Add tabindex=0 to allow keyboard users to tab to the control. 4.1.2
https://s1.eground.org/Line 3828 3854
https://s1.eground.org/search/?type=postLine 1280
https://s1.eground.org/whats-new/Line 1905
https://s1.eground.org/whats-new/posts/40166/Line 3220
This issue was found on another 4 pages. The trial version is limited to showing issues on 4 pages.
CriticalClickable controls should have an ARIA role. WCAG 2.1 A F54 Section 508 (2017) A F54 8 pages
Controls that respond to clicks should be given an ARIA role such as role=button or role=link. 2.1.1
https://s1.eground.org/Line 3828 3854
https://s1.eground.org/search/?type=postLine 1280
https://s1.eground.org/whats-new/Line 1905
https://s1.eground.org/whats-new/posts/40166/Line 3220
This issue was found on another 4 pages. The trial version is limited to showing issues on 4 pages.
CriticalEach a element must contain text or an img with an alt attribute. WCAG 2.1 A F89 Section 508 (2017) A F89 1 pages

A link name allows screen readers to voice what the links does. If there is no link text / `alt` text, or the text / image is hidden by CSS, screen readers have nothing to read, so read out the URL instead. To add a name do one of the following:

  • Add text between the a element start and end tags
  • Add an aria-label attribute
  • Add an aria-labelledby attribute
  • Add a descriptive img alt attribute if the link contains an img element
img elements with role=presentation or role=none are not included in the link's accessible name. Note: img elements with display:none or visibility:hidden are not included in the link's accessible name. Some lazy loader scripts hide images until they scroll into view, but screen readers can voice links below the fold (via the List Links command) resulting in reading links with no name.		2.4.4 2.4.9 4.1.2
https://s1.eground.org/Line 381 397 409 3993 4001 ...
CriticalHTML form control has no accessible name. WCAG 2.1 A F68 Section 508 (2017) A F68 1 pages

A label (or name) linked to the control allows screen readers to voice the label correctly when reading the control. To add a label do one of the following:

  • Use a label element with the for attribute set to the ID of the form control
  • Wrap a label element around the form control
  • Add a title attribute
  • Add an aria-label attribute
  • Add an aria-labelledby attribute
4.1.2
https://s1.eground.org/search/?type=postLine 938
Criticalimg alt text must not use ASCII art (which includes smileys). WCAG 2.1 A F72 Section 508 (2017) A F72 1 pages
Change the alt text to a meaningful description. alt text consisting of punctuation characters sounds like "colon dash right-bracket" when read aloud.

Impact on users:

  • NVDA 2022.2 Chrome 105 Windows 10 Reading: Reads "graphic", with no indication what the graphic is.
  • NVDA 2022.2 FF102 Windows 10 Reading: Reads "graphic", with no indication what the graphic is.
  • NVDA 2022.2 Edge 105 Windows 10 Reading: Reads "graphic", with no indication what the graphic is.
  • NVDA 2021.2 Chrome 94 Windows 10 Reading: Reads "graphic", with no indication what the graphic is.
  • NVDA 2021.2 FF91 Windows 10 Reading: Reads "graphic", with no indication what the graphic is.
  • NVDA 2021.2 Edge 94 Windows 10 Reading: Reads "graphic", with no indication what the graphic is.
  • NVDA 2020.2 Chrome 86 Windows 10 Reading: Reads "graphic", with no indication what the graphic is.
  • NVDA 2020.2 FF78 Windows 10 Reading: Reads "graphic", with no indication what the graphic is.
  • NVDA 2020.2 Edge 92 Windows 10 Reading: Reads "graphic", with no indication what the graphic is.
  • NVDA 2019.2 Chrome 79 Windows 10 Reading: Reads "graphic", with no indication what the graphic is.
  • NVDA 2019.2 FF68 Windows 10 Reading: Reads "graphic", with no indication what the graphic is.
  • JAWS 2022.2207.25 Chrome 105 Windows 10 Reading: Meaningless punctuation read.
  • JAWS 2022.2207.25 FF102 Windows 10 Reading: Meaningless punctuation read.
  • JAWS 2022.2207.25 Edge 105 Windows 10 Reading: Meaningless punctuation read.
  • JAWS 2021.2107.12 Chrome 94 Windows 10 Reading: Meaningless punctuation read.
  • JAWS 2021.2107.12 FF91 Windows 10 Reading: Meaningless punctuation read.
  • JAWS 2021.2107.12 Edge 94 Windows 10 Reading: Meaningless punctuation read.
  • JAWS 2020.2008.24 Chrome 86 Windows 10 Reading: Meaningless punctuation read.
  • JAWS 2020.2008.24 FF78 Windows 10 Reading: Meaningless punctuation read.
  • JAWS 2020.2008.24 Edge 92 Windows 10 Reading: Meaningless punctuation read.
  • JAWS 2019.1912.1 Chrome 79 Windows 10 Reading: Meaningless punctuation read.
  • JAWS 2019.1912.1 FF68 Windows 10 Reading: Meaningless punctuation read.
1.1.1
alt=':)' alt=':)' alt=':)' alt=':)' alt=':)'
https://s1.eground.org/whats-new/thread-ratings/40164/		Line 1016 1016 1016 1016 1016 ...
CriticalNo space between attributes. HTML5 WCAG 2.1 A 4.1.1 Section 508 (2017) A 4.1.1 5 pages
https://s1.eground.org/Line 2361 2361 2616 2616 2651 ...
https://s1.eground.org/whats-new/latest-activityLine 856 856 882 882 911 ...
https://s1.eground.org/whats-new/profile-posts/40165/Line 808 808 823 823
https://s1.eground.org/whats-new/thread-ratings/40164/Line 899 899 1271 1271 1647 ...
This issue was found on another 1 pages. The trial version is limited to showing issues on 4 pages.
CriticalQuote " in attribute name. Probable cause: Matching quote missing somewhere earlier. HTML5 WCAG 2.1 A 4.1.1 Section 508 (2017) A 4.1.1 5 pages
https://s1.eground.org/Line 2361 2616 2651 3058 6916 ...
https://s1.eground.org/whats-new/latest-activityLine 856 882 911 939 965 ...
https://s1.eground.org/whats-new/profile-posts/40165/Line 808 823
https://s1.eground.org/whats-new/thread-ratings/40164/Line 899 1271 1647 2115 2301 ...
This issue was found on another 1 pages. The trial version is limited to showing issues on 4 pages.
CriticalUsing the same alt text on adjacent images results in screen readers stuttering as the same text is read out twice. WCAG 2.1 A 1.1.1 Section 508 (2017) A 1.1.1 1 pages
Use alt='' for the subsequent adjacent images, or change the redundant alt text.
https://s1.eground.org/whats-new/thread-ratings/40164/Line 1016 1016 1016 1016 1016 ...

Level AA

3 issues on 8 pages

Very ImportantEnsure that text and background colors have enough contrast. WCAG 2.1 AA 1.4.3 Section 508 (2017) AA 1.4.3 8 pages

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.

  • The contrast ratio should be 3.0 or more for 18 point text, or larger
  • The contrast ratio should be 3.0 or more for 14 point bold text, or larger
  • The contrast ratio should be 4.5 or more for all other text
1.4.6
The text color to background color contrast ratio after composition is:
1.33 with color: rgb(223,223,223);background-color: rgb(255,255,255);font-size: 8.25pt;font-weight: 400;
1.33 with color: rgb(223,223,223);background-color: rgb(255,255,255);font-size: 8.25pt;font-weight: 400;
1.33 with color: rgb(223,223,223);background-color: rgb(255,255,255);font-size: 8.25pt;font-weight: 400;
1.33 with color: rgb(223,223,223);background-color: rgb(255,255,255);font-size: 8.25pt;font-weight: 400;
1.33 with color: rgb(223,223,223);background-color: rgb(255,255,255);font-size: 8.25pt;font-weight: 400;
https://s1.eground.org/		Line 572 573 584 585 596 ...
The text color to background color contrast ratio after composition is:
2.71 with color: rgb(157,157,157);background-color: rgb(255,255,255);font-size: 9.75pt;font-weight: 400;
https://s1.eground.org/search/?type=post		Line 839
The text color to background color contrast ratio after composition is:
4.03 with color: rgb(89,126,165);background-color: rgb(249,249,249);font-size: 11.25pt;font-weight: 400;
2.71 with color: rgb(157,157,157);background-color: rgb(255,255,255);font-size: 11.25pt;font-weight: 400;
2.71 with color: rgb(157,157,157);background-color: rgb(255,255,255);font-size: 11.25pt;font-weight: 400;
2.71 with color: rgb(157,157,157);background-color: rgb(255,255,255);font-size: 11.25pt;font-weight: 400;
2.71 with color: rgb(157,157,157);background-color: rgb(255,255,255);font-size: 11.25pt;font-weight: 400;
https://s1.eground.org/whats-new/		Line 792 896 993 1090 1187 ...
The text color to background color contrast ratio after composition is:
4.03 with color: rgb(89,126,165);background-color: rgb(249,249,249);font-size: 11.25pt;font-weight: 400;
2.71 with color: rgb(157,157,157);background-color: rgb(255,255,255);font-size: 11.25pt;font-weight: 400;
2.71 with color: rgb(157,157,157);background-color: rgb(255,255,255);font-size: 11.25pt;font-weight: 400;
2.71 with color: rgb(157,157,157);background-color: rgb(255,255,255);font-size: 11.25pt;font-weight: 400;
2.71 with color: rgb(157,157,157);background-color: rgb(255,255,255);font-size: 11.25pt;font-weight: 400;
https://s1.eground.org/whats-new/posts/40166/		Line 779 1005 1107 1209 1311 ...
This issue was found on another 4 pages. The trial version is limited to showing issues on 4 pages.
Very ImportantThe 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
Do not remove the default outline style, and change any border styles 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)
1.4.11 2.4.7
:focus and :not(:focus) have same outline: :focus and :not(:focus) have same outline: :focus and :not(:focus) have same outline: :focus and :not(:focus) have same outline: :focus and :not(:focus) have same outline:
https://s1.eground.org/		Line 524 527 530 533 536
Very ImportantUser interface controls must have a contrast ratio of at least 3:1 against adjacent colors. WCAG 2.1 1.4.11 1 pages
If the control has a visible edge, make sure this has sufficient contrast against the area outside the control.
The contrast ratio between the control edge and surrounding area is:
1.16 with border-color: rgb(238,238,238);background-color: rgb(255,255,255); box margin rgb(255,255,255);
1.16 with border-color: rgb(238,238,238);background-color: rgb(255,255,255); box margin rgb(255,255,255);
1.16 with border-color: rgb(238,238,238);background-color: rgb(255,255,255); box margin rgb(255,255,255);
https://s1.eground.org/search/?type=post		Line 819 838 852

Level AAA

3 issues on 8 pages

ImportantAvoid specifying a new window as the target of a link with target=_blank. WCAG 2.1 AAA F22 8 pages
Displaying new windows without warning can be very confusing to non-sighted and mobile users. Some screen readers and mobile devices give very little indication a new tab or window has opened. If you cannot avoid displaying a new window, insert an "opens in a new window" warning into the link text or add the warning to the link using a title attribute or aria-label attribute. 3.2.5
https://s1.eground.org/Line 977 981 3836 3876 3939 ...
https://s1.eground.org/search/?type=postLine 1337 1406 1413 1424 1431 ...
https://s1.eground.org/whats-new/Line 1962 2031 2038 2049 2056 ...
https://s1.eground.org/whats-new/posts/40166/Line 3277 3346 3353 3364 3371 ...
This issue was found on another 4 pages. The trial version is limited to showing issues on 4 pages.
ImportantDon't use CSS animations or transitions in interactions without giving the user a way to turn them off. WCAG 2.1 2.3.3 8 pages
Use the @media (prefers-reduced-motion) media query to respect user preferences.
:hover transition: all 0.5s :hover transition: all 0.5s :hover transition: all 0.5s :hover transition: all 0.5s :hover transition: all 0.5s
https://s1.eground.org/		Line 466 469 472 475 478 ...
:hover transition: all 0.25s :hover transition: all 0.25s :hover transition: all 0.25s :hover transition: all 0.25s :hover transition: all 0.25s
https://s1.eground.org/search/?type=post		Line 246 330 402 424 446 ...
:hover transition: all 0.25s :hover transition: all 0.25s :hover transition: all 0.25s :hover transition: all 0.25s :hover transition: all 0.25s
https://s1.eground.org/whats-new/		Line 188 332 404 426 448 ...
:hover transition: all 0.25s :hover transition: all 0.25s :hover transition: all 0.25s :hover transition: all 0.25s :hover transition: all 0.25s
https://s1.eground.org/whats-new/posts/40166/		Line 248 332 404 426 448 ...
This issue was found on another 4 pages. The trial version is limited to showing issues on 4 pages.
ImportantEnsure that text and background colors have a 7:1 contrast ratio. WCAG 2.1 AAA 1.4.6 5 pages

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.

  • The contrast ratio should be 4.5 or more for 18 point text, or larger
  • The contrast ratio should be 4.5 or more for 14 point bold text, or larger
  • The contrast ratio should be 7.0 or more for all other text
The text color to background color contrast ratio after composition is:
5.14 with color: rgb(106,106,106);background-color: rgb(249,249,249);font-size: 9pt;font-weight: 400;
4.96 with color: rgb(255,255,255);background-color: rgb(226,0,0);font-size: 9pt;font-weight: 400;
4.96 with color: rgb(255,255,255);background-color: rgb(226,0,0);font-size: 9pt;font-weight: 400;
4.96 with color: rgb(255,255,255);background-color: rgb(226,0,0);font-size: 9pt;font-weight: 400;
4.96 with color: rgb(255,255,255);background-color: rgb(226,0,0);font-size: 9pt;font-weight: 400;
https://s1.eground.org/		Line 570 582 594 606 3671 ...
The text color to background color contrast ratio after composition is:
5.14 with color: rgb(106,106,106);background-color: rgb(249,249,249);font-size: 11.25pt;font-weight: 400;
5.14 with color: rgb(106,106,106);background-color: rgb(249,249,249);font-size: 11.25pt;font-weight: 400;
5.14 with color: rgb(106,106,106);background-color: rgb(249,249,249);font-size: 11.25pt;font-weight: 400;
https://s1.eground.org/search/?type=post		Line 792 796 799
The text color to background color contrast ratio after composition is:
4.54 with color: rgb(232,28,39);background-color: rgb(255,255,255);font-size: 12.75pt;font-weight: 700;
https://s1.eground.org/whats-new/latest-activity		Line 1026
The text color to background color contrast ratio after composition is:
3.70 with color: rgb(191,159,223);background-color: rgb(102,51,153);font-size: 21.75pt;font-weight: 400;
https://s1.eground.org/whats-new/profile-posts/40165/		Line 809
This issue was found on another 1 pages. The trial version is limited to showing issues on 4 pages.
Expand all 14 issues