Showing Arizona county sites. All U.S. county sites
B 89
Average accessibility score of 10 fully scanned Arizona county sites
7th
of 49 states, ranked by average accessibility score
10 of 14
Sites fully scanned. We couldn't fully scan 4, so they're listed without grades
B 88
U.S. county average accessibility score, 2467 fully scanned sites
Arizona's state site, az.gov, could not be fully scanned. State rankings.
How Arizona county accessibility scores are distributed
Smoothed distribution of the 10 fully scanned Arizona county sites, score 0 to 100. Height shows how many sites score near each value.
Distribution of 10 scores. The data table lists counts by score range.
- Arizona average
- U.S. county 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 | 0 |
| 50 to 59 | 0 |
| 60 to 69 | 0 |
| 70 to 79 | 1 |
| 80 to 89 | 5 |
| 90 to 100 | 4 |
Arizona counties by accessibility grade
Each county with a site on our list is colored by that site's grade. Select a county to open its report. The table lists every site.
- A (90 to 100)
- B to C (70 to 89)
- D to F (below 70)
- Not fully scanned
- No site on our list
Arizona counties by accessibility grade, compared with all U.S. counties
Share of fully scanned sites in each grade band. Arizona: 10 sites. U.S.: 2467 sites.
- 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) |
|---|---|---|---|
| Arizona | 40% (4) | 60% (6) | 0% (0) |
| All U.S. counties | 49% (1,201) | 49% (1,197) | 3% (69) |
Top 3 Arizona county sites by accessibility score
#1 in Arizona · U.S. rank 1
Yavapai County, AZ
A 100 accessibility
- Accessibility A
- Botability A
- Security A
- Usability C
- Readability A
#2 in Arizona · U.S. rank 3
Mohave County, AZ
A 96 accessibility
- Accessibility A
- Botability A
- Security A
- Usability B
- Readability F
#3 in Arizona · U.S. rank 8
Pima County, AZ
A 91 accessibility
- Accessibility A
- Botability C
- Security B
- Usability B
- Readability -
What each check means
- 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.
- Heading elements appear in a sequentially-descending order. Page headings follow a logical order without skipping levels. Keyboard users cannot efficiently navigate your site.
- [aria-hidden="true"] elements do not contain focusable descendents. Interactive elements are not hidden from screen reader users. Keyboard users can focus elements that screen readers cannot announce.
- 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.
- 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. Screen readers cannot navigate grouped elements like menus or lists.
All Arizona county sites by accessibility score
| Rank | Site | Checks passed | Grade |
|---|---|---|---|
| 1 |
yavapaiaz.gov
Yavapai County, AZ U.S. rank 1 |
32 of 32 checks pass | A |
| 2 |
mohave.gov
Mohave County, AZ U.S. rank 3 |
30 of 31 checks pass | A |
| 3 |
pima.gov
Pima County, AZ U.S. rank 8 |
33 of 36 checks pass | A |
| 4 |
coconino.az.gov
Coconino County, AZ U.S. rank 9 |
29 of 32 checks pass | A |
| 5 |
greenlee.az.gov
Greenlee County, AZ U.S. rank 10 |
25 of 28 checks pass | B |
| 5 |
navajocountyaz.gov
Navajo County, AZ U.S. rank 10 |
35 of 39 checks pass | B |
| 6 |
cochise.az.gov
Cochise County, AZ U.S. rank 11 |
31 of 35 checks pass | B |
| 7 |
maricopa.gov
Maricopa County, AZ U.S. rank 14 |
30 of 35 checks pass | B |
| 8 |
lapaz.gov
La Paz County, AZ U.S. rank 15 |
27 of 32 checks pass | B |
| 9 |
gilacountyaz.gov
Gila County, AZ U.S. rank 23 |
23 of 30 checks pass | C |
|
apachecountyaz.gov
Apache County, AZ |
Not fully scanned, so not graded. We couldn't scan your site because it showed our bot a captcha or browser check instead of the page. Status 996 | - | |
|
graham.az.gov
Graham County, AZ |
Not fully scanned, so not graded. We couldn't scan your site because it showed our bot a captcha or browser check instead of the page. Status 996 | - | |
|
pinal.gov
Pinal County, AZ |
Not fully scanned, so not graded. We couldn't scan your site because it showed our bot a captcha or browser check instead of the page. Status 996 | - | |
|
santacruzcountyaz.gov
Santa Cruz County, AZ |
Not fully scanned, so not graded. We couldn't scan your site because it showed our bot a captcha or browser check instead of the page. Status 996 | - |
About accessibility
Meet WCAG standards so every type of user can use your website.
Why it's important
People with disabilities need equal access to information and services online.
Risks
- People with disabilities cannot use your site.
Guidance
What we use to grade accessibility:
Standards
- [accesskey] values are unique
- [aria-*] attributes match their roles
- Uses ARIA roles only on compatible elements
- button, link, and menuitem elements have accessible names
- ARIA attributes are used as specified for the element's role
- Deprecated ARIA roles were not used
- Elements with role="dialog" or role="alertdialog" have accessible names
- [aria-hidden="true"] is not present on the document <body>
- [aria-hidden="true"] elements do not contain focusable descendents
- ARIA input fields have accessible names
- ARIA meter elements have accessible names
- ARIA progressbar elements have accessible names
- Elements use only permitted ARIA attributes
- [role]s have all required [aria-*] attributes
- Elements with an ARIA [role] that require children to contain a specific [role] have all required children
- [role]s are contained by their required parent element
- [role] values are valid
- Elements with the role=text attribute do not have focusable descendents
- ARIA toggle fields have accessible names
- ARIA tooltip elements have accessible names
- ARIA treeitem elements have accessible names
- [aria-*] attributes have valid values
- [aria-*] attributes are valid and not misspelled
- Buttons have an accessible name
- The page contains a heading, skip link, or landmark region
- Background and foreground colors have a sufficient contrast ratio
- <dl>'s contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements
- Definition list items are wrapped in <dl> elements
- Document has a <title> element
- ARIA IDs are unique
- No form fields have multiple labels
- <frame> or <iframe> elements have a title
- Heading elements appear in a sequentially-descending order
- <html> element has a [lang] attribute
- <html> element has a valid value for its [lang] attribute
- <html> element has an [xml:lang] attribute with the same base language as the [lang] attribute
- Image elements have [alt] attributes
- Image elements do not have [alt] attributes that are redundant text
- Input buttons have discernible text
- <input type="image"> elements have [alt] text
- Form elements have associated labels
- Links are distinguishable without relying on color
- Links have a discernible name
- Lists contain only <li> elements and script supporting elements (<script> and <template>)
- List items (<li>) are contained within <ul>, <ol> or <menu> parent elements
- The document does not use <meta http-equiv="refresh">
- [user-scalable="no"] is not used in the <meta name="viewport"> element and the [maximum-scale] attribute is not less than 5
- <object> elements have alternate text
- Select elements have associated label elements
- Skip links are focusable
- No element has a [tabindex] value greater than 0
- Tables have different content in the summary attribute and <caption>
- Touch targets have sufficient size and spacing
- Cells in a <table> element that use the [headers] attribute refer to table cells within the same table
- <th> elements and elements with [role="columnheader"/"rowheader"] have data cells they describe
- [lang] attributes have a valid value
- <video> elements contain a <track> element with [kind="captions"]
- All heading elements contain content
- Identical links have the same purpose
- Document has a main landmark
- Elements with visible text labels have matching accessible names
- Tables use <caption> instead of cells with the [colspan] attribute to indicate a caption
- <td> elements in a large <table> have one or more table headers
- Image aspect ratio
- Valid doctype
- Character encoding
Grades/scores
ScanGov
About this ranking
About this data
ScanGov scans the homepage of each county site on our county list in Arizona. Scores come from the checks in the ScanGov standards. Sites were scanned between 10/27/2026 and 11/3/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 4 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.