National Oceanic and Atmospheric Administration · Department of Commerce
papahanaumokuakea.gov
Federal: Section 508 applies, not Title II · 20 pages and a keyboard test, checked October 6, 2026
35out of 100
1critical barrier
Controls a visitor can’t use at all. Any one keeps a site at Behind, whatever its score.
Compared
The 34 other Department of Commerce websites checked average 70.
Fixing the 1 critical barrier would raise this from 35 (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 papahanaumokuakea.gov yourself now, free. You get a report of your own; this page changes at our next check.
Check papahanaumokuakea.gov now Opens our free check with its address filled in.
What we found
What is wrong and who it affects, most serious first.
-
3
3 form fields have no label, so a blind visitor’s screen reader can’t say what to enter, and voice-control users can’t name them.
- Screen readers
- Voice control
-
242
242 buttons or links are so small, or so close to others, that people with shaky hands may tap the wrong thing.
- Limited hand movement
-
138
138 images have no description, so a blind visitor’s screen reader says only “image” or reads out file names.
- Screen readers
-
138
138 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
-
75
Text in 75 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
-
39
39 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
-
8
8 controls show no sign when a keyboard user moves to them, so they can’t tell where they are on the page.
- Keyboard users
- Low vision
-
6
6 parts of the page are hidden from screen readers but can still be reached with the Tab key, so a blind visitor lands on things their screen reader won’t describe.
- Screen readers
- Keyboard users
-
6
6 lists are built incorrectly, so screen readers may not announce them as lists or say how many items they have.
- Screen readers
-
4
4 pages don’t say what language they are in, so screen readers may read them aloud with the wrong pronunciation.
- Screen readers
-
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 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 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 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 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
-
1
1 link in running text stands out only by its color, so people with color blindness or low vision may not see that it is a link.
- Color blindness
- Low vision
-
1
1 page stops visitors zooming in on a phone, so people with low vision can’t enlarge the text to read it.
- Low vision
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
The keyboard test
We pressed Tab 98 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: 6 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 @papahanaumokuakea.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 National Oceanic and Atmospheric Administration?
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.