Cost and scope guide
Accessible UX Scope and Cost Drivers
Accessible UX Scope and Cost Drivers organizes the decisions that matter for organizations improving websites and applications for disabled users: the current workflow, ownership, implementation choices, rollout risk, and acceptance evidence.
Working artifact
Accessible UX ownership matrix
Complete the owner and evidence columns before implementation so access and maintenance do not become hidden project risks.
| System or capability | Owner question | Evidence to retain |
|---|---|---|
| WCAG-informed manual and automated review | Who approves changes affecting WCAG-informed manual and automated review? | Current export, access record, and acceptance result for accessibility audits and prioritized remediation |
| Semantic HTML, ARIA, focus, and error handling | Who approves changes affecting semantic HTML, ARIA, focus, and error handling? | Current export, access record, and acceptance result for keyboard, focus, screen-reader, and form repair |
| Cross-device assistive-technology testing | Who approves changes affecting cross-device assistive-technology testing? | Current export, access record, and acceptance result for accessible design-system and content guidance |
The five largest scope drivers
Keyboard users cannot complete essential journeys. Confirm who encounters it, where it occurs, and what changed before it appeared. Then distinguish the visible symptom from dependencies such as WCAG-informed manual and automated review.
- Accessibility audits and prioritized remediation
- Keyboard, focus, screen-reader, and form repair
- Semantic HTML, ARIA, focus, and error handling
- Cross-device assistive-technology testing
- Responsive and accessible web application delivery
What makes an estimate more reliable
For Accessibility Remediation & Inclusive UX, confirm account ownership, current exports or backups, recovery options, and recent changes before touching production. Preserve exact errors and timestamps that may disappear after a restart or update.
- Current-system inventory
- Representative user journeys
- Known constraints and deadlines
- Named decision owner
When phasing helps
Frame the first scope around accessibility audits and prioritized remediation and one observable acceptance journey. Treat keyboard, focus, screen-reader, and form repair as a later phase unless the evidence shows it is a true dependency.
- Phase 1: evidence and risk control
- Phase 2: smallest useful outcome
- Phase 3: measured expansion
Estimate preparation checklist
Repair fits when the core remains sound. Extension fits when the boundary around WCAG-informed manual and automated review is understood. Replacement fits when ownership, architecture, or operating risk prevents a responsible change.
- Desired result
- Systems and vendors involved
- Access owner
- Examples and errors
- Definition of done