Interaction
Review keyboard operation, focus, controls, and task sequences.
Digital product accessibility services
Find barriers that prevent people from reading, navigating, or completing product tasks. ACW reviews agreed journeys and specifies changes to content, interaction, and implementation against a defined accessibility target.
Contact UsIdentify the barriers in important tasks
Accessibility requirements can also affect procurement. The technical assessment needs a stated version, conformance level, and coverage before its findings can be interpreted.
Blocked actions
Controls or navigation cannot be operated with the required input method.
Missing assistive information
Labels, names, states, or structure are not exposed appropriately to assistive technology.
Unclear content
Hierarchy, instructions, contrast, or feedback make information difficult to perceive or understand.
Recurring defects
Inaccessible shared components reproduce the same difficulty across screens and releases.
Address design and implementation together
From assessment to verified remediation
- 01.
Set the scope
Identify pages, journeys, states, devices, technologies, and the accessibility target.
- 02.
Evaluate
Combine relevant tool checks with knowledgeable manual review. Record reproducible barriers and their effect on tasks.
- 03.
Prioritize and resolve
Agree design, content, and engineering changes, their owners, and implementation scope.
- 04.
Verify
Recheck agreed fixes in the implemented product and record remaining issues and coverage limits.
What you receive
Findings tied to affected screens, tasks, and applicable criteria.
Prioritized remediation recommendations and component specifications.
Implemented fixes where development is included.
Verification findings, unresolved issues, and guidance for subsequent changes.
Shared patterns can reduce repeated defects, but each new feature and content change still needs review. A limited assessment does not establish whole-product conformance.
An assessment example, not a client case.
Illustrative engagement scenario
A user cannot finish a form with a keyboard. The scope examines focus order, control behavior, validation messages, and completion feedback. Findings identify reproducible issues; verification repeats the affected task after the agreed fixes are implemented.
Questions before an accessibility engagement
Which WCAG version and level do you evaluate?
Agree the target and evaluation coverage before work starts. Different procurement or product requirements may specify different versions or levels.
Is an automated scan enough?
No. Tools identify some issues. Manual evaluation is required to assess aspects such as interaction behavior and whether information supports the task.
Does this certify legal compliance?
The engagement provides technical findings and agreed remediation. Legal interpretation, certification, or formal procurement attestations require their own explicitly defined process.
Start with the journeys that must be accessible
Share the product, intended users, target requirements, and any existing audit or procurement findings.