The City of Halliday is committed to making this website usable by everyone, including residents with disabilities. This page explains the standard we build to, how the site is tested, what those tests can and cannot tell you, and how to reach us if something here does not work for you.
The standard we build to
We build and maintain this site against the Web Content Accessibility Guidelines, version 2.1, at Level AA. Those guidelines are written by the World Wide Web Consortium, the body that sets the technical standards of the web, and they rest on four ideas: that content must be perceivable, operable, understandable and robust. At Level A and Level AA together, a page is measured against 50 separate requirements.
A newer version, 2.2, was published in October 2023 and adds nine further requirements. It does not replace 2.1 or make it obsolete; the two share the same foundation, and anything that meets 2.2 also meets 2.1. We name 2.1 Level AA here because that is the version this site is actually measured against every month, and we would rather publish the standard we test than the newest one on the shelf.
What we do when we build a page
Every page is built with real headings in the right order, so screen-reader software can move through it by structure instead of guesswork. Text is sized to stay readable when it is enlarged, and every text and background pairing is checked so the words stand out from what is behind them. Links say where they go rather than saying “click here.” Form fields carry labels that stay visible while you type. Nothing on this site uses color alone to carry meaning, so a notice is never distinguished only by being red. Every page works down to a phone-sized screen without sideways scrolling, and tables that are too wide to fit scroll on their own instead of pushing the page out of shape.
How this site is tested
Once a month every page on this site is scanned with axe-core, an open-source accessibility testing engine. The scan runs 62 rules drawn from the Level A and Level AA rule set, and it runs on each page twice: once at a desktop screen width and once at a phone width of 375 pixels, because a problem can exist at one size and not the other. Each page is sampled twice after it loads and then loaded again as a returning visitor, since some things only appear on a second visit. Anything the scan flags is checked a third time in a clean browser session before it is recorded. The report for each scan lists every page it covered and exactly what was found there.
What an automated scan cannot tell you
An automated scan is a measurement, not a verdict. Research published by Deque, the company behind axe-core, put automated coverage at about 57 percent of accessibility problems — measured across more than two thousand audits and roughly three hundred thousand individual issues. The rest need a person. A scan can confirm that an image carries alternative text; it cannot tell you whether that text describes the picture. It can confirm that a heading exists; it cannot tell you whether the wording is clear.
The engine also returns results it cannot decide either way, which it marks as needing review, and each of our reports says how many it found. Those are neither failures nor passes — they are the places a human review would look first.
We have not published a keyboard-only or screen-reader review of this site, and a passing scan is not a substitute for one. We do not claim this site satisfies every requirement. What we publish is what was actually measured, on the dates it was measured.
Scan history
This site is re-scanned every month against the WCAG 2.1 Level A & AA rule set using axe-core, an open-source accessibility engine. Every scan that came back a complete pass — no violations, and every page in scope actually measured — is published here, newest first; each one opens a report listing the pages it covered.
A scan that finds something is not published on this page — it is held for our team to review. So this list is the record of this site’s passing scans, not of every scan we have run.
If something here does not work for you
Tell us, and we will help you directly while we fix it. If you can, say which page you were on and what happened — but you do not need to know the technical reason, and you will never be asked to explain your disability or prove anything. We can also provide anything published on this site in another format, including large print, plain text or read to you over the phone. City Hall, 131 Main Street East, Halliday, ND 58636 · (701) 938-4680.