huduser.gov

What we found

What is wrong and who it affects, most serious first.

• 2

  2 buttons have no name, so a blind visitor’s screen reader says just “button”, with no clue to what they do.

  Critical barrierBlocks a task

  • Screen readers
  • Voice control
• 17

  17 links in running text stand out only by their color, so people with color blindness or low vision may not see that they are links.

  • Color blindness
  • Low vision
• 16

  16 pages have to be scrolled sideways on a narrow phone screen, so people who enlarge text must scroll back and forth to read each line.

  • Low vision
• 14

  Text in 14 places is too faint against its background, so people with low vision, or anyone reading a phone in sunlight, may struggle to read it.

  • Low vision
  • Color blindness
• 9

  9 list items sit outside a list, so screen readers may not announce them as part of one.

  • Screen readers
• 3

  3 images have no description, so a blind visitor’s screen reader says only “image” or reads out file names.

  • Screen readers
• 2

  2 links have no name, so a blind visitor’s screen reader says just “link”, with no clue to where they go.

  • Screen readers
  • Voice control
• 2

  2 fields have no name, so a blind visitor’s screen reader can’t say what to type into them.

  • Screen readers
  • Voice control
• 2

  2 menus, lists or sets of tabs are built incompletely, so screen readers may announce them without their items or not let a blind visitor move through them.

  • Screen readers
• 1

  1 part of the page carries screen-reader details that don’t apply to it, so screen readers may describe it wrongly.

  • Screen readers
• 1

  1 control sits inside another, such as a button inside a link, so screen readers may skip one of them and keyboard users may not reach it.

  • Screen readers
  • Keyboard users
• 1

  On 1 page, pressing Tab gets stuck on one control, so someone using a keyboard instead of a mouse can’t reach the rest of the page.

  Not in the score

  • Keyboard users
  • Screen readers
• 1

  1 embedded section, such as a map, video or form from another site, has no title, so a blind visitor’s screen reader can’t say what it is.

  • Screen readers
• 1

  1 form field has no label, so a blind visitor’s screen reader can’t say what to enter, and voice-control users can’t name it.

  • Screen readers
  • Voice control
• 1

  1 list is built incorrectly, so screen readers may not announce it as a list or say how many items it has.

  • Screen readers

The keyboard test

We pressed Tab 39 times through the homepage, as someone who can’t use a mouse would. What it found is shown here and is not yet counted in the score.

• Problem: Focus gets stuck. Pressing Tab stops on one control, so keyboard users can’t reach the rest of the homepage.
• Passed: “Skip to content” works. Keyboard users can jump past the menu.
• Passed: Focus can be seen. Every control we reached shows where the keyboard is.

Questions about this page