Begin with semantic headings, labels, contrast, keyboard testing, focus states, alt text and error identification. Treat automated scans as aids, not proof of conformance.
Improve access by building clear structure, keyboard support, visible focus, useful alternatives and understandable forms. This page answers one narrow question first, then explains the checks needed before you act on the answer.
Search data source: Google Keyword Planner, India, English, Sep 2025 to Aug 2026. These are planning estimates, not promised traffic.
Why this matters
Improve access by building clear structure, keyboard support, visible focus, useful alternatives and understandable forms.
Begin with semantic headings, labels, contrast, keyboard testing, focus states, alt text and error identification. Treat automated scans as aids, not proof of conformance.
Action plan
Begin with semantic headings, labels, contrast, keyboard testing, focus states, alt text and error identification. Treat automated scans as aids, not proof of conformance.
- Can every action be used by keyboard? Write the answer in the brief and connect it to this outcome: Begin with semantic headings, labels, contrast, keyboard testing, focus states, alt text and error identification. Treat automated scans as aids, not proof of conformance.
- Are labels and errors programmatically connected? Check the answer against this practical situation: A placeholder is not a durable form label because it disappears during entry. A visible label helps more users understand and correct the field.
- Does zoom break the task? Name the owner, the evidence they must keep and the date when the decision will be reviewed.
| Step | Decision question | Evidence to keep |
|---|---|---|
| 1 | Can every action be used by keyboard? | Begin with semantic headings, labels, contrast, keyboard testing, focus states, alt text and error identification. Treat automated scans as aids, not proof of conformance. |
| 2 | Are labels and errors programmatically connected? | A placeholder is not a durable form label because it disappears during entry. A visible label helps more users understand and correct the field. |
| 3 | Does zoom break the task? | Named owner, source record and review date |
Worked example
A placeholder is not a durable form label because it disappears during entry. A visible label helps more users understand and correct the field.
Checks before you commit resources
- Can every action be used by keyboard?
- Are labels and errors programmatically connected?
- Does zoom break the task?
- Who will take the next action on accessibility?
- For Accessible Service Websites: A Practical WCAG 2.2 Starting Point, what result will show that the plan worked?
Begin with semantic headings, labels, contrast, keyboard testing, focus states, alt text and error identification. Treat automated scans as aids, not proof of conformance.
Mistakes to avoid
- Starting work before answering: Can every action be used by keyboard?
- Relying on an assumption instead of checking: Are labels and errors programmatically connected?
- Launching without a clear answer to: Does zoom break the task?
References and further reading
For technical benchmarks, use web.dev Core Web Vitals and W3C WCAG 2.2. Internal links follow Google link best practices. Check the date, location and original source before using any number in a business decision.
Common questions
Can every action be used by keyboard?
Begin with semantic headings, labels, contrast, keyboard testing, focus states, alt text and error identification. Treat automated scans as aids, not proof of conformance.
Are labels and errors programmatically connected?
A placeholder is not a durable form label because it disappears during entry. A visible label helps more users understand and correct the field.
Does zoom break the task?
Begin with semantic headings, labels, contrast, keyboard testing, focus states, alt text and error identification. Treat automated scans as aids, not proof of conformance. Keep the first test small enough to learn from, then expand only when the result is clear.
The short version
- Make the offer easy to understand on a phone.
- Give the visitor one obvious next step.
- Test the form, speed and tracking before sending traffic.
Meet Neha. Neha runs a travel company in Pune. Customers keep asking questions that the website should answer. On a phone, the contact button is hard to find. Neha uses this guide to fix one clear path first, instead of rebuilding everything in a panic.
This is a made-up example to explain the idea. It is not a client result.
Check the real mobile journey
This panel is specific to Accessible Service Websites: A Practical WCAG 2.2 Starting Point.
Reference: web.dev performance guidance
Use this for Accessible Service Websites: A Practical WCAG 2.2 Starting Point
| Check | Question | Proof to keep |
|---|---|---|
| Clarity | Can a new visitor understand the offer? | A five-second mobile test |
| Action | Is the main button easy to find and tap? | A completed form test |
| Delivery | Does the enquiry reach the right person? | A recorded test lead |
Words made simple
- CTA
- The button or link that tells a visitor what to do next.
- Responsive
- A page that fits and works well on phones, tablets and computers.
- CMS
- The tool used to update website text and images.
Check the page on a real phone
Tick only what is true today. This is a decision aid, not a performance promise.
Related Website Development guides
Continue with the Website Development learning hub.
- Core Web Vitals for Business Owners
- Website Project Scope Checklist Before You Request Quotes
- Website Content Architecture for Service Businesses
- Explore Jodbrain’s related services
Need help with Accessible Service Websites: A Practical WCAG 2.2 Starting Point?
Begin with semantic headings, labels, contrast, keyboard testing, focus states, alt text and error identification. Treat automated scans as aids, not proof of conformance.
Talk to Jodbrain