How to run a 5-page accessibility spot check on a government website

A spot check tells a government web team, in about half a day, whether its site has obvious accessibility barriers. It samples 5 pages, runs quick manual and automated checks, and logs each failure so the next step is clear.

Short answer: To spot check a government website, pick 5 pages that cover your main page types and one complete task, then run about 10 quick checks on each: page title, headings, image text, contrast, zoom, keyboard, focus, forms, media and moving content. Log every failure with the page, the WCAG criterion and an owner, and treat the result as a first look, not an audit.

Sources: W3C, Easy Checks; W3C, WCAG-EM 2.0.

State and local governments must meet WCAG 2.1 Level AA under the ADA Title II web rule. Governments serving 50,000 or more people must comply by April 26, 2027. Smaller governments and special district governments must comply by April 26, 2028.

A spot check will not prove you meet that standard. It shows where the biggest barriers are, so you can plan and budget the real work.

Sources: ADA.gov fact sheet; Federal Register, Interim Final Rule of April 20, 2026.

What is an accessibility spot check?

An accessibility spot check is a short, structured review of a few pages using simple manual tests and an automated scanner. It finds obvious barriers fast. It does not cover every WCAG success criterion, so a page that passes can still have serious problems that only a full evaluation or user testing would find.

The W3C says its own Easy Checks "cover just a few accessibility issues" and are "designed to be quick and easy, rather than definitive." It also warns that a page "could seem to pass these checks, yet still have significant accessibility barriers."

So use the spot check to answer one question: is there clear work to do, and where does it start?

Source: W3C, Easy Checks: A First Review of Web Accessibility.

Which 5 pages should you pick?

Pick pages that represent the site, not the 5 you like most. The W3C evaluation method, WCAG-EM, asks for common views, essential functions, a variety of page types and every step of a complete process. A good 5-page set for a government site follows the same logic on a smaller scale.

WCAG-EM defines common views as those "relevant to the entire digital product," such as the home page, login and other entry points, contact, help and legal pages. It says a sample set "has to include all pages or views that belong to a series presenting a complete process." It also asks for pages that "vary in style, layout, structure, navigation, interaction, and visual design."

For most city, county and state sites, these 5 cover that ground:

  1. Home page. It carries the shared header, menu, footer and search.
  2. A high-traffic service page. For example trash pickup, property tax or a permit overview. This is a typical content template.
  3. A form. A service request, contact form or job application.
  4. A document or media page. A page listing agendas, PDFs or meeting videos.
  5. One step of a transaction. A payment, permit or registration screen, even if a vendor hosts it.

Source: W3C, WCAG Evaluation Methodology (WCAG-EM) 2.0, Group Note, July 23, 2026.

What do you check on each page?

Run the same 10 checks on every page so results compare cleanly. Most need only a browser and a keyboard. Start with an automated scanner to catch the easy failures, then do the manual checks, because the W3C says tools "can not determine accessibility, they can only assist in doing so."

The 10 checks below follow the topics in W3C Easy Checks and map to WCAG 2.1 success criteria.

10 spot checks and the WCAG 2.1 criteria they relate to
CheckHow to do itRelated WCAG 2.1 criterion
1. Page titleRead the browser tab. It should briefly describe the page.2.4.2 Page Titled (A)
2. HeadingsList the headings with a browser extension. They should outline the page in order.1.3.1 Info and Relationships (A)
3. Image textCheck that each meaningful image has useful alt text and decorative ones are skipped.1.1.1 Non-text Content (A)
4. ContrastTest body text and buttons with a contrast tool. Normal text needs at least 4.5:1.1.4.3 Contrast (Minimum) (AA)
5. Zoom and reflowZoom to 200%, then narrow the window to 320 CSS pixels. Nothing should be cut off or need side scrolling.1.4.4 Resize Text (AA); 1.4.10 Reflow (AA)
6. KeyboardPress Tab through the page. Every link, field, button and player control must be reachable and usable.2.1.1 Keyboard (A)
7. Visible focusWhile tabbing, you should always see where focus is.2.4.7 Focus Visible (AA)
8. FormsEach field has a visible label. Submit with errors and check that each error is described in text.3.3.1 Error Identification (A); 3.3.2 Labels or Instructions (A)
9. MediaPlay a video with sound off. Speech should appear as captions.1.2.2 Captions (Prerecorded) (A)
10. Moving contentCarousels or auto-playing items that last more than 5 seconds need a way to pause, stop or hide them.2.2.2 Pause, Stop, Hide (A)

