Our target
We build to WCAG 2.2 Level AA and treat it as an engineering constraint rather than an annual audit. On client platforms we run automated checks in CI, keyboard and screen-reader passes on every significant release, and a manual review against the success criteria before launch.
This site is held to the same standard. It uses semantic landmarks, a visible focus ring on every interactive element, a skip link, and colour contrast ratios that meet AA throughout. Motion is suppressed for visitors who have asked their operating system to reduce it.
How we test
- Automated linting with axe-core against every page and component state, failing the build on violations.
- Keyboard-only traversal of each template, recorded as part of the release checklist.
- Screen-reader passes with VoiceOver (macOS and iOS) and NVDA (Windows) on primary user journeys.
- Zoom to 200% and 400% reflow checks on every template.
- Contrast and colour-independence review on charts, badges and status indicators.
What we cannot promise
Accessibility is a property of content as much as code. An editor who uploads an image with no alt text, or pastes a heading in the wrong order, can reintroduce a barrier that engineering fixed. This is why we train editorial teams as part of the handover, and why the CMS blocks uploads that would break the standard.
We also do not claim conformance for third-party components we do not control — payment iframes, embedded video players, chat widgets. We choose accessible ones and report where a third party limits us.
Found a barrier?
Tell us what you were trying to do, which page you were on and which browser or assistive technology you were using. We treat accessibility reports as defects, not feedback, and we aim to respond within two working days.
If a part of this site is unusable for you, email{" "}hello@mcginnpublishing.com with the page address and we will work with you to get you the information another way.
Questions
This is a demonstration document for a demonstration build, written to show how editorial pages are structured. In a live deployment this would be reviewed by your counsel. For anything real, write to hello@mcginnpublishing.com.