Accessibility Review

WCAG review and remediation support with evidence a team can act on.

Accessibility work is scoped against an explicit baseline, usually WCAG 2.2 AA. Section 508 or EN 301 549 mapping can be included when procurement or policy requires it.

Request an assessment View all offers

Review Method

Accessibility review needs a target, a test path, and evidence.

The goal is a remediation path a product team can understand, estimate, implement, and retest without treating accessibility as a one-time scan report.

Manual review path

Keyboard-only operation, focus order, and visible focus
Accessible names, descriptions, headings, landmarks, and reading order
Screen reader spot checks for form flow, dynamic updates, and complex widgets
Zoom, reflow, contrast, reduced motion, and forced-colors behavior

Finding format

Severity, affected users, and affected WCAG criterion
Reproduction path, expected behavior, and observed behavior
Code-level remediation guidance and acceptance criteria
Retest status and evidence captured after remediation

Tooling boundary

Automated checks help catch regressions and obvious failures, but they do not determine accessibility by themselves. Human review remains part of the acceptance path for semantics, interaction behavior, and user impact.

Deliverables

The output should support implementation, not just reporting.

Findings are useful only when the affected workflow, acceptance path, and retest expectation are clear.

Baseline and scope

Target standard, tested workflows, browsers, assistive technology spot checks, and explicit out-of-scope areas.

Findings backlog

Prioritized issues with reproduction steps, user impact, affected criteria, implementation guidance, and acceptance criteria.

Remediation support

Code-level guidance for component patterns, forms, focus behavior, dynamic state, contrast, and semantic structure.

Retest evidence

Verification notes after remediation so the team can distinguish fixed, deferred, and newly discovered work.

Contact

Start with the workflows users need to complete.

Use the contact page to describe the application, target standard, known problem areas, and whether the work needs assessment, remediation support, or retest evidence.

Accessibility inquiries

Include the target workflows, user roles, technology stack, and any policy or procurement baseline already in play.

Request an assessment