← Back to Knowledge Base

KNOWLEDGE / 15

Accessibility testing

WCAG 2.2 AA, semantics, keyboard use, contrast, reflow, manual audits and automated checks with links to primary sources.

01 / 3

Standards, semantics and perception

What does WCAG 2.2 Level AA mean, and what does a high Lighthouse score not prove?Junior

Answer

WCAG 2.2 is a W3C Recommendation with testable success criteria. Level AA includes the applicable Level A and AA criteria for pages and complete processes in a defined scope. First identify routes, states, languages, technologies and exceptions; then gather evidence criterion by criterion. An automated score is a useful signal but cannot assess every keyboard journey, the meaning of alternative text or actual assistive-technology behaviour.

  • The criterion, its level and applicability matter more than a tool's overall score.
  • Do not call a site certified after axe or Lighthouse alone; WAI recommends combining automated and manual methods.

Primary sources

Examples

  • A page scoring 95/100 can still have no mobile navigation; a scanner is not guaranteed to catch that.

Practice exercises

  1. Define an audit scope covering routes, EN/UA states, 320 CSS px, keyboard use and one real VoiceOver journey.
How do you check semantic structure and language on a bilingual page?Junior

Answer

Start with native HTML: one meaningful H1, a logical heading hierarchy, main, nav and header outside main, useful names for interactive elements, and image alt text appropriate to purpose. The html lang attribute should match the primary language of the displayed content; when the client switches EN/UA, update it together with the text. Consider lang on individual phrases in another language. Do not add ARIA when a native element already provides the required role and behaviour.

  • The DOM reading order should remain understandable without CSS.
  • The lang attribute affects screen-reader pronunciation; an empty lang is not a neutral solution.

Primary sources

Examples

  • A language control changes the text to Ukrainian, but html still says lang=en: the check is not complete.

Practice exercises

  1. On a blog page, inspect H1, main/nav, link names and html lang before and after switching language.
Which contrast ratios matter for text, controls and focus?Junior

Answer

For normal text, SC 1.4.3 Level AA requires at least 4.5:1, and for large text 3:1. SC 1.4.11 generally requires 3:1 for meaningful control boundaries and states, including a focus indicator against adjacent colours. Calculate the ratio for actual normal, hover, active and focused states; a bright-looking green outline is not necessarily distinguishable on white. Read the normative criteria for exceptions and the definition of large text.

Primary sources

Examples

  • A #88ad00 outline on white has about 2.62:1 contrast, insufficient for a meaningful indicator under 1.4.11.

Practice exercises

  1. Check card text, a select boundary and a focus outline on light and dark backgrounds; record colour pairs and ratios.

02 / 3

Keyboard, reflow and components

How should you test a keyboard journey, navigation and disclosures without unnecessary ARIA?Middle

Answer

Follow Tab and Shift+Tab, activate links with Enter, buttons with Enter/Space, and native selects with browser keys. Check visible focus, logical order, no trap, and that hidden controls do not enter the tab order. Native details/summary fits a simple disclosure; do not label it an ARIA menu without implementing the richer keyboard pattern. After switching language or opening a panel, confirm focus is not lost.

Primary sources

Examples

  • CSS hides desktop navigation at 320px without a mobile replacement: a perfect tab order among the remaining controls does not restore missing routes.

Practice exercises

  1. Without a mouse, open the mobile navigation, traverse every link, close it, change language and download the selected resume.
What should you check at 320 CSS px, with enlarged text and minimum target sizes?Middle

Answer

SC 1.4.10 requires most vertically scrolling content to remain available without two-dimensional scrolling at a width equivalent to 320 CSS px; certain inherently two-dimensional parts have exceptions. Check not just document.scrollWidth but missing functionality, clipped buttons, panels and long words in both languages. WCAG 2.2 SC 2.5.8 sets a 24×24 CSS px minimum target or defined exceptions, including sufficient spacing. Distinguish the actual hit area from the visible icon.

Primary sources

Examples

  • An arrow icon may be 16×16 px while its entire link row is 44 px high; assess the link bounding box, not the glyph.

Practice exercises

  1. Inspect home, a long article and the resume panel at 320px; record horizontal scrolling and the smallest target rectangles.
How do you assess alt text, video and forms beyond checking a box?Middle

Answer

Alt text conveys an image's purpose in context: informative images need useful alternatives, decorative ones an empty alternative. For video, check operable controls, captions for synchronised speech and other applicable criteria. A form label must name its field programmatically, while errors identify the field and how to fix it; colour must not be the sole signal. If no form or video exists, mark the criterion not applicable to the current scope, but assess a reusable component before it is used later.

Primary sources

Examples

  • Repeating the visible caption 'Oleksandr Doroshenko' in a portrait alt may be redundant; the decision depends on whether the portrait adds meaning.

Practice exercises

  1. Review each project content-block type and explain which require manual content judgment rather than only an attribute-presence check.

03 / 3

Audit, automation and ownership

How do you make an accessibility audit reproducible and write defensible findings?Senior

Answer

Define complete processes and a matrix of routes, languages, viewports, states, browsers and assistive technologies. For each finding record a stable ID, criterion and level, affected users, steps, actual/expected result, evidence, severity, owner and status. Group automated nodes by root cause: 70 html nodes without lang are one systemic defect, not 70 independent bugs. Separate confirmed failures from manual hypotheses and not-applicable criteria; do not conceal uncertainty behind a Lighthouse score.

Primary sources

Examples

  • A report assigns one root cause to a repeated header component and attaches a 35-route × 2-language coverage list as evidence.

Practice exercises

  1. Write a finding for disappeared mobile navigation with WCAG mapping, severity, evidence, uncertainty and a post-fix check.
How do you add axe/Playwright to CI without creating false confidence?Senior

Answer

Build and serve the real production output, wait for HTTP readiness, and assert the intended route, title/H1 and absence of an error page before axe. Scan each relevant route, EN/UA and critical viewports; open interactive states before scanning. On failure print rule, impact, target and help URL, and preserve JSON, screenshots and traces. Gate on an agreed severity; make exceptions narrow with owner, reason and expiry. CI does not replace keyboard/VoiceOver checks or judgment of alt-text meaning.

Primary sources

Examples

  • A test that accidentally scans a 404 instead of the intended page may return zero violations, so assert the H1 before axe.

Practice exercises

  1. Design a CI job with build, local server, readiness, route matrix and evidence-artifact upload.
How should residual risks and an accessibility statement be managed after release?Senior

Answer

Maintain known limitations, owners, priorities and verified workarounds; do not call a product fully accessible without evidence for the full scope. An accessibility statement can describe the target standard, a way to report barriers and known issues, but its wording and any legal claims require approval. After release, collect concrete user reports, retest changed routes and monitor temporary-exception expiry. A better score is supporting evidence, not a release gate by itself.

Primary sources

Examples

  • A team says it assessed WCAG 2.2 AA criteria on defined routes but still has an open VoiceOver check for a video block; it does not hide that limitation.

Practice exercises

  1. Prepare an exception register with owner, reason, impact, temporary workaround, review date and closure evidence.