Sources: W3C, Easy Checks; W3C, WCAG 2.1; W3C, Understanding Reflow; W3C, Selecting Web Accessibility Evaluation Tools.

Worked example: a 5-page spot check on a county website

This example shows the method on a made-up county site. It is a plan and a log format, not a report of real findings. A web team can copy the structure and fill in its own pages.

Budget about 45 minutes per page for the 10 checks and notes, plus time to set up and write up. That is our planning estimate, not a W3C figure. Your time will vary with page length.

Example spot check plan for a county website
PageWhy it is in the sampleChecks to focus on
Home pageShared header, menu, search and footer appear on every pageKeyboard, visible focus, moving content, page title
Property tax service pageTypical content template used across departmentsHeadings, contrast, zoom and reflow, image text
Report a pothole formEssential function residents use without helpForms, keyboard, error messages
Board meetings pageAgendas, PDFs and recorded videoMedia captions, link text, document links
Online payment stepPart of a complete process, often vendor hostedKeyboard, forms, visible focus, zoom

Log each failure as one row. Use the same columns every time so the log can become a backlog later:

  • Page: the URL and the page name.
  • Check and criterion: for example "6. Keyboard, 2.1.1".
  • What happened: one plain sentence, plus a screenshot.
  • Shared or local: does it come from a template used on many pages?
  • Severity: blocks a task, makes it hard, or is minor.
  • Owner: the web team, a department or a vendor.

An example row could read: "Report a pothole form. 8. Forms, 3.3.1. Error says 'invalid input' with no field named. Local. Makes it hard. Web team." The point is that anyone can pick up the row and act on it.

What do you do with the results?

Sort the log by severity, then by shared versus local. A failure in a shared template, such as the header or a form component, repeats on every page that uses it, so one fix clears many pages. Fix those first, then the tasks residents cannot finish.

Next, decide whether you need a full evaluation. WCAG-EM sets out 5 steps: define the scope, explore the product, select a representative sample, evaluate the sample and report the findings. A spot check gives you a head start on the first 3.

Also check what the rule excludes before you plan fixes. ADA.gov lists exceptions such as archived web content and preexisting documents that meet set conditions. Content a government posts through its vendors or contractors is not exempt, which is why the payment step belongs in the sample.

Sources: W3C, WCAG-EM 2.0; ADA.gov fact sheet.

What this means for subcontractors

Primes bidding on state and local web work can use a spot check to scope effort before pricing. The 5-page log shows the agency what was tested, what failed and which fixes are shared, which makes a remediation plan easier to defend.

We test and remediate to WCAG 2.1 AA as a subcontractor to primes. See our accessibility and software development services and how to subcontract with Konnex. For a longer test list, read the WCAG 2.1 AA checklist for government websites. For dates, read ADA Title II web rule deadlines, and for documents see how to remediate PDFs.

Quick answers

Is a 5-page spot check enough to show WCAG 2.1 AA conformance?

No. The W3C says quick checks are not definitive and a page can pass them yet still have significant barriers. Use a full evaluation of a representative sample for conformance.

Can an automated scanner replace the manual checks?

No. The W3C says tools cannot check all accessibility aspects automatically and that human judgement is required.

Should a vendor-hosted payment page be in the sample?

Yes. ADA.gov says content a government posts through its vendors or contractors is not exempt, and WCAG-EM asks for every step of a complete process.

Sources: W3C, Easy Checks; W3C, Selecting Web Accessibility Evaluation Tools; ADA.gov fact sheet; W3C, WCAG-EM 2.0.

Sources

This is general information, not legal advice.

Want a second pair of eyes on a state or local web project? Contact Konnex to talk it through.