
Key takeaways
- Accessibility means people with different abilities, devices and situations can use your site. WCAG is the common standard to follow.
- Start with the basics: readable contrast, full keyboard use, clear headings, text alternatives, labelled forms and visible focus.
- Add automated checks, but also test by hand with a keyboard and a screen reader, because tools catch only part of the problems.
- Treat accessibility as part of design and development from the start, not a late audit.
What accessibility means
Accessibility is about making your website usable by as many people as possible: users with visual, hearing, motor or cognitive disabilities, people on small screens or slow connections, and anyone using a site in bright sunlight or with one hand. The Web Content Accessibility Guidelines, known as WCAG, are the widely used standard. They are organised around four ideas: content must be perceivable, operable, understandable and robust. Many accessibility improvements also help usability and search visibility, because they make structure and content clearer.
The checklist
- 1Contrast: normal text should have a contrast ratio of at least 4.5 to 1 against its background, and large text at least 3 to 1.
- 2Keyboard use: every link, button and form control must be reachable and usable with the keyboard alone, in a logical order.
- 3Visible focus: users must see which element is focused. Never remove the focus outline without a clear replacement.
- 4Headings: use one main heading and a logical hierarchy, so screen reader users can navigate by section.
- 5Text alternatives: meaningful images need descriptive alt text, and decorative images should have empty alt text.
- 6Forms: every input needs a visible label, clear instructions and error messages that explain how to fix the problem.
- 7Links and buttons: use descriptive text, not just “click here”, and make touch targets large enough to tap.
- 8Colour: never use colour alone to convey meaning, such as red for errors with no text or icon.
- 9Motion: let users pause or avoid animations, and respect the reduced-motion setting.
- 10Language: set the page language and mark language changes, which matters for Arabic and English pages.
- 11Media: provide captions for videos and transcripts for audio.
- 12Zoom and reflow: content should stay usable when zoomed and on narrow screens without horizontal scrolling.
Quick checks you can do today
| Check | How to do it |
|---|---|
| Keyboard test | Unplug the mouse and tab through the page; can you do everything and always see focus? |
| Zoom test | Zoom to 200 percent; does anything overlap, disappear or need sideways scrolling? |
| Contrast test | Use a contrast checker on text, buttons and form borders. |
| Heading outline | List the headings only; does the page still make sense? |
| Screen reader pass | Use a built-in screen reader on one key task, such as sending the contact form. |
| Automated scan | Run a free accessibility checker to catch the obvious issues, then fix them. |
Accessibility for Arabic and bilingual sites
Set the language attribute correctly on each page and on fragments in the other language so screen readers pronounce text properly. Make sure the reading order matches the visual order in right-to-left layouts, and that focus moves in the expected direction. Test with Arabic content, because contrast and font size can behave differently with Arabic letterforms. Our guide on Arabic UI design covers the layout details.
A worked example
A small business site passes a quick visual check but fails a keyboard test: the mobile menu opens only on click, focus disappears on buttons and the contact form shows errors only in red. The team makes the menu keyboard operable, restores visible focus, adds text to error messages, labels each field and adds alt text to product images. None of this changes the look much, yet the form becomes usable for people who cannot use a mouse. This is an illustrative scenario, not a client story, but these are typical findings.
Mistakes to avoid
- Relying on an automated score alone. Tools cannot judge whether alt text is meaningful or a flow makes sense.
- Adding an accessibility overlay widget instead of fixing the underlying code.
- Removing outlines for a cleaner look.
- Using images of text for headings or buttons.
- Leaving accessibility to a final audit, when fixes are most expensive.
Next step
Fold these checks into your build with our UX design process and the web app security checklist, explore our UI/UX design service, or contact us for an accessibility review.
Frequently asked questions
What is WCAG?
The Web Content Accessibility Guidelines are a widely used set of recommendations for making web content accessible. They are organised around making content perceivable, operable, understandable and robust.
Can an automated tool make my site accessible?
No. Tools find many common issues but cannot judge meaning, such as whether alt text is useful. Combine automated scans with manual keyboard and screen reader testing.
Does accessibility help SEO?
Often indirectly. Clear headings, text alternatives, descriptive links and fast, well-structured pages help both people and search engines understand your content.

