Accessibility
Website Accessibility Checklist for Business Websites (WCAG Basics)
Updated 7 November 2026·10 min read·MeraSEO, Mumbai
Most business websites are built and approved on a large screen by people who can see well, use a mouse and hear audio. Then a customer with low vision, a broken wrist, a screen reader or just a phone in bright sunlight tries to book an appointment, and the site quietly stops working for them. You rarely hear about it, because those visitors leave.
This checklist covers the WCAG 2.2 level AA basics in plain terms. For each area you get what to check, how to test it for free and the usual fix. It is written for site owners and the people who manage their sites, not for auditors.
WCAG (Web Content Accessibility Guidelines) is the international standard published by the W3C. It has three conformance levels: A (the minimum), AA (the usual target) and AAA (very strict, not expected for whole sites). Version 2.2 added a handful of criteria on top of 2.1, mainly about touch targets, focus visibility, dragging and logging in. You can read the official overview on the W3C WCAG page.
The guidelines are organized around four ideas: content must be perceivable, operable, understandable and compatible with different browsers and assistive tools. The checklist below follows how you would actually work through a site.
Test: paste your hex values into any contrast checker, or use the color picker in Chrome DevTools, which shows the ratio and whether it passes.
Every meaningful image needs a short text alternative that says what the image is for. A product photo gets the product name and a distinguishing detail. A logo that links home gets “MeraSEO home”. Decorative images (background flourishes, dividers) get an empty alt attribute (alt=””) so screen readers skip them.
Avoid “image of” and keyword stuffing. If an image contains text, such as a banner offer, repeat that text in the alt or put it in real page text instead. Charts need a sentence stating the conclusion, or a data table nearby.
Page builders often pick heading tags for their size. If a “heading” is just bold text in a div, it is invisible to assistive tools. Choose the tag for structure and use CSS for size.
Everything you can do with a mouse must work with the keyboard alone: menus, dropdowns, sliders, accordions, modals, carousels and forms. Put your mouse aside and press Tab through the page.
While tabbing, you should always see where you are. The common failure is a stylesheet rule that removes the outline (outline: none) without replacing it. WCAG 2.2 also adds that the focused element must not be completely hidden behind a sticky header, cookie bar or chat widget. Check by tabbing to links near the bottom of the page with a sticky element on screen.
Forms are where accessibility problems cost you leads directly.
Link text should make sense out of context, because screen reader users often list all links on a page. “Read more” repeated ten times tells them nothing. Write “Read our SEO pricing guide” instead. Buttons need names too: an icon-only WhatsApp or menu button needs an accessible name such as aria-label=”Chat on WhatsApp”.
Also check that links and buttons actually go somewhere. On our own site, a crawl of about 230 pages found 286 links pointing to “#” or “javascript:void(0)”, mostly page-builder widgets whose link field was left at its default. They are a problem for every visitor, and doubly so for keyboard and screen reader users, who land on a control that does nothing.
Touch targets matter on phones. WCAG 2.2 sets a minimum target size of 24 by 24 CSS pixels (with some exceptions), and larger is kinder to thumbs.
A properly built responsive layout gets you most of this for free. See our notes on responsive web design.
| Problem found | Where to fix it | Typical effort |
|---|---|---|
| Low-contrast text or buttons | Theme color settings, global CSS | Low |
| Missing form labels, vague errors | Form plugin or template | Low to medium |
| Menu not usable by keyboard | Header template or theme code | Medium |
| Missing alt text | Media library, per image | Low, but repetitive |
| Whole design depends on tiny tap targets or fixed widths | Layout, usually part of a redesign | High |
The Rights of Persons with Disabilities Act, 2016 is the main disability-rights law in India, and it includes provisions about accessibility of information and communication technology. Government websites and apps are guided by GIGW, the Guidelines for Indian Government Websites and Apps, which build on WCAG. The current guidance is published at guidelines.india.gov.in. If you build for a government body, a public institution or a regulated entity, check which version of GIGW and which accessibility requirements your contract cites. For a private business, requirements vary by sector and contract, so ask a qualified lawyer if you need to know your legal exposure. Either way, WCAG 2.2 AA is a sensible common target.
Practical India notes: many users are on mid-range Android phones with outdoor glare, so contrast and target size help far more people than just those with a diagnosed disability. Hindi and Marathi pages need the correct lang attribute and fonts that render conjuncts properly.
Accessibility is cheapest when it is part of the design brief. When we plan a website redesign or UI/UX website design, contrast, focus styles, form patterns and heading structure get decided in the design system, so developers inherit them instead of patching each page later. The general usability side is covered in our post on UX design principles; this post stays with the standards-level checks.
Most organizations aim for WCAG 2.2 level AA. It covers contrast, alt text, keyboard operation, form labels, headings, zoom and captions. Level A alone leaves many barriers in place, and level AAA is not expected across a whole site. If you serve government clients, also check the GIGW guidance they cite.
No. Tools like Lighthouse, axe and WAVE reliably catch missing alt attributes, low contrast and unlabeled fields, but they cannot judge whether alt text is meaningful or a menu is usable by keyboard. Use them first, then test by tabbing through the site and listening with a screen reader.
Not reliably. A script that adds a toolbar to your page cannot repair missing labels, broken focus order or poor structure in the underlying code. Some can even interfere with the screen readers people already use. Fix the source code and templates, and treat any widget as an optional extra.
Indirectly. Descriptive headings, alt text, link text, page titles and a clean structure also help search engines understand a page, and faster, mobile-friendly layouts help everyone. It is not a ranking trick, but the work overlaps with good on-page practice.
Tell us your site address and we will point out the template-level fixes that matter most, then build them into the design.
Talk to our design team →WhatsApp us