Accessible Indexpowered by Dynamosys

Federal Acquisition Service · General Services Administration

sam.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

55out of 100

ScoreBehindMany problems found, or at least one critical barrierAutomated checks of 20 pages, October 6, 2026. They find many problems, not all.

0critical barriers

The automated checks found no control a visitor can’t use at all.

Compared

The 30 other General Services Administration websites checked average 79.

See how it does today

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

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

What we found

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

  • 10

    Text in 10 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
  • 6

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

    6 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
  • 5

    5 items that belong in menus, lists or sets of tabs sit outside them, so screen readers may not announce them as part of their group.

    • Screen readers
  • 4

    4 drop-down lists have no label, so a blind visitor’s screen reader can’t say what they are for.

    • Screen readers
    • Voice control
  • 3

    3 parts of the page have labels that screen readers ignore, because of what those parts are, so a blind visitor may miss what they say.

    • Screen readers
  • 3

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

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

    1 control shows no sign when a keyboard user moves to it, so they can’t tell where they are on the page.

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

    1 menu, list or set of tabs is built incompletely, so screen readers may announce it without its items or not let a blind visitor move through them.

    • Screen readers
  • 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
  • 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 part of the page carries a broken detail for screen readers, such as a pointer to something that isn’t there, so screen readers may describe it wrongly.

    • Screen readers

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 72 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.

  • Passed: “Skip to content” works. Keyboard users can jump past the menu.
  • Problem: 1 control shows 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 @sam.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 Federal Acquisition Service?

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 @sam.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.