[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.2Section 508 - 2017Key
ALevel A, 5 issuesLevel A, 5 issuesCritical Pages with level A issues are unusable for some people
AALevel AA, 2 issuesLevel AA, 2 issuesVery Important Pages with level AA issues are very difficult to use
AAALess Important Pages with level AAA issues can be difficult to use
PriorityDescription and URLGuideline and Line#Count

Level A

5 issues on 1 pages

Criticalalt text should not be a meaningless image file name. WCAG 2.2 A F30 Section 508 (2017) A F30 1 pages
Change the alt text to describe the information or function represented by the image, and for purely decorative images use alt="" without any global ARIA attributes. Do not use alt text containing only spaces since that's voiced as an unlabeled image. 1.1.1
alt='mobile_app3' alt='service_icon1' alt='service_icon2' alt='service_icon3' alt='service_icon4'
https://www.amstokens.io/presale/
Line 145 152 159 166 335 ...
Criticalalt text should not contain placeholders like 'picture' or 'spacer'. WCAG 2.2 A F30 Section 508 (2017) A F30 1 pages
For purely decorative images and spacers use alt='', for images of text use the text, and for other images use a description of the image.

Impact on users:

  • JAWS : Reads out placeholder text, instead of a useful image description.
  • NVDA : Reads out placeholder text, instead of a useful image description.
  • VoiceOver : Reads out placeholder text, instead of a useful image description.
1.1.1 1.2.1
alt='mobile_app3' alt='banner_vector2' alt='service_icon1' alt='service_icon2' alt='service_icon3'
https://www.amstokens.io/presale/
Line 126 145 152 159 335 ...
CriticalElements with role=tablist must contain or own an element with role=tab and must not contain elements with other roles. HTML5 ARIA 1.2 WCAG 2.2 A 1.3.1 Section 508 (2017) A 1.3.1 1 pages
Owned roles: listitem
https://www.amstokens.io/presale/
Line 460
Criticalimg elements must have an accessible name. WCAG 2.2 A F65 Section 508 (2017) A F65 1 pages
Add an alt attribute describing the image, which screen readers voice instead of the image. Spacer images and purely decorative images should use alt="" without any global ARIA attributes. Do not use alt text containing only spaces since that's voiced as an unlabeled image.

Impact on users:

  • NVDA 2023.3 Chrome 120 Windows 10 Reading: Image ignored.
  • NVDA 2023.3 FF 115 Windows 10 Reading: Image ignored.
  • NVDA 2023.3 Edge 120 Windows 10 Reading: Image ignored.
  • JAWS 2023.2311.34 Chrome 120 Windows 10 Reading: Image ignored.
  • JAWS 2023.2311.34 FF 115 Windows 10 Reading: Image ignored.
  • JAWS 2023.2311.34 Edge 120 Windows 10 Reading: Image ignored.
  • VoiceOver macOS 13.6 Safari 16.6 macOS 13.6.0 Reading: Image filename read out.
  • VoiceOver iOS 16.6 Safari iOS 16.6 iOS 16.6.1 Touch: Image filename read out, along with OCR text from image.
1.1.1
https://www.amstokens.io/presale/Line 100 250
CriticalUse semantic markup like strong instead of using the CSS font-weight property. WCAG 2.2 A F2 Section 508 (2017) A F2 1 pages
Use the strong element instead of the span element for bold text. 1.3.1
https://www.amstokens.io/presale/Line 90 239 239

Level AA

3 issues on 1 pages

Very ImportantCannot use aria-label or aria-labelledby on elements and roles that prohibit naming. HTML5 ARIA 1.2 1 pages
The div and span elements have an implicit role of generic and cannot be named unless they have a role attribute. The following roles cannot be named: caption code deletion emphasis generic insertion paragraph presentation strong subscript superscript
Element role: generic Element role: generic Element role: generic Element role: generic Element role: generic
https://www.amstokens.io/presale/
Line 479 489 506 516 534 ...
Very ImportantEnsure that text and background colors have enough contrast. WCAG 2.2 AA 1.4.3 Section 508 (2017) AA 1.4.3 1 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: 4.42 with color: rgb(122,122,122)background: rgb(12,14,39)font-size: 12ptfont-weight: 400 4.42 with color: rgb(122,122,122)background: rgb(12,14,39)font-size: 12ptfont-weight: 700 4.42 with color: rgb(122,122,122)background: rgb(12,14,39)font-size: 12ptfont-weight: 700 4.42 with color: rgb(122,122,122)background: rgb(12,14,39)font-size: 12ptfont-weight: 700 4.42 with color: rgb(122,122,122)background: rgb(12,14,39)font-size: 12ptfont-weight: 700
https://www.amstokens.io/presale/
Line 284 285 287 289 291 ...
Very ImportantThe CSS outline or border style on this element makes it difficult or impossible to see the link focus outline. WCAG 2.2 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. See :focus-visible for more information.

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)
2.4.7
:focus and :not(:focus) have same outline: outline-style:none or outline-width:0 outline-style:none or outline-width:0 :focus and :not(:focus) have same outline:
https://www.amstokens.io/presale/
Line 89 201 638 641
Expand all 8 issues