Accessibility checks across 32 pages and both themes
Implemented WCAG 2.2 Level AA checks across 32 representative pages
in both colour themes, with a conformance record, one AAA criterion
checked and the partial result for criterion 1.4.13 stated
explicitly.
August 2026

Situation. A consultancy that sells engineering judgement and ships
an inaccessible website has a credibility problem before it has an
accessibility one. The site also has an unusually wide surface for
it: three languages, two colour themes, a full print stylesheet, a
dark‑first palette, hand‑drawn annotations and an illustrated
character — every one of which is a way to fail a criterion in one
configuration while passing it in another.

Task. The site had to conform to WCAG 2.2 at Level AA across every
page, every language and both themes, and the conformance had to be
defended by checks rather than asserted in a document.

Action. A conformance record documents every criterion in scope,
each row naming what satisfies it and what checks it. One Level AAA
criterion is taken beyond the target: visual presentation, in full.
Focus appearance is offered rather than claimed, because its
contrast over the photograph cannot be proven. The automation runs
an accessibility rule engine with its best‑practice rules enabled
rather than only the conformance ones, which is a thirty‑rule
difference and mattered immediately: one of the extra rules failed
the moment it was switched on, because the brand mark sat outside
every landmark on every inner page. A second, slower check runs
thirty‑two representative pages across two colour schemes and two
widths, and what it asserts is unusual: focus is proven in pixels
rather than in the document, by pressing the tab key for real and
comparing screenshots, because identical pixels mean the user cannot
tell where focus is regardless of what the markup says. It also
walks the whole page looking for a keyboard trap, applies the
specified text‑spacing overrides, doubles the root font size, and
measures line length, justification, centring and paragraph spacing.

Result. The conformance record documents the checks and their scope:
32 representative pages, both themes and the stated viewport
samples. It identifies WCAG 2.2 criterion 1.4.13 as only partly met
and records that testing with real assistive technology has not been
established. That is evidence of implemented accessibility checks
and known limits, rather than complete Level AA conformance across
every configuration.

Categories:
1Frontend Engineering	/categories/frontend/	software.engineer.company	70
1Web Development	/categories/web-development/	software.engineer.company	70
1Testing & QA	/categories/testing/	software.engineer.company	70
1Design Systems & UI	/categories/design-systems/	software.engineer.company	70
1UX / UI Design	/categories/ux-ui/	software.engineer.company	70
1Internationalization	/categories/i18n/	software.engineer.company	70
1Documentation	/categories/documentation/	software.engineer.company	70

Services:
1Frontend Development	/services/frontend-development/	software.engineer.company	70
1Website Development & CMS	/services/web-development/	software.engineer.company	70
1AI Agent Readiness	/services/ai-agent-readiness/	software.engineer.company	70
1UI/UX Design & Design Systems	/services/ui-ux-design/	software.engineer.company	70
1Internationalization & Localization	/services/i18n-localization/	software.engineer.company	70

hThis page on the web	URL:https://software.engineer.company/portfolio/a-site-that-meets-the-accessibility-standard/	software.engineer.company	70
