Skip to main content

Accessibility audit plan

Evaluate the web application using WCAG-EM against WCAG 2.2 Level AA.

Scope

The scope is the Hephaestus SPA at one tested commit and deployment, including:

  • public, authenticated, loading, empty, error and permission-denied states;
  • authentication, workspace creation, developer feedback, mentor and settings processes;
  • workspace and instance administration for every supported role; and
  • Hephaestus controls and presentation around imported content.

Linked sites and identity-provider pages are outside the application scope. The handoff to and return from those pages remain in scope.

Surface inventory

SurfaceRepresentative routes and states
Public and legal/, /about, /imprint, /privacy, not found
Authentication/login, workspace login, callback and error
Workspace creationprovider selection, GitHub, GitLab, validation and errors
Workspace homedashboard, teams, achievements and user profiles
Developer feedbackreviews, trace, observations, feedback delivery and targets
Mentorthread list, greeting, transcript, composer and copilot
Personal settingssettings, integrations and destructive actions
Workspace administrationmembers, practices, review operations, models, usage and integrations
Instance administrationusers, workspaces, audit, catalogue, providers, models and usage

The dated audit record expands this inventory to the routes, states and roles present in the tested revision.

Evaluation

Record the revision, deployment, test data, tester, date, and exact operating-system, browser and assistive-technology versions.

  1. On every surface, use only the keyboard to check operation, focus visibility and order, skip navigation, overlay dismissal and focus restoration, and keyboard traps.
  2. On every surface, inspect landmarks, headings, names, roles and states with NVDA and Firefox on Windows and VoiceOver and Safari on macOS. Complete every end-to-end process in both combinations, including validation and error recovery.
  3. Build the structured and random samples required by WCAG-EM. Across those samples, evaluate every applicable Level A and AA criterion, including 200% zoom, 320 CSS-pixel reflow, text spacing, contrast, use of colour, target size and motion. Record the results with the WCAG-EM Report Tool.
  4. Run axe on the integrated sampled pages and reconcile its results with the manual evaluation.

Findings and completion

Link every failure to an issue with its context, reproduction steps, expected and observed behaviour, user impact, environment, applicable WCAG criterion and evidence. Use GitHub assignment, priority and milestones for ownership and scheduling. Check other callers when the failure is in a shared component.

pnpm --filter webapp run test:storybook runs axe against the maintained Storybook states in Chromium. Retain its report, revision and browser version with the audit, and document any rule exclusions.

An AA conformance claim requires every scoped page and complete process to pass every applicable Level A and AA criterion. Follow W3C's conformance-claim requirements when updating the public accessibility statement.