Accessibility statement for this website
We report on other people's documents. It would be indefensible not to publish the same kind of report about our own site — including the parts we have not assessed.
Target standard: WCAG 2.1 Level AA.
Date of this assessment: 28 July 2026.
Scope: the two pages of this site — the home page and this statement.
What was machine-checked
Checked programmatically against the machine-decidable subset of WCAG 2.1 AA, in a browser, on the date above. Every item below is reproducible by anyone with developer tools open.
| Check | Criterion | Result |
|---|---|---|
| Page language declared | 3.1.1 | Pass |
| Page has a descriptive title | 2.4.2 | Pass |
| Skip-to-content link present and functional | 2.4.1 | Pass |
| Heading levels in order, none skipped | 1.3.1 | Pass |
| Every link has an accessible name | 2.4.4 | Pass |
| No images without alternative text | 1.1.1 | Pass — this site uses no images |
| No unlabelled icons or decorative graphics | 1.1.1 | Pass — this site uses no icons |
| Tables use header cells with scope | 1.3.1 | Pass |
| Text resizes to 200% without loss | 1.4.4 | Pass — relative units throughout, no maximum-scale |
| Reflow at 320 pixels without horizontal scrolling | 1.4.10 | Pass — wide tables scroll within their own container |
| Visible keyboard focus indicator | 2.4.7 | Pass — focus outline defined and never removed |
| Reduced-motion preference honoured | 2.3.3 | Pass — no animation is used regardless |
| Body text contrast against background | 1.4.3 | Pass — measured 16.5:1 for primary text, 8.5:1 for links, 7.3:1 for secondary text. Requirement is 4.5:1. |
What a person confirmed
- The page can be operated from the keyboard alone: the skip link is the first stop, the focus ring is visible on every interactive element, and focus order follows the reading order.
- The headings describe the sections beneath them, so the page can be navigated by heading rather than read start to finish.
What was not assessed
This is the section most accessibility statements omit. These are real gaps, not formalities, and we would flag the same ones in a report about your site.
- No screen-reader session. Nobody has listened to this site with VoiceOver, NVDA or JAWS. Structure was inspected; the experience was not.
- No testing with people who use assistive technology daily. That is the only assessment that settles whether a page is usable rather than well-formed.
- Not tested at 400% zoom, nor with a browser text-size override, nor with a custom stylesheet.
- Not tested across browsers or on a physical mobile device. Checked in one desktop browser only.
- Cognitive load, reading level and plain-language quality not assessed. WCAG 2.1 AA says relatively little here and we make no claim.
- The contact address is an ordinary mailto link, not a form, so no form error-handling criteria apply — and none were tested.
What this statement is not
This is a record of tests performed on a date, not a legal conclusion. Passing every automated check above does not establish that this site meets WCAG 2.1 AA in full, because most of that standard is not machine-decidable. We would say the same about your documents, and anyone who tells you otherwise about theirs is overstating what their tooling can do.
Found a problem?
Email contact@northlinestandard.com and describe what happened and what you were using. A defect reported against this page is worth more to us than a clean audit, and we will publish the correction here with its date.