Ask for semantic HTML, keyboard access, visible focus, labels, error handling, contrast, zoom support and manual testing against agreed WCAG 2.2 criteria.
Put practical accessibility requirements into the brief, proposal and acceptance test before development begins. Use the questions below during planning, review and approval. Do not mark an item complete without evidence.
Search data source: Google Keyword Planner, India, English, Sep 2025 to Aug 2026. These are planning estimates, not promised traffic.
The decision behind this topic
Put practical accessibility requirements into the brief, proposal and acceptance test before development begins.
Use the questions below during planning, review and approval. Do not mark an item complete without evidence.
Action plan
Ask for semantic HTML, keyboard access, visible focus, labels, error handling, contrast, zoom support and manual testing against agreed WCAG 2.2 criteria.
- Which WCAG level is required? Write the answer in the brief and connect it to this outcome: Ask for semantic HTML, keyboard access, visible focus, labels, error handling, contrast, zoom support and manual testing against agreed WCAG 2.2 criteria.
- Who performs manual testing? Check the answer against this practical situation: A vendor saying “the scanner passed” is not enough. Automated tools cannot test every keyboard, focus or comprehension issue.
- How are defects fixed after launch? Name the owner, the evidence they must keep and the date when the decision will be reviewed.
| Step | Decision question | Evidence to keep |
|---|---|---|
| 1 | Which WCAG level is required? | Ask for semantic HTML, keyboard access, visible focus, labels, error handling, contrast, zoom support and manual testing against agreed WCAG 2.2 criteria. |
| 2 | Who performs manual testing? | A vendor saying “the scanner passed” is not enough. Automated tools cannot test every keyboard, focus or comprehension issue. |
| 3 | How are defects fixed after launch? | Named owner, source record and review date |
Worked example
A vendor saying “the scanner passed” is not enough. Automated tools cannot test every keyboard, focus or comprehension issue.
For “Website Accessibility Procurement Checklist”, replace the example assumptions with your own audience, constraints and approval evidence before using the method.
Working checklist
- Which WCAG level is required?
- Who performs manual testing?
- How are defects fixed after launch?
- Who owns the next action for accessibility?
- Which evidence for “Website Accessibility Procurement Checklist” will be reviewed, and on which date?
Ask for semantic HTML, keyboard access, visible focus, labels, error handling, contrast, zoom support and manual testing against agreed WCAG 2.2 criteria.
Mistakes to avoid
- Treating “Website Accessibility Procurement Checklist” as a generic deliverable instead of a specific business decision.
- For “Website Accessibility Procurement Checklist”, avoid this: Approving screens before content, accessibility and measurement requirements are clear.
- For “Website Accessibility Procurement Checklist”, avoid this: Launching without testing forms, redirects, analytics and mobile paths.
- For “Website Accessibility Procurement Checklist”, do not use an example or number without recording its source, context and approval.
Sources and data rules
For technical benchmarks, use web.dev Core Web Vitals and W3C WCAG 2.2. Internal links follow Google link best practices. A keyword number is published only when it matches the exact topic, location and date range, and its source is named.
Questions to answer
Which WCAG level is required?
Ask for semantic HTML, keyboard access, visible focus, labels, error handling, contrast, zoom support and manual testing against agreed WCAG 2.2 criteria. Start by writing a direct answer to “Which WCAG level is required?” and the evidence that would change that answer.
Who performs manual testing?
Test the answer against a real situation. A vendor saying “the scanner passed” is not enough. Automated tools cannot test every keyboard, focus or comprehension issue. Record where your situation is different before copying the approach.
How are defects fixed after launch?
Assign one owner and one review date for “How are defects fixed after launch?”. Keep the brief, test result and final decision together so the next review uses evidence.
Related Website Development guides
Part of the Website Development learning hub.
- Website Launch QA Checklist: Content, SEO, Analytics and Mobile
- Landing Page Message Match for Paid Campaigns
- Mobile Website Usability Audit for Lead Generation
- Explore Jodbrain’s related services
Need help applying this practical checklist?
Ask for semantic HTML, keyboard access, visible focus, labels, error handling, contrast, zoom support and manual testing against agreed WCAG 2.2 criteria. Bring your current brief, evidence and constraints to the conversation.
Talk to Jodbrain