Accessible Indexpowered by Dynamosys

Government Publishing Office

gpo.gov

Federal: Section 508 applies, not Title II · 20 pages and a keyboard test, checked October 6, 2026

Status

Scanned

From our checks · October 2026

Not yet claimed by its staff

What the statuses mean

36out of 100

ScoreFar behindMany problems found across the pages checkedAutomated checks of 20 pages, October 6, 2026. They find many problems, not all.

1critical barrier

Controls a visitor can’t use at all. Any one keeps a site at Behind, whatever its score.

Compared

The 5 other Government Publishing Office websites checked average 55.

Fixing the 1 critical barrier would raise this from 36 (Far behind) to 39 (Far behind).

See how it does today

Our latest check was on October 6, 2026, and the next is in January 2027. You can check gpo.gov yourself now, free. You get a report of your own; this page changes at our next check.

Check gpo.gov now Opens our free check with its address filled in.

What we found

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

  • 1

    1 drop-down list has no label, so a blind visitor’s screen reader can’t say what it is for.

    Critical barrierBlocks a task
    • Screen readers
    • Voice control
  • 786

    Text in 786 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
  • 32

    32 parts of the page carry screen-reader details that don’t apply to them, so screen readers may describe them wrongly.

    • Screen readers
  • 28

    28 controls sit inside others, such as buttons inside links, so screen readers may skip some of them and keyboard users may not reach them.

    • Screen readers
    • Keyboard users
  • 14

    14 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
  • 14

    14 lists are built incorrectly, so screen readers may not announce them as lists or say how many items they have.

    • Screen readers
  • 8

    8 controls show no sign when a keyboard user moves to them, so they can’t tell where they are on the page.

    Not in the score
    • Keyboard users
    • Low vision
  • 5

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

    • Screen readers
  • 4

    4 embedded sections, such as maps, videos or forms from other sites, have no title, so a blind visitor’s screen reader can’t say what they are.

    • Screen readers
  • 4

    4 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
  • 3

    3 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
  • 3

    3 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
  • 2

    2 buttons or links are so small, or so close to others, that people with shaky hands may tap the wrong thing.

    Not in the score
    • Limited hand movement
  • 1

    1 field has no name, so a blind visitor’s screen reader can’t say what to type into it.

    • Screen readers
    • Voice control

More in the full report

The full report is for the agency’s own staff. It adds:

  • The 20 pages we checked, by name
  • Where each problem is, with a screenshot
  • What needs to change, in the order to fix it
  • A new check any day, once something is fixed

Claim this page to see it

The keyboard test

We pressed Tab 38 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: 5 controls show no sign of focus. Keyboard users may not be able to tell where they are.

Questions about this page

Does this mean the agency is breaking the law?

No. Federal agencies follow Section 508 of the Rehabilitation Act, whose standards are built on WCAG 2.0 AA. This is an automated check against WCAG 2.1 AA, which includes every WCAG 2.0 AA requirement. Automated checks find many problems but not all, and only a full review can say whether a site meets Section 508.

Why isn’t there a Title II deadline?

The ADA’s Title II rule and its April 2027 and April 2028 deadlines are for state and local governments. Federal websites already have to meet Section 508.

How often is this page updated?

Every three months, in January, April, July and October. Once its staff claim this page, they can also scan the site again, once a day; the new result shows here like our regular check, marked as checked at their request. The date at the top shows the latest check, and the score can go up as problems are fixed.

How can the agency respond?

Staff with an email address ending in @gpo.gov can claim this page to set its status, see where each problem is, and scan the site again. Think a result is wrong? Tell us and we will check it again.

Work for the Government Publishing Office?

Claim this page to see where each problem is and what needs to change, set its status for the public, and scan again any day.

An address ending in @gpo.gov, the domain of the website we check. We’ll email you a link to confirm.

Read the Terms and our Privacy policy.

Our commitments to governments

This is an automated scan. It finds many but not all accessibility problems, and it can be wrong. If something looks off, let us know. This is not legal advice or a certification of compliance.