[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.0Section 508 - 2017Key
ALevel A, 11 issuesLevel A, 11 issuesCritical Pages with level A issues are unusable for some people
AALevel AA, 3 issuesLevel AA, 3 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

11 issues on 7 pages

CriticalAll fieldset elements should be labeled with legend elements. WCAG 2.0 A H71 Section 508 (2017) A H71 2 pages
The first child element inside a `fieldset` must be a `legend` element, which provides a label or description for the group. `legend` elements in other positions may be ignored.
https://coinexpressway.com/Exchange/ccexLine 1831
https://coinexpressway.com/ExchangesLine 19193
CriticalAll onclick handlers should have an equivalent onkeypress handler. WCAG 2.0 A F54 Section 508 (2017) A F54 7 pages
Some users are unable to use a mouse, so use the keyboard instead. Add an equivalent keyboard event handler to help these users.
https://coinexpressway.com/Line 489
https://coinexpressway.com/CoinsLine 7223
https://coinexpressway.com/ExchangesLine 299 367 435 503 19329 ...
https://coinexpressway.com/NewsLine 40875
This issue was found on another 3 pages. The trial version is limited to showing issues on 4 pages.
Criticalalt text should not contain placeholders like 'picture' or 'spacer'. WCAG 2.0 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.
  • SaToGo : Reads out placeholder text, instead of a useful image description.
  • WindowEyes : Reads out placeholder text, instead of a useful image description.
  • VoiceOver : Reads out placeholder text, instead of a useful image description.
alt='FinCEN' alt='FinCEN' alt='FinCEN' alt='FinCEN' alt='FinCEN'
https://coinexpressway.com/News
Line 9490 11851 14212 16573 18934 ...
CriticalDecorative and spacer images must have a null alt attribute. WCAG 2.0 A F38 Section 508 (2017) A F38 1 pages
Images used for decoration only should have alt='' or role='presentation' so they can be ignored by screen readers.

Impact on users:

  • JAWS : Reads out redundant ALT text.
  • NVDA : Reads out redundant ALT text.
  • SaToGo : Reads out redundant ALT text.
  • WindowEyes : Reads out redundant ALT text.
  • VoiceOver : Reads out redundant ALT text.
https://coinexpressway.com/ExchangesLine 4898
CriticalDuplicate id - the same ID is used on more than one element. HTML5 WCAG 2.0 A 4.1.1 Section 508 (2017) A 4.1.1 1 pages
`id=div2`.
https://coinexpressway.com/
Line 200 270 279 348
CriticalEach a element must contain text or an img with an alt attribute. WCAG 2.0 A F89 Section 508 (2017) A F89 7 pages
Add text to the link, or ALT text if the link contains an image. If there is no link text or the ALT text is blank, screen readers have nothing to read, so read out the URL instead.
https://coinexpressway.com/Line 60 447 450 453 485 ...
https://coinexpressway.com/CoinsLine 91 120 7163 7167 7218 ...
https://coinexpressway.com/ExchangesLine 91 120 19269 19273 19324 ...
https://coinexpressway.com/NewsLine 91 120 40815 40819 40870 ...
This issue was found on another 3 pages. The trial version is limited to showing issues on 4 pages.
CriticalElement div not allowed as child element in this context. HTML5 WCAG 2.0 A 4.1.1 Section 508 (2017) A 4.1.1 2 pages
https://coinexpressway.com/coin/dashLine 191
https://coinexpressway.com/Exchange/ccexLine 190
Criticalimg elements must have an alt attribute. WCAG 2.0 A F65 Section 508 (2017) A F65 7 pages
Add an ALT attribute describing each image, which screen readers read aloud. Spacer images and purely decorative images should use ALT=''.

Impact on users:

  • NVDA 2015.2 FF40 Windows 7 Reading: Image ignored.
  • JAWS 16.0.4350 FF40 Windows 7 Reading: Image ignored.
  • WindowEyes 8.4 IE11 Windows 7 Reading: Image ignored.
  • VoiceOver Safari OSX 10.10 Reading: Image filename read out.
  • VoiceOver Safari iOS 7.1 Touch: Image filename read out.
  • SaToGo 3.4.96.0 IE11 Windows 7 Reading: Image ignored.
https://coinexpressway.com/Line 60 129 251 282 413
https://coinexpressway.com/CoinsLine 92 301 369 437 505 ...
https://coinexpressway.com/ExchangesLine 92 274 342 410 19232 ...
https://coinexpressway.com/NewsLine 92 794 811 828 845 ...
This issue was found on another 3 pages. The trial version is limited to showing issues on 4 pages.
Criticallabel elements should be attached to the controls they label. WCAG 2.0 A 4.1.2 Section 508 (2017) A 4.1.2 1 pages
Add a FOR attribute set to the ID of the associated control, or wrap the LABEL round the associated control, or use a different element if this isn't a control label.
https://coinexpressway.com/NewsLine 195
CriticalThis form control has no label and no programmatically determined name. WCAG 2.0 A F68 Section 508 (2017) A F68 7 pages

A programmatically determined name allows screen readers to tell the user what the control does. To add a name 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-LABELLEDBY attribute (not supported in all screen readers)
  • Add an ARIA-LABEL attribute (not supported in all screen readers)
https://coinexpressway.com/Line 73 92 133 437
https://coinexpressway.com/CoinsLine 116 162 207 7152
https://coinexpressway.com/ExchangesLine 162 19202 19205 19208 19258 ...
https://coinexpressway.com/NewsLine 116 162 196 40804
This issue was found on another 3 pages. The trial version is limited to showing issues on 4 pages.
CriticalUse the lang attribute to identify the language of the page. WCAG 2.0 A 3.1.1 Section 508 (2017) A 3.1.1 7 pages
In HTML add a `lang` attribute to the `html` tag, and in PDF set the language using Document Properties in Acrobat. This allows screen readers to pronounce words correctly.
https://coinexpressway.com/Line 2
https://coinexpressway.com/CoinsLine 2
https://coinexpressway.com/ExchangesLine 2
https://coinexpressway.com/NewsLine 2
This issue was found on another 3 pages. The trial version is limited to showing issues on 4 pages.

Level AA

3 issues on 1 pages

Very ImportantEnsure that text and background colors have enough contrast. WCAG 2.0 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
The text color to background color contrast ratio is:
3.54 with color: rgb(136,136,136);background-color: rgb(255,255,255);font-size: 9.96pt;font-weight: 700.00;
https://coinexpressway.com/
Line 462
Very ImportantIf you set any of the colors on the body or a elements you must set all of them. WCAG 2.0 AA F24 Section 508 (2017) AA F24 1 pages
In HTML the color attributes are `text`, `bgcolor`, `link`, `alink` and `vlink`. In CSS the attributes are `color` and `background-color`. Some users have browser defaults set to white text on a black background, so setting one color without setting the others can result in black text on a black background.
The colors used are:
color: rgb(0,0,238); uses browser default background-color: rgb(255,255,224);
color: rgb(0,0,238); uses browser default background-color: rgb(255,255,224);
color: rgb(0,0,238); uses browser default background-color: rgb(255,255,224);
https://coinexpressway.com/
Line 47 47 48
Very ImportantThis CSS style makes it difficult or impossible to see the dotted link focus outline. WCAG 2.0 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 and Edge do not support the outline-offset property, so using this does not reliably avoid focus outline overlap.

https://coinexpressway.com/Line 6
Expand all 14 issues