← Back to the City of Dodge, North Dakota accessibility page
Monthly accessibility scan
https://cityofdodge.com · scanned 2026-09-14
PASS — no violations found by the automated rules that were run
Every page listed below was tested against the WCAG 2.1 Level A & AA using axe-core 4.13.0, an open-source accessibility engine. Automated testing catches many WCAG failures; it does not replace a manual review, and a PASS here means no violation was found by the rules that were run, not that the site meets every WCAG criterion.
The number of pages covered changed. This scan covered 19 pages. The previous scan (September 11, 2026) covered 18 pages — that is 1 page more this time. The added pages were measured against the same rules as the rest.
This is the rule set the engine reported for this scan. It was recorded once, from the first page measured, and the same rule set was run against every page listed below; the list is not a per-page record of which rules found something to check on that page.
"Individual checks passed" counts passing axe checks (rule x element) on each page's desktop sample; one viewport per page, not summed across viewports.
10 checks could not be decided automatically. The automated rules looked at them and could not tell, on their own, whether they pass — the usual reason is text sitting on an image, a gradient or a transparent background, where the engine cannot read the real color behind the text. They are counted here, are not counted as a violation and are not counted as a passing check; the rule involved is color-contrast. Deciding them needs a person to look. Axe checks (rule x element) that the automated rules could not decide either way, counted once per element over both screen widths and every sample.
Every page listed below was tested at desktop 1280x800 and mobile 375x812. A page can pass on a desktop and fail on a phone, so a result from one screen width alone is not a pass. A report only carries this PASS when every page was measured at both widths.
Each page was sampled 3 times (first visit ~0.6s after load; first visit ~3.5s after load; second visit (reload, same browser) ~0.6s after load). Every finding retested on a fresh visit (new context, cold storage); findings that did not reproduce are KEPT and counted as intermittent violations.
What this measurement does not cover: automated point-in-time measurement of a first and a second visit at two screen widths; content shown only under other conditions (time of day, location, third or later visits, server-side variants) or appearing outside the sample windows is not covered; automated checks do not replace a manual review.
Excluded from the scan scope: the published accessibility scan reports under /reports/accessibility/ are not scanned, so this scan makes no claim about those pages.
| Page | Checks passed | Violations | Undecided |
|---|---|---|---|
| / | 201 | None | 0 |
| /about/ | 160 | None | 0 |
| /accessibility/ | 159 | None | 0 |
| /auditorium/ | 163 | None | 0 |
| /community/ | 143 | None | 0 |
| /contact/ | 191 | None | 4 |
| /dump-ground/ | 212 | None | 3 |
| /elections/ | 153 | None | 0 |
| /events/ | 289 | None | 0 |
| /government/ | 199 | None | 1 |
| /health/ | 142 | None | 0 |
| /library/ | 164 | None | 0 |
| /meetings/ | 176 | None | 0 |
| /news/ | 144 | None | 0 |
| /ordinances/ | 142 | None | 0 |
| /parks/ | 170 | None | 0 |
| /privacy/ | 148 | None | 0 |
| /services/ | 213 | None | 2 |
| /terms/ | 153 | None | 0 |