Accessibility

Website Accessibility Checklist for Business Websites (WCAG Basics)

Website Accessibility Checklist for Business Websites (WCAG Basics): MeraSEO article cover
Key takeaways
  • WCAG 2.2 level AA is the practical target for a business site. Most failures come from the same few areas: low contrast, missing alt text, unlabeled form fields, broken keyboard use and vague links.
  • Automated tools catch only part of the problems. You also need ten minutes of keyboard-only testing and a pass with a screen reader.
  • Fix templates first (header, menu, forms, buttons). One fix there repairs every page that uses it.
  • In India, the Rights of Persons with Disabilities Act 2016 and the GIGW guidelines for government sites are the reference points. Treat this post as practical guidance, not legal advice.

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.

What WCAG is and which level to aim for

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.

The checklist

1. Text and color contrast

  • Normal body text needs a contrast ratio of at least 4.5:1 against its background. Large text (roughly 24 px, or 19 px bold) needs 3:1.
  • Icons, input borders and button outlines that you need in order to understand the interface need 3:1 against their surroundings.
  • Light grey placeholder text and pale-green-on-white buttons are the most common failures.
  • Do not use color alone to carry meaning. A red border on an invalid field also needs an error message in text.

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.

2. Images and alt text

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.

3. Headings and page structure

  • One H1 describing the page, then H2s for sections and H3s beneath them, without skipping levels for visual styling.
  • Use real landmarks: header, nav, main, footer. Screen reader users jump between them.
  • Give every page a unique, descriptive title.
  • Set the page language (for example lang=”en” or lang=”hi”) so the screen reader pronounces text correctly. Mark inline passages in another language too.

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.

4. Keyboard use

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.

  • The tab order should follow the visual order.
  • Menus must open with Enter or arrow keys, not hover only.
  • A modal must trap focus while open, close with Escape and return focus to the button that opened it.
  • Offer a “Skip to main content” link as the first focusable item so keyboard users do not tab through 30 menu links on every page.

5. Visible focus

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.

6. Forms and labels

Forms are where accessibility problems cost you leads directly.

  • Every field has a visible label connected to it in the code. Placeholder text is not a label, since it disappears when typing.
  • Mark required fields in a way that does not rely on color: write “(required)” or explain the asterisk at the top of the form, and add the required attribute in the code.
  • Error messages say what is wrong and how to fix it (“Enter a 10-digit mobile number”), appear near the field and are announced to screen readers.
  • Do not make people retype information they already entered in the same flow, and avoid logins that depend on solving a puzzle or transcribing characters with no alternative.

7. Links and buttons

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.

8. Zoom, reflow and text spacing

  • The page must remain usable when text is enlarged to 200% in the browser.
  • At a width equivalent to 320 CSS pixels (a 400% zoom on a desktop window), content should reflow into one column without sideways scrolling, except for things like data tables and maps.
  • Never disable pinch zoom with a viewport setting such as user-scalable=no.
  • Content must survive users increasing line, letter and word spacing without text being clipped.

A properly built responsive layout gets you most of this for free. See our notes on responsive web design.

9. Video, audio and motion

  • Prerecorded video with speech needs captions. Auto-generated captions are a starting point; correct them, especially names and Hinglish.
  • Provide a transcript for podcasts and other audio-only content. If a video shows important information only visually (on-screen steps, a product demo with no narration), level AA expects audio description: a narrated version, or narration written into the main audio track so the visuals are spoken.
  • Do not autoplay sound. Carousels and animations that move for more than five seconds need a visible pause control.
  • Avoid content that flashes more than three times a second.

How to test: a 30-minute routine

  1. Run an automated scan. Lighthouse in Chrome DevTools, the axe browser extension or the WAVE tool will flag contrast, missing alt text, missing labels and heading problems. Treat a clean score as “no obvious errors”, not “accessible”.
  2. Tab through the home page and one key form. Note any place you lose focus, cannot see focus or cannot operate something.
  3. Zoom to 200%, then shrink the window to a phone width. Look for overlapping text and sideways scrolling.
  4. Turn on a screen reader for five minutes. NVDA is free on Windows, VoiceOver is built into macOS and iPhone, and TalkBack is built into Android. Listen to the header, the main menu and your contact form. If you cannot tell what a control does with your eyes closed, neither can a user.
  5. Log the findings against the table below and fix the shared templates first.
Problem foundWhere to fix itTypical effort
Low-contrast text or buttonsTheme color settings, global CSSLow
Missing form labels, vague errorsForm plugin or templateLow to medium
Menu not usable by keyboardHeader template or theme codeMedium
Missing alt textMedia library, per imageLow, but repetitive
Whole design depends on tiny tap targets or fixed widthsLayout, usually part of a redesignHigh

The Indian context

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.

Where accessibility fits in a redesign

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.

Frequently asked questions

What is the minimum accessibility standard for a business website?

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.

Can an automated tool tell me if my site is accessible?

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.

Do accessibility overlay widgets fix my site?

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.

Does accessibility help SEO?

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.

Want an accessibility review before your next redesign?

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 →

Related Post

Call Now Button