ACCESSIBILITY SERVICES
Find the barriers automated scans miss.
Manual WCAG audits for websites and web applications, combining automation, keyboard testing, screen readers, zoom and reflow, with developer-ready findings that can flow straight into remediation.
The problem this solves
You need to know which barriers exist, which users they affect, how serious they are, and what should change in the product. A scan can support that work, but the audit is the human evaluation of behavior, meaning, interaction and recovery.
Who needs this
Product teams preparing a launch or redesign
Scope, evidence and recommendations are adapted to this context.
SaaS companies answering procurement questions
Scope, evidence and recommendations are adapted to this context.
Teams that ran automated scans and need manual validation
Scope, evidence and recommendations are adapted to this context.
Organizations planning remediation or an ACR
Scope, evidence and recommendations are adapted to this context.
What we evaluate
Scope definition and representative sampling
Tested with native semantics, keyboard behavior, responsive states and assistive technology where appropriate.
Automated analysis with manual review
Tested with native semantics, keyboard behavior, responsive states and assistive technology where appropriate.
Keyboard operation and focus order
Tested with native semantics, keyboard behavior, responsive states and assistive technology where appropriate.
Screen reader behavior and announcements
Tested with native semantics, keyboard behavior, responsive states and assistive technology where appropriate.
Zoom, reflow, text spacing and responsive behavior
Tested with native semantics, keyboard behavior, responsive states and assistive technology where appropriate.
Forms, errors, semantics, ARIA and dynamic content
Tested with native semantics, keyboard behavior, responsive states and assistive technology where appropriate.
Technical examples
Focus order through dialogs, menus and route changes
Findings include evidence, impact, fix guidance and verification steps.
Accessible names for controls whose visible label changes by state
Findings include evidence, impact, fix guidance and verification steps.
Status messages after filtering, saving or validation
Findings include evidence, impact, fix guidance and verification steps.
Text alternatives that match the purpose of images and icons
Findings include evidence, impact, fix guidance and verification steps.
Methodology
Test
Define scope and evaluate representative workflows.
Find
Record barriers with reproducible evidence.
Explain
Connect issues to user impact and technical criteria.
Fix
Recommend source-level remediation.
Verify
Retest fixes and update status.
Deliverables
Audit report with scope, environments and methodology
Prepared for product, design, engineering and QA conversations.
Issue inventory with stable IDs, severity and WCAG references
Prepared for product, design, engineering and QA conversations.
Developer-ready reproduction steps and remediation guidance
Prepared for product, design, engineering and QA conversations.
Walkthrough call and optional retesting
Prepared for product, design, engineering and QA conversations.
Related resources
Digital Accessibility Compliance Calendar
Major upcoming and already-in-force accessibility dates, with official sources.
Audit before a deadline
What a technical accessibility audit should cover before a compliance date.
FAQ
Is this only automated testing?
No. Automated tools are used because they are fast and repeatable, but the audit centers on manual operation, assistive technology testing and technical review.
Do you only audit, or can you fix the issues too?
Both. You can take the audit as documented, prioritized remediation guidance, or add remediation so we implement or support the code-level fixes within the agreed scope and retest the result where technically possible.
Which WCAG version do you test against?
WCAG 2.2 Level AA is the default target unless a contract or policy requires another version.
Can this feed a VPAT or ACR?
Yes, if that is scoped before testing so the work covers the criteria and documentation needed for the report.
Audit, fix, verify.
Tell us about your website or application, the scope and your accessibility goals. We'll recommend an approach — audit only, or audit plus remediation — and send a written proposal.