What we scan
ScanGov scans the homepage of every federal site on our list, 866 sites. Each scan runs the checks on standards.scangov.org for accessibility, botability, security, usability, and readability. A site counts as fully scanned when its homepage responded and returned page content; sites that did not are listed with their scan status and left out of every figure here. The federal rankings list every site; Pulse for all sites compares the groups.
688 of 866
Federal sites fully scanned. We couldn't fully scan 178
C 79
Average overall score of the fully scanned federal sites
15%
Fully scanned federal sites earning an A overall (104 sites)
11/8/2026
Newest scan. Sites were scanned between 9/30/2026 and this date
How sites are doing
Of 688 fully scanned sites, 15% (104) earn an A for overall score, 71% (488) a B or C, and 14% (96) a D or F. The average score is 79. The curve shows where scores cluster; the bar shows the share in each grade band.
How federal overall scores are distributed
Smoothed distribution of the 688 fully scanned federal sites, score 0 to 100. Height shows how many sites score near each value.
Distribution of 688 scores. The data table lists counts by score range.
- Average
View the data table
| Score range | Sites |
|---|---|
| 0 to 9 | 0 |
| 10 to 19 | 0 |
| 20 to 29 | 0 |
| 30 to 39 | 0 |
| 40 to 49 | 1 |
| 50 to 59 | 15 |
| 60 to 69 | 80 |
| 70 to 79 | 240 |
| 80 to 89 | 248 |
| 90 to 100 | 104 |
Federal sites by overall grade
Share of the 688 fully scanned federal sites in each grade band
- A (90 to 100)
- B to C (70 to 89)
- D to F (below 70)
View the data table
| Group | A (90 to 100) | B to C (70 to 89) | D to F (below 70) |
|---|---|---|---|
| All federal sites | 15% (104) | 71% (488) | 14% (96) |
Where sites fail
For each indicator, the five checks that fully scanned federal sites fail most often. A site can fail more than one check. In each chart, a check links to the list of federal sites failing it where we have one, or to its standard; the notes under the chart link every standard.
Accessibility
Meet WCAG standards so every type of user can use your website. The most common accessibility failure is Background and foreground colors have a sufficient contrast ratio: 28% (196 of 688 sites) fail it.
What each accessibility check means
- Background and foreground colors have a sufficient contrast ratio. Text and background colors meet minimum contrast ratios. Users with low vision cannot read your text.
- Heading elements appear in a sequentially-descending order. Page headings follow a logical order without skipping levels. Keyboard users cannot efficiently navigate your site.
- Document has a main landmark. The page has exactly one main content area so screen readers can navigate to it. Screen reader users cannot skip directly to main content.
- Touch targets have sufficient size and spacing. Buttons and interactive elements are large enough to tap easily on touch screens. Users with motor disabilities struggle to tap small buttons.
- Links have a discernible name. Links have unique, descriptive text so users know where they go. Screen reader users cannot identify or interact with elements.
Botability
Help AI and search engines discover, crawl, and index your website. The most common botability failure is GovernmentOrganization Schema.org type: 93% (640 of 688 sites) fail it.
What each botability check means
- GovernmentOrganization Schema.org type. Homepage is marked up as an official government organization. Systems cannot verify you are an official government site.
- Link text. Links use descriptive text that tells users and search engines where they go. Users cannot tell where links go.
- Sitemap status. The sitemap file loads and returns a successful response. Search engines cannot find all your pages.
- Sitemap XML. The sitemap file uses the required XML format. Search engines cannot read your sitemap.
- Sitemap in robots.txt. The robots.txt file links to the sitemap. Search engines take longer to find your pages.
Security
Secure your site and protect users with proper security practices. The most common security failure is Errors in the console: 40% (275 of 688 sites) fail it.
What each security check means
- Errors in the console. The page loads without JavaScript or network errors. Site may have hidden bugs that break features.
- X-Content-Type-Options. The site tells browsers not to guess the type of files it serves. Browsers might run dangerous files by mistake.
- Sponsored top-level domain (sTLD). The site uses a government-issued domain (.gov, .edu, or .mil). People cannot tell if your site is real government.
- Security.txt. The site has a security.txt file so researchers know how to report issues. Security researchers cannot report problems to you.
- Paste preventing inputs. The page lets users paste content into form fields. Users cannot use password managers safely.
Usability
Optimize content structure so users quickly find what they need. The most common usability failure is Open Graph image alt: 89% (612 of 688 sites) fail it.
What each usability check means
- Open Graph image alt. The social media preview image has alt text for screen readers. Screen readers cannot describe shared images.
- Open Graph site name. The site has a name for social media and browser display. Site name missing in social media shares.
- Open Graph image. The page has a preview image for social media cards. Shared links have no image on social media.
- Open Graph description. The page has a description for social media previews. Shared links have no description on social media.
- Open Graph type. The page declares its content type for social media cards. Social media shows wrong content type.
Readability
Write content at a reading level most users can understand. The most common readability failure is Reading level: 49% (339 of 688 sites) fail it.
What each readability check means
- Reading level. Page text reads at or below a 7th grade level so most users can understand it. Users struggle to understand your content.
Where to go next
- Federal rankings: 688 fully scanned of 866 sites.
- Pulse for all sites: every group compared.
- Federal websites not on a .gov domain: 148 of 688 fully scanned federal sites, with every site listed.
- Federal websites with sitemap problems: 352 of 670 fully scanned federal sites, with every site listed.
- Federal websites with robots.txt problems: 32 of 663 fully scanned federal sites, with every site listed.
- Federal websites that need JavaScript to show their content: 61 of 688 fully scanned federal sites, with every site listed.
- Federal websites that are hard to read: 339 of 591 fully scanned federal sites, with every site listed.
- Federal websites missing Open Graph tags: 553 of 688 fully scanned federal sites, with every site listed.
- Websites by issue: every check and every group in one table.
- Changelog: what changed in the latest scans.
- Scan status: why some sites could not be fully scanned.
About this data
ScanGov scans the homepage of every federal site on our list. Scores come from the checks in the ScanGov standards. Sites were scanned between 9/30/2026 and 11/8/2026. Each site's report shows its own scan date. A site counts as fully scanned when its homepage loaded and sent us its page content. Averages, grade shares, failure rates, and ranks use fully scanned sites only. We could not fully scan 178 sites. They did not respond, blocked the scanner, or sent no page content. They appear in the table without grades, with their scan status, and are left out of every figure. Grades follow the ScanGov grade scale. Rank follows the ScanGov ranking method. The full dataset, with every county's raw results, is in the ScanGov data repository.