City of Dunn website accessibility test
An automated test on October 20, 2026 detected 532 failures against WCAG 2.1 Level A and AA success criteria across 50 pages of the City of Dunn website.
- Scan date
- October 20, 2026
- Failures detected
- 532
- Pages tested
- 50
- Date in the DOJ Title II web rule
- April 26, 2028
Detected failures by severity
| Severity | Failures |
|---|---|
| Critical | 33 |
| Serious | 499 |
| Moderate | 0 |
| Minor | 0 |
Severity levels are assigned by axe-core to each failure it detects.
Detected failures by WCAG 2.1 success criterion
| Success criterion | Level | Failures |
|---|---|---|
| 1.1.1 Non-text Content | A | 8 |
| 1.4.3 Contrast (Minimum) | AA | 114 |
| 2.4.4 Link Purpose (In Context) | A | 381 |
| 4.1.2 Name, Role, Value | A | 410 |
One failure can relate to more than one success criterion, so this column can add up to more than the total.
Date in the DOJ Title II web rule
The U.S. Department of Justice rule on web content under Title II of the Americans with Disabilities Act sets April 26, 2028 as the date for public entities of this type and population tier.
Tier basis: Census population 8,754 (2024), below 50,000.
Scope and limitations
What this report is
This is an automated conformance test of publicly accessible pages on City of Dunn's website, measured against the Web Content Accessibility Guidelines (WCAG) 2.1, Level A and Level AA success criteria. It was produced on October 20, 2026 using axe-core 4.14.0, testing 50 pages.
What this report is not
This report does not determine whether City of Dunn satisfies any legal obligation. Legal determinations under the Americans with Disabilities Act or any other statute or regulation are for your legal counsel, not for an automated test, and nothing in this document should be read as a legal opinion or as advice.
Automated testing identifies a subset of accessibility barriers. Published estimates of automated coverage range from roughly 20% to 57% of issues depending on methodology and the site being tested. Categories of barrier that automated testing cannot reliably detect include, among others:
- whether alternative text is meaningful rather than merely present
- keyboard traps and illogical focus order
- whether content is usable and comprehensible with a screen reader
- accuracy and synchronization of captions and audio description
- accessibility of linked PDFs and other documents
- whether an accessible alternative conveys equivalent information
A site with zero findings in this report may still present significant barriers to users with disabilities. Manual testing and testing with assistive technology by people with disabilities are necessary to assess a site's actual usability, and no automated test substitutes for them.
No findings are a guarantee of anything. This report describes what an automated test detected on specific pages on a specific date. Website content changes continuously.
Element-level report
The full report lists each of the 532 detected failures with the page address, the element, its HTML, the success criterion, and what that criterion requires. Findings are ordered by severity and by how many pages share the same defect.
One-time purchase of $149, delivered by email link. No account or subscription.