Department of Education
nces.ed.gov
Federal: Section 508 applies, not Title II · 20 pages and a keyboard test, checked October 6, 2026
35out of 100
0critical barriers
The automated checks found no control a visitor can’t use at all.
Compared
The 3 other Department of Education websites checked average 61.
See how it does today
Our latest check was on October 6, 2026, and the next is in January 2027. You can check nces.ed.gov yourself now, free. You get a report of your own; this page changes at our next check.
Check nces.ed.gov now Opens our free check with its address filled in.
What we found
What is wrong and who it affects, most serious first.
-
90
90 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
-
62
62 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
-
39
Text in 39 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
-
23
23 images have no description, so a blind visitor’s screen reader says only “image” or reads out file names.
- Screen readers
-
10
10 parts of the page carry screen-reader details that don’t apply to them, so screen readers may describe them wrongly.
- Screen readers
-
10
10 drop-down lists have no label, so a blind visitor’s screen reader can’t say what they are for.
- Screen readers
- Voice control
-
9
9 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
-
7
7 buttons or links are so small, or so close to others, that people with shaky hands may tap the wrong thing.
- Limited hand movement
-
6
6 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
-
4
4 pages don’t say what language they are in, so screen readers may read them aloud with the wrong pronunciation.
- Screen readers
-
4
4 list items sit outside a list, so screen readers may not announce them as part of one.
- Screen readers
-
3
3 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
-
2
On 2 pages, pressing Tab gets stuck on one control, so someone using a keyboard instead of a mouse can’t reach the rest of those pages.
- Keyboard users
- Screen readers
-
2
2 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
-
2
2 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
-
1
1 control is missing details screen readers need, such as whether it is on or open, so a blind visitor can’t tell its state.
- 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 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
The keyboard test
We pressed Tab 5 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
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 @nces.ed.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 Department of Education?
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.