Website accessibility means building a site that people can use whatever their abilities, devices or situation. That includes people who are blind, deaf, color blind, or unable to use a mouse, and it also helps anyone using a phone in bright sunlight. This guide explains the WCAG standard in plain English, the checks you can run today, and the legal and business reasons to care. Also, it covers color contrast and the European Accessibility Act.
Quick answer: Aim for WCAG 2.2 level AA. In practice, that means text with enough color contrast (4.5:1 for normal text), a text alternative for every meaningful image, a page that works with a keyboard alone, labelled form fields, clear headings and a page language. Start with the free checks in this guide, fix the most common failures first, then test with a keyboard and a screen reader. Many problems are cheap to fix, so website accessibility is one of the best returns on a small amount of work, and this guide shows you where to begin.
What is website accessibility and why does it matter?
Website accessibility is the practice of designing and coding pages so that people with disabilities can perceive, understand, navigate and interact with them. The W3C Web Accessibility Initiative explains the idea on its accessibility fundamentals pages, and its standard is the Web Content Accessibility Guidelines, or WCAG.
There are three practical reasons to care about website accessibility:
- More customers can use your site. First, people with permanent, temporary or situational limits all benefit, for example someone with a broken arm or someone watching a video on a noisy train.
- It overlaps with SEO. Also, clear headings, descriptive links, alt text and fast pages help search engines too. Our on-page SEO checklist covers many of the same basics.
- It reduces legal risk. Finally, some countries now require it for certain businesses, as the section on the European Accessibility Act below explains.
What is WCAG 2.2 and which level should you target?
WCAG is organised around four principles, often shortened to POUR: content must be perceivable, operable, understandable and robust. Each guideline has success criteria at three levels: A, AA and AAA. Most laws and contracts ask for level AA, so that is the sensible target for a business site. In other words, you do not need to chase level AAA everywhere.
According to the W3C's WCAG overview, WCAG 2.2 became a W3C Recommendation on 5 October 2023 and was updated on 12 December 2024. It is backwards compatible, so a page that meets 2.2 also meets 2.1 and 2.0, with one exception: criterion 4.1.1 Parsing is obsolete and was removed. The same page notes that WCAG 2.2 is also the international standard ISO/IEC 40500:2025, and that WCAG 3 is still an early draft.
As of November 2026, the nine criteria that WCAG 2.2 added include these, as listed on the W3C's page on what is new in WCAG 2.2:
| New criterion | Level | What it asks for |
|---|---|---|
| 2.4.11 Focus Not Obscured (Minimum) | AA | A focused item is not completely hidden by sticky headers or banners |
| 2.5.7 Dragging Movements | AA | Anything that needs dragging also works with a simple click or tap |
| 2.5.8 Target Size (Minimum) | AA | Click and tap targets are at least 24 by 24 CSS pixels, with exceptions |
| 3.2.6 Consistent Help | A | Help links or contact options stay in the same place across pages |
| 3.3.7 Redundant Entry | A | Do not make people retype information they already gave |
| 3.3.8 Accessible Authentication (Minimum) | AA | Logging in does not rely on solving a cognitive puzzle |
For the exact wording and exceptions, always check the criteria on the W3C site, because this table is only a summary.

