WEB DESIGN & DEVELOPMENT / A PRACTICAL ANSWER
How do you include accessibility in a website project scope?
The short answer
An accessibility scope should state the target standard, pages and interactions to be assessed, the review methods and the responsibility for fixing findings. Accessibility is broader than a single automated score. The project needs practical acceptance evidence and ongoing content responsibilities alongside its initial design work.
What to plan
Use a relevant standard such as WCAG as a reference and agree the intended scope with the responsible specialists. Include keyboard operation, form instructions, focus, content structure and representative assistive-technology checks where appropriate. Document the limits of the chosen assessment.
What to verify
Distinguish an automated scan, a manual review and a formal conformance claim. Ask how issues will be recorded, prioritised and retested. Applicable legal duties need suitable professional review; a design proposal should not casually promise universal compliance.
ILLUSTRATIVE EXAMPLE / NOT A CLIENT RESULT
Make it concrete.
A booking journey may look clear but fail when someone cannot use a mouse or needs an error explained. Including the real interaction in the assessment produces more useful evidence than checking only a static homepage.
Before you commission
- Name the standard and assessment boundaries.
- Include manual interaction checks and retesting.
- Assign ongoing content and component ownership.
A plain-text worksheet. Downloading does not send us your details.
Further reading
FROM THE QUESTION TO THE WORK
A useful next step.
Bring the decision, the existing situation and the information you have. We can help define a scope before you commit to a wider project.
Explore the relevant service