Accessibility
6,097 U.S. websites checked for accessibility. The average score is 90 out of 100. Meet WCAG standards so every type of user can use your website.
Of 6,097 fully scanned sites, 59% (3,567) earn an A for accessibility, 39% (2,404) a B or C, and 2% (126) a D or F. The average score is 90.
Why accessibility matters
People with disabilities need equal access to information and services online.
People with disabilities cannot use your site.
What we check
Standards for making your website usable by people with disabilities.
- <dl>'s contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements: Definition lists use correct markup so screen readers can announce them properly.
- <frame> or <iframe> elements have a title: Embedded frames have titles so screen readers can describe their content.
- <html> element has a [lang] attribute: The page declares its language so screen readers use the correct voice.
- <html> element has a valid value for its [lang] attribute: The page has a valid language code so screen readers pronounce content correctly.
- <html> element has an [xml:lang] attribute with the same base language as the [lang] attribute: The page's language setting is consistent so screen readers pronounce content correctly.
- <input type="image"> elements have [alt] text: Image buttons have alt text that describes their action.
- <object> elements have alternate text: Embedded objects have alt text so screen readers can describe their content.
- <td> elements in a large <table> have one or more table headers: Each cell in a large table is linked to a header so screen readers can navigate it.
- <th> elements and elements with [role="columnheader"/"rowheader"] have data cells they describe: Table headers have associated data cells.
- <video> elements contain a <track> element with [kind="captions"]: Videos include captions for users who are deaf or hard of hearing.
- [accesskey] values are unique: Each access key shortcut is unique so keyboard navigation works correctly.
- [aria-*] attributes are valid and not misspelled: Accessibility attributes use valid, recognized names.
- [aria-*] attributes have valid values: Accessibility attributes use valid values so screen readers can interpret them.
- [aria-*] attributes match their roles: Accessibility attributes are only used where they are supported.
- [aria-hidden="true"] elements do not contain focusable descendents: Interactive elements are not hidden from screen reader users.
- [aria-hidden="true"] is not present on the document <body>: The page body is not hidden from screen readers.
- [lang] attributes have a valid value: Language codes on page elements are valid so screen readers pronounce content correctly.
- [role] values are valid: Accessibility roles use valid, recognized values.
- [role]s are contained by their required parent element: Interactive elements are nested inside the correct parent container.
- [role]s have all required [aria-*] attributes: Accessibility roles include all required attributes so screen readers can describe the element.
- [user-scalable="no"] is not used in the <meta name="viewport"> element and the [maximum-scale] attribute is not less than 5: The page allows users to zoom in on mobile devices.
- All heading elements contain content: Headings have visible, descriptive text so screen readers can announce them.
- ARIA attributes are used as specified for the element's role: Accessibility attributes are only used when the element's role allows them.
- ARIA IDs are unique: Each element has a unique ID so screen readers can reference it correctly.
- ARIA input fields have accessible names: Form input fields have labels that screen readers can announce.
- ARIA meter elements have accessible names: Meter elements have labels so screen readers can announce their value.
- ARIA progressbar elements have accessible names: Progress bars have labels so screen readers can describe their status.
- ARIA toggle fields have accessible names: Toggle controls have labels that screen readers can announce.
- ARIA tooltip elements have accessible names: Tooltips have labels so screen readers can describe their content.
- ARIA treeitem elements have accessible names: Tree navigation items have labels that screen readers can announce.
- Background and foreground colors have a sufficient contrast ratio: Text and background colors meet minimum contrast ratios.
- button, link, and menuitem elements have accessible names: Buttons, links, and menu items have labels that screen readers can announce.
- Buttons have an accessible name: Buttons have labels so screen readers can describe their action.
- Cells in a <table> element that use the [headers] attribute refer to table cells within the same table: Table data cells correctly reference their header cells.
- Character encoding: The page declares its character encoding so text displays correctly.
- Definition list items are wrapped in <dl> elements: Definition list items are nested inside the correct parent element.
- Deprecated ARIA roles were not used: Accessibility roles use current, supported values.
- Document has a <title> element: The page has a descriptive title visible in browser tabs and search results.
- Document has a main landmark: The page has exactly one main content area so screen readers can navigate to it.
- Elements use only permitted ARIA attributes: Accessibility attributes are not used where they are prohibited.
- Elements with an ARIA [role] that require children to contain a specific [role] have all required children: Interactive groups contain all the child elements they need to work correctly.
- Elements with role="dialog" or role="alertdialog" have accessible names: Dialog boxes have labels so screen readers can describe their purpose.
- Elements with the role=text attribute do not have focusable descendents: Text groupings do not hide interactive elements from screen readers.
- Elements with visible text labels have matching accessible names: A button or link's visible label matches what screen readers announce.
- Form elements have associated labels: Form fields have labels so screen readers can identify them.
- Heading elements appear in a sequentially-descending order: Page headings follow a logical order without skipping levels.
- Identical links have the same purpose: Links to the same destination have consistent text across the page.
- Image aspect ratio: Images display at their intended proportions.
- Image elements do not have [alt] attributes that are redundant text: Image alt text does not duplicate the surrounding visible text.
- Image elements have [alt] attributes: Images have descriptive alt text or are marked as decorative.
- Input buttons have discernible text: Input buttons have labels so screen readers can describe their action.
- Links are distinguishable without relying on color: Links in body text are visually distinct from surrounding text, not by color alone.
- Links have a discernible name: Links have unique, descriptive text so users know where they go.
- List items (<li>) are contained within <ul>, <ol> or <menu> parent elements: List items are nested inside a valid parent list element.
- Lists contain only <li> elements and script supporting elements (<script> and <template>): Lists use correct markup so screen readers can announce them properly.
- No element has a [tabindex] value greater than 0: The page uses natural keyboard tab order without manual overrides.
- No form fields have multiple labels: Each form field has only one label so screen readers announce it correctly.
- Select elements have associated label elements: Dropdown menus have labels so screen readers can identify them.
- Skip links are focusable: Skip links are visible and reachable by keyboard so users can bypass navigation.
- Tables have different content in the summary attribute and <caption>: Table captions and summaries have different content.
- Tables use <caption> instead of cells with the [colspan] attribute to indicate a caption: Tables use the caption element to label their content.
- The document does not use <meta http-equiv="refresh">: The page does not use automatic refresh or redirect tags.
- The page contains a heading, skip link, or landmark region: The page has a skip link so keyboard users can bypass repeated navigation.
- Touch targets have sufficient size and spacing: Buttons and interactive elements are large enough to tap easily on touch screens.
- Uses ARIA roles only on compatible elements: Accessibility roles are only applied to elements that support them.
- Valid doctype: The page has a doctype declaration so browsers render it correctly.
Policy and guidance that supports web accessibility for people with disabilities. Guidance: Web Content Accessibility Guidelines (WCAG).
How sites score
All sites by accessibility grade
Share of the 6,097 fully scanned sites in each grade band
- A (90 to 100): 3,567 (59%)
- B to C (70 to 89): 2,404 (39%)
- D to F (below 70): 126 (2%)
| Grade band | Sites |
|---|---|
| A (90 to 100) | 3,567 |
| B to C (70 to 89) | 2,404 |
| D to F (below 70) | 126 |
Where sites fail
The most common accessibility failure is Links have a discernible name: 38% (2,322 of 6,097 sites) fail it.
Highest and lowest scores
Highest accessibility scores
| Rank | Site | Checks passed | Grade |
|---|---|---|---|
| 1 |
handbook.data.ca.gov
|
27 of 27 checks pass | A |
| 1 |
stopfraud.ca.gov
|
31 of 31 checks pass | A |
| 1 |
waterchallenge.data.ca.gov
|
27 of 27 checks pass | A |
| 1 |
projectresources.cdt.ca.gov
|
30 of 30 checks pass | A |
| 1 |
data.ca.gov
|
30 of 30 checks pass | A |
Lowest accessibility scores
| Rank | Site | Checks passed | Grade |
|---|---|---|---|
| 48 |
leo.gov
Department of Justice |
5 of 11 checks pass | F |
| 49 |
spinkcounty-sd.org
Spink County, SD |
8 of 18 checks pass | F |
| 50 |
newhire-reporting.com
Administration for Children and Families |
5 of 12 checks pass | F |
| 51 |
cornellcollege.edu
Cornell College |
3 of 9 checks pass | F |
| 52 |
harlanonline.net
Harlan County, KY |
6 of 19 checks pass | F |
Rankings and issues
- All sites ranked by accessibility: every site with a accessibility score, 100 to a page.
- States ranked by accessibility: 42 fully scanned sites.
- Counties ranked by accessibility: 2,471 fully scanned sites.
- Cities ranked by accessibility: 212 fully scanned sites.
- Federal ranked by accessibility: 688 fully scanned sites.
- Education ranked by accessibility: 2,687 fully scanned sites.
- Pulse: how every indicator scores across all sites and each group.
- Accessibility standards and how ScanGov helps with accessibility.