How common are accessibility problems?
Very common. The WebAIM Million report automatically tests the home pages of the top one million websites each year. In its 2026 edition, it found WCAG 2 failures on 95.9% of home pages, with an average of 56.1 detected errors per page.
The same report lists the most common failures, and they are all fixable:
- Low contrast text on 83.9% of pages.
- Missing alternative text for images on 53.1%.
- Missing form input labels on 51%.
- Empty links on 46.3% and empty buttons on 30.6%.
- Missing document language on 13.5%.
So if you fix just these six issues, you will already be ahead of most of the web. However, automated tools only detect part of the problem, which is why manual checks matter. In short, treat a tool score as a starting point.
How do you check color contrast?
Color contrast is the difference in brightness between text and its background. Under WCAG success criterion 1.4.3, level AA needs a contrast ratio of at least 4.5:1 for normal text and at least 3:1 for large text, which means 18 point or 14 point bold and above. Logos and purely decorative text are exempt.
To check your colors, paste the text and background values into any free contrast checker. Then adjust until the ratio passes. A few habits help:
- Avoid light grey text on white. It looks elegant in a mockup but fails for many readers.
- Check text over images and gradients. Test the worst spot, not the best one.
- Do not rely on color alone. For example, mark required fields or errors with text or an icon as well as red.
- Check buttons and form borders. WCAG 1.4.11 asks for at least 3:1 contrast on interface components.
How do you write good alt text?
Alt text is a short text description of an image that screen readers read aloud. It also appears if the image fails to load. The W3C has a helpful alt decision tree that starts with one question: what is the image for?
For example, use these simple rules:
- Informative images get a brief description of what matters, such as "Chart showing website visits doubling between March and June".
- Decorative images get an empty alt attribute (alt="") so assistive technology skips them.
- Images that act as links or buttons describe the action, such as "Download the price list", not the picture.
- Images of text should be avoided, but if you must use one, the alt text repeats the words.
Avoid starting with "image of" or stuffing keywords. Instead, write for a person first, and the search benefit follows.
How do you make a site work with a keyboard?
Many people cannot use a mouse, including screen reader users and people with motor impairments. Because of this, every link, button and form field must work with the keyboard alone. The W3C's easy checks are a good starting list. Try this five-minute test on your key pages:
- Put the mouse aside and press the Tab key repeatedly.
- Confirm that you can always see where the focus is, through a visible outline.
- Check that the order makes sense, usually top to bottom and left to right.
- Make sure you can open menus, forms and pop-ups, and close them with Esc.
- Look for a "skip to main content" link as the first item.
If you cannot reach something, a screen reader user cannot reach it either. In addition, make sure sticky headers do not cover the focused item, which is the new WCAG 2.2 rule above.
What about forms, headings and page language?
Forms cause the most real-life frustration. First, every field needs a visible label that is connected to it in the code, and required fields should be clearly marked. In addition, error messages should say what went wrong and how to fix it, in text, not only in color.
Headings give the page its outline. Use one main heading, then subheadings in order, because screen reader users often jump from heading to heading. Then set the page language in the HTML, so that screen readers pronounce the text correctly. This matters especially on bilingual Thai and English sites, where a wrong language setting makes speech software read Thai with English rules.
For video, add captions. For audio, add a transcript. These steps also help people watching with the sound off.
Does the European Accessibility Act affect your business?
Possibly, if you sell to consumers in the EU. The European Accessibility Act, formally Directive (EU) 2019/882, applies to many consumer products and services, including e-commerce, banking services and e-books. Under the text on EUR-Lex, its rules cover services provided to consumers after 28 June 2025. Microenterprises that provide services, meaning fewer than 10 staff and turnover up to 2 million euros, are exempt from the service requirements.
Because national laws differ and enforcement is still developing, this is general information, not legal advice. So if you sell into the EU, ask a qualified adviser which rules apply to you. As for Thailand, the picture is less clear, so check current local rules for your sector. In any case, WCAG 2.2 AA is the benchmark most regulators and customers refer to.
A simple accessibility checklist for small businesses
Use this website accessibility checklist every time you launch or redesign a page:
- Text contrast passes 4.5:1, and large text passes 3:1.
- Every meaningful image has useful alt text, and decorative ones have empty alt.
- You can use every function with the keyboard, and the focus is visible.
- Forms have labels, clear errors and marked required fields.
- Headings are in order, link text makes sense out of context, and the page language is set.
- Videos have captions, and audio has a transcript.
- Touch targets are at least 24 by 24 CSS pixels, or have enough spacing.
- Your site has a way to contact you if someone cannot use a page.
If you use WordPress, many themes advertise accessibility support, but you still need to test them. Our guides on building a WordPress website and WordPress vs Shopify vs Wix cover platform choices, and the Core Web Vitals guide covers speed, which also helps people on slow connections.
Need help with website accessibility?
Develop Marketing helps businesses with social media, AI content, SEO, AEO and GEO, WordPress websites and advertising. If you want a second pair of eyes on your site's accessibility, see our services page (in Thai) or contact us.
Frequently asked questions
Usability is about how easy a site is for the typical user. Accessibility makes sure people with disabilities can use it too. Good sites need both, and the two overlap a lot.
It depends on your country, sector and customers. WCAG is a technical standard, not a law, but many laws and public contracts point to it. Check the rules that apply to you and consult a qualified adviser.
Not on its own. Tools can find or fix some issues, but they cannot judge whether alt text is meaningful or whether a flow works with a keyboard. Fix the underlying code and use tools as a helper.
Test every new page template, and run a full check at least once or twice a year. In addition, retest after redesigns, plugin updates or new features.
Indirectly, yes. Descriptive headings, alt text, clear link text and fast, stable pages help people and search engines understand your content. However, accessibility should be done for users first.
Final thoughts
Website accessibility is not a one-time project or a luxury. Instead, it is a habit: check contrast, write honest alt text, test with the keyboard, label forms and keep the page structure clean. Start with the six most common failures from the WebAIM data, aim for WCAG 2.2 level AA, and review new pages before you publish them. Therefore, a site that more people can use is a site that serves more customers, and good website accessibility is simply good service.










