Site Report

[Skip navigation links]

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 2Section 508 - 2000Section 508 - 2017Key
ALevel A, 9 issues508, 7 issues508, 9 issuesCritical Priority A - accessibility users will find it impossible to use some pages
AALevel AA, 3 issuesVery Important, 3 issuesVery Important Priority AA - accessibility users will find it difficult to use some pages
AAALess Important Priority AAA - accessibility users will find it somewhat difficult to use some pages
PriorityDescription and URLGuideline and Line#Count

Level A

11 issues on 2 pages

CriticalAn image with a null ALT attribute should not have TITLE or ARIA label attributes.WCAG 2.0 A F39 Section 508 (2017) A F39 1 pages
If the image should be voiced use a descriptive ALT attribute. If the image is purely decorative remove any TITLE and ARIA label attributes.

Impact on users:

  • JAWS : Ignores all images with ALT=''.
  • NVDA : Reads some images with ALT='' and a TITLE or ARIA label.
  • WindowEyes : Reads images with ALT='' and a TITLE or ARIA label.
  • VoiceOver : Reads images with ALT='' and a TITLE or ARIA label.
https://vector-rev.blogspot.is/Line 1202
CriticalEach A element must contain text or an IMG with an ALT attribute.WCAG 2.0 A F89 Section 508 (2017) A F89 2 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.

The TITLE attribute on the A element doesn't work in:

  • WindowEyes 8.4 with IE11 (the link HREF is read instead)
  • VoiceOver on OSX 10.9 (the image filename is read instead)
https://vector-rev.blogspot.is/Line 658 777 836 893 939 ...
https://vector-rev.blogspot.is/2017/07/blog-post_16.htmlLine 654 769 801 847 859 ...
CriticalIdentify row and column headers in data tables using TH elements, and mark layout tables with role='presentation'.Section 508 (2000) 1194.22 (g) WCAG 2.0 A F91 Section 508 (2017) A F91 2 pages
Data tables allow screen reader users to understand column and row relationships. Layout tables read cells as a series of unrelated paragraphs with no tabular structure. Without TH or ROLE, screen readers apply heuristics to decide whether a table is a layout table or data table. These heuristics vary greatly between screen readers, and are affected by browser being used, window size, and font size (so the outcome is very unpredictable without TH or ROLE). If a data table has headers marked up using TD, then change these to TH. If a data table has no headers, add TH elements describing each row and/or column. If the table is only used for layout add role='presentation' to the TABLE element.

Impact on users:

  • JAWS Reading: Treats tables without TH and ROLE as layout tables if the table contains cells above or below certain pixel sizes. This measurement is affected by browser window size, browser font size, and the browser used.
  • NVDA Reading: Applies a 'layout table' heuristic to tables without TH and ROLE which varies depending on the browser used and on the window size in some circumstances.
  • VoiceOver Safari OSX 10.9 Reading: Uses a sophisticated heuristic on tables without TH and ROLE, which is similar (but not identical) to the heuristic used by NVDA with Firefox.
https://vector-rev.blogspot.is/Line 1000 1139 1203 1217 1305
https://vector-rev.blogspot.is/2017/07/blog-post_16.htmlLine 908 1047 1111 1125 1225
CriticalIMG elements must have an ALT attribute.Section 508 (2000) 1194.22 (a) WCAG 2.0 A F65 Section 508 (2017) A F65 2 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://vector-rev.blogspot.is/Line 1231
https://vector-rev.blogspot.is/2017/07/blog-post_16.htmlLine 1139
CriticalNo TITLE attributes found for the frames on these pages.Section 508 (2000) 1194.22 (i) WCAG 2.0 A 2.4.1 Section 508 (2017) A 2.4.1 2 pages
Add a TITLE attribute to each FRAME and IFRAME element (e.g. TITLE="Main Content"). Without a TITLE some screen readers read out the FRAME filename, which is usually meaningless.

IFRAMEs with no title cause problems in:

  • JAWS 14 and 15 with Firefox (the frame SRC filename is read instead)
  • VoiceOver on OSX 10.9 (a meaningless title like "Frame twelve" is read out)
https://vector-rev.blogspot.is/Line 753 812 869 1121 1395 ...
https://vector-rev.blogspot.is/2017/07/blog-post_16.htmlLine 749 802 1029
CriticalProvide a way to skip repetitive navigation links.Section 508 (2000) 1194.22 (o) 1 pages
Without skip links, keyboard users must tab through the navigation links to get to page content. Headings and landmarks allow screen reader users to skip navigation, but don't work for other keyboard users. Add a "Skip to Content" link at the start of the document hidden offscreen by CSS, and made visible on focus, so it's available to keyboard and screen reader users: <a class="accessible" href="#main">[Skip to Content]</a>
https://vector-rev.blogspot.is/2017/07/blog-post_16.htmlLine 623 654 741 759 769 ...
CriticalRemoving the underline from links makes it hard for color-blind users to see them.Section 508 (2000) 1194.22 (c) WCAG 2.0 A F73 Section 508 (2017) A F73 2 pages
Remove the text-decoration:none property from your link styles, or add other non-color style attributes to visually distinguish links.
https://vector-rev.blogspot.is/Line 146
https://vector-rev.blogspot.is/2017/07/blog-post_16.htmlLine 146
CriticalThis form control has no LABEL and no programmatically determined name.WCAG 2.0 A F68 Section 508 (2017) A F68 Section 508 (2000) 1194.22 (n) 2 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://vector-rev.blogspot.is/Line 1142 1317 1322 1327
https://vector-rev.blogspot.is/2017/07/blog-post_16.htmlLine 1050 1237 1242 1247
CriticalThis form has fields without LABEL elements or TITLE attributes.Section 508 (2000) 1194.22 (n) 2 pages
Screen readers use LABEL elements or TITLE attributes to describe form fields to non-sighted users. Without these, forms are very hard to use with a screen reader. Forms designed to be completed online shall allow people using assistive technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues.
https://vector-rev.blogspot.is/Line 1142 1317 1322 1327
https://vector-rev.blogspot.is/2017/07/blog-post_16.htmlLine 1050 1237 1242 1247
CriticalThis page has markup errors, causing screen readers to miss content.WCAG 2.0 A F70 Section 508 (2017) A F70 2 pages
Fix the errors listed on the Standards tab of this report. Markup errors like missing end tags mean screen readers may skip important content.
https://vector-rev.blogspot.is/Line 783 1206
https://vector-rev.blogspot.is/2017/07/blog-post_16.htmlLine 775 1114
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 2 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://vector-rev.blogspot.is/Line 2
https://vector-rev.blogspot.is/2017/07/blog-post_16.htmlLine 2

Level AA

3 issues on 2 pages

Very ImportantEnsure that foreground and background colors have enough contrast.WCAG 2.0 AA 1.4.3 Section 508 (2017) AA 1.4.3 2 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 foreground to background color contrast ratio is 1. CSS color: 0, 0, 0; background-color: 0, 0, 0; font-size: pt; font-weight:
https://vector-rev.blogspot.is/
Line 133 760 819 876
The foreground to background color contrast ratio is 1. CSS color: 0, 0, 0; background-color: 0, 0, 0; font-size: pt; font-weight:
https://vector-rev.blogspot.is/2017/07/blog-post_16.html
Line 133
Very ImportantProvide information about the general layout of a site using a site map or table of contents.WCAG 2.0 AA 2.4.5 Section 508 (2017) AA 2.4.5 1 pages
You should provide a link labeled 'Site Map' or 'Sitemap' or the equivalent in your language, on every page.
https://vector-rev.blogspot.is/Line 1
Very ImportantUse relative rather than absolute units in CSS property values.WCAG 2.0 AA 1.4.4 Section 508 (2017) AA 1.4.4 2 pages
Absolute units are CM, MM, IN, PC and PT. When used with fonts PX is also considered an absolute unit, because it isn't relative the user's preferred font size. Low-vision users, and a lot of people over 50, increase the browser default font size to make text easier to read. Absolute units ignore this user choice. Relative units like EM and percentages "stretch" according to the screen size and/or user's preferred font size, and work on a large range of devices.
https://vector-rev.blogspot.is/Line 134 196 230 264 301 ...
https://vector-rev.blogspot.is/2017/07/blog-post_16.htmlLine 134 196 230 264 301 ...
Expand all 14 issues