E-commerce14 min read•

Ecommerce Website Development in Pune: Building an Accessible Online Store — WCAG 2.2 for Product Pages, Filters and Checkout, With a One-Afternoon Test Plan

How to build an online store to WCAG 2.2 AA: product cards, filters, variants, checkout errors, target size, focus and a test plan.

#ecommerce website development Pune#WCAG 2.2#accessible checkout#online store accessibility#product page

An accessible online store is one where a shopper who is blind, has low vision, uses only a keyboard, has a tremor, or is simply using a cracked phone in bright sunlight can still find a product, choose a variant and complete checkout. For ecommerce website development in Pune, the practical standard to build against is WCAG 2.2 at Level AA, the version of the Web Content Accessibility Guidelines that the W3C published as a recommendation in October 2023. This guide translates the criteria that matter most into specific work for product pages, filters, carts and checkout, with a test plan you can run in an afternoon and a way to brief your developer. It is a build guide, not legal advice; the legal position in India is summarised near the end, with pointers to the primary sources.

Why Store Accessibility Is a Revenue Question, Not Just a Compliance One

Most ecommerce teams think of accessibility as something a lawyer asks for. In practice, the same fixes help everyone:

  • Clear form labels and error messages reduce abandoned checkouts on every device.
  • Large tap targets help anyone using a phone one-handed on a Pune bus.
  • Good contrast helps everyone on a bright screen outdoors.
  • Keyboard-friendly menus and filters help power users and anyone with a broken trackpad.

India has a large population of people with disabilities, and the Rights of Persons with Disabilities Act, 2016 requires accessibility in information and communication technology. Government websites follow GIGW guidelines, which draw on WCAG. Private stores are not all bound in the same way, but marketplaces, payment providers and enterprise buyers increasingly ask for accessible interfaces, and the standard to design to is clear. We do not quote figures for "revenue lost" because such numbers are rarely sourced; treat the business case as a reasonable expectation, not a promise.

The Standard in Plain Language: WCAG 2.2 AA

WCAG is organised around four principles: content must be perceivable, operable, understandable and robust. Level AA is the usual target. WCAG 2.2 added several criteria that matter a great deal to stores:

New in 2.2 Level What it means for a store
2.4.11 Focus Not Obscured (Minimum) AA A sticky header, cookie banner or chat bubble must not completely hide the element that has keyboard focus
2.5.7 Dragging Movements AA Anything done by dragging (price slider, reorder) needs a non-dragging alternative
2.5.8 Target Size (Minimum) AA Tap and click targets should be at least 24 by 24 CSS pixels, or spaced so they do not crowd each other
3.2.6 Consistent Help A If you offer help (WhatsApp, phone, FAQ), put it in the same place on each page
3.3.7 Redundant Entry A Do not make shoppers re-type information they already gave in the same flow
3.3.8 Accessible Authentication (Minimum) AA Do not require solving a puzzle or remembering a password with no alternative at login

Older criteria still carry most of the weight, such as 1.4.3 Contrast (Minimum), which asks for a text contrast ratio of at least 4.5:1 for normal text and 3:1 for large text, and 1.1.1 Non-text Content, which requires text alternatives for images.

Product Listing and Category Pages

Product images and alt text

Every product image needs an alternative that describes what the shopper needs to know. "Blue cotton kurta, front view, mandarin collar" works; "IMG_4021.jpg" and "kurta kurta buy kurta online" do not. If several images show angles of the same product, describe the differences ("back view showing embroidery"). Decorative images (dividers, background textures) should have empty alt text so screen readers skip them. Do not stuff keywords into alt text; it harms users and counts as keyword stuffing. Our guide to image alt text and headings covers the pattern in more depth.

Headings and landmarks

Use one h1 per page (the product or category name) and h2/h3 for sections such as "Description", "Size guide" and "Reviews". Wrap navigation, main content and footer in the proper HTML landmarks (nav, main, footer) so screen-reader users can jump straight to the product list.

Product cards

A card that contains an image link, a title link and a "Quick add" button creates three tab stops for one product. Better: one link on the title, with the image either part of the same link or hidden from the accessibility tree, and the quick-add button with a specific label ("Add Blue cotton kurta to cart"). Repeated generic labels such as "Add to cart" ten times in a row give a screen-reader user no way to tell products apart.

Price and sale information

Never rely on colour or strikethrough alone to show a sale. Add text such as "Sale price" and "Original price" (visually hidden if needed) so the meaning survives for someone who cannot see the formatting.

Filters, Sorting and Pagination

Filters are where store accessibility most often fails.

  • Use real form controls. Checkboxes and radio buttons with associated label elements, not clickable div elements.
  • Announce changes. When a filter updates the product list without a page reload, tell assistive tech through an ARIA live region (for example "24 products shown"). Without this a screen-reader user hears nothing happen.
  • Provide an alternative to sliders. A price range slider fails 2.5.7 unless there are also two number inputs for minimum and maximum.
  • Keep focus sensible. After applying a filter, do not throw the keyboard focus back to the top of the page.
  • Make mobile filter drawers closable with the Escape key and a visible close button, and return focus to the button that opened them.

Pagination and "load more" buttons also need care; endlessly loading lists trap keyboard users in front of an unreachable footer. See our overview of pagination, load more and infinite scroll for the trade-offs.

The Product Page: Variants, Quantity and Add to Cart

Variant selectors

Size and colour pickers are often built as rows of coloured circles or boxes. Make sure that:

  • Each option is a radio button or a native select, with a visible label ("Size: M").
  • Colour is not conveyed by swatch colour alone. Show the name in text ("Colour: Indigo") when an option is selected.
  • Unavailable options are marked in a way that is not colour-only, and the reason is clear ("Out of stock") rather than silently disabled.
  • Each swatch meets the minimum target size of 24 by 24 CSS pixels; larger is better on phones.

If your product uses size charts, make them readable and accessible. Our guide to size charts and fit guides describes how to build them.

Quantity controls

The classic minus/plus buttons need accessible names ("Decrease quantity", "Increase quantity") and the quantity field needs a label. Let users type a number directly.

Add to cart feedback

When someone presses "Add to cart", the confirmation must reach screen-reader users: use a live-region message ("Blue cotton kurta added to cart, 1 item") or move focus to the mini-cart. A silent badge that changes from 0 to 1 is invisible to many users.

Stock and delivery information

State availability in text. "Only 2 left" should be plain text in the page, not just a red badge. For delivery checks by PIN code, label the field clearly, accept the six digits without forcing special formatting, and show a text result.

The Cart and Checkout

Checkout is where accessibility directly meets money. Work through these in order.

Labels, hints and autocomplete

Every field gets a visible label, not placeholder text alone, because placeholders disappear as people type and have contrast problems. Use proper autocomplete attributes (name, email, tel, postal-code, address-line1) so browsers and password managers can fill them. This also supports WCAG 1.3.5 Identify Input Purpose. Our checkout address form guide covers India-specific address fields.

Errors

Errors should be:

  1. Described in text, not just a red border.
  2. Linked to the field they concern.
  3. Announced to assistive technology, for instance through a summary at the top that receives focus after a failed submission, with links to each problem field.
  4. Specific: "Enter a 6-digit PIN code" rather than "Invalid input".

Redundant entry

WCAG 3.3.7 says do not make people enter the same information twice in one process. Offer a "Billing address same as shipping" checkbox, remember the details already entered if they move back a step, and do not ask for the phone number again on the payment step.

Authentication

If shoppers can create accounts, 3.3.8 means that logging in must not depend on a cognitive test such as transcribing characters from a distorted image with no alternative. Allow paste into password fields so password managers work, and offer an alternative to image puzzles. If you use OTP by SMS or WhatsApp, allow the code to be pasted and to autofill; the autocomplete="one-time-code" attribute helps on phones. Our guide to OTP login by SMS and WhatsApp covers the technical side, and this article's point is simply that a bot-protection choice should never be the thing that stops a legitimate customer. If you are weighing that, see bot protection at checkout.

Third-party payment widgets

Hosted payment pages and embedded iframes from payment providers are not under your direct control, but you choose the provider. Test their widget with a keyboard and a screen reader before you commit, and ask the provider for their accessibility conformance information. Do not accept "it's their responsibility" as an answer if your customers cannot pay.

Colour, Contrast and Typography

  • Text contrast. Aim for 4.5:1 for body text and 3:1 for large text and for important graphical elements like icon-only buttons. Use a contrast checker on your brand palette before you finalise buttons.
  • Disabled and placeholder text is often too pale. If it carries information, it needs contrast.
  • Sale badges in light red on white commonly fail; test them.
  • Zoom and reflow. The page should remain usable when text is enlarged to 200 percent and when the viewport is 320 CSS pixels wide, with no horizontal scrolling for ordinary content.
  • Respect user settings. Do not lock the zoom with user-scalable=no or a maximum scale, and honour reduced-motion preferences with the prefers-reduced-motion media query.

Focus, Keyboard Use and Sticky Elements

Try this now on your own store: put your mouse aside and press Tab repeatedly.

  • Can you see where focus is at every moment? A visible focus outline must exist.
  • Does focus move in a logical order (header, search, menu, products, footer)?
  • Can you reach and operate the menu, filters, cart and checkout?
  • Does a sticky "Add to cart" bar or cookie banner cover the focused element? That is the 2.4.11 failure.

Offer a "Skip to main content" link as the first focusable element so keyboard users can bypass the header and the mega menu.

Pop-ups and modals need special care: focus moves into them when opened, is trapped there while open, and returns to the trigger when closed, and Escape closes them. Marketing pop-ups and exit offers frequently break all of these; see our guide to pop-ups, exit offers and cookie banners.

Help and Support Placement

WCAG 3.2.6 Consistent Help asks that where you offer help mechanisms (contact details, a human contact option, a chat or WhatsApp link, a self-help page), they appear in the same relative place across pages. A store that puts the WhatsApp icon bottom right on the home page and in the footer on the cart page fails the spirit of it. Build a help centre and link it from a consistent spot.

Video, Audio and Motion

Product videos and promotional banners need:

  • Captions for pre-recorded video with speech, and a text alternative or description where visuals carry meaning.
  • No autoplay with sound.
  • A way to pause, stop or hide anything that moves for more than five seconds, as WCAG 2.2.2 requires.
  • No content that flashes more than three times a second.

Carousels that auto-advance are a common failure. Give them a pause button, or avoid auto-advance entirely.

Platform Notes: Shopify, WooCommerce and Custom

  • Shopify. Theme choice matters. Test a theme's demo store with a keyboard before buying, and check that app-added widgets (reviews, filters, pop-ups) do not break it. Each app you install can add inaccessible markup.
  • WooCommerce. WordPress themes vary widely. Block themes and the WooCommerce Blocks checkout have received accessibility work, but results depend on your version and plugins, so test your actual configuration.
  • Custom builds. You control the markup, which is an advantage: use semantic HTML first and ARIA only to fill gaps. The first rule of ARIA is not to use it when a native element will do.

Whatever the platform, test after every theme update and plugin change. Our pre-launch testing checklist is a good place to add the accessibility checks below.

A One-Afternoon Test Plan

You do not need a specialist to find the worst problems. Plan three hours.

  1. Automated scan (30 minutes). Run Lighthouse in Chrome DevTools and a tool such as axe DevTools or WAVE on the home page, a category page, a product page, the cart and each checkout step. Automated tools find only a portion of WCAG issues, so treat a clean score as a starting point, never a certificate.
  2. Keyboard test (45 minutes). Complete a purchase using only the keyboard. Note every place you get stuck.
  3. Screen reader test (60 minutes). Use NVDA on Windows (free) or VoiceOver on a Mac or iPhone, TalkBack on Android. Try to search, filter, choose a variant and begin checkout with the screen turned off or your eyes closed.
  4. Zoom and mobile test (30 minutes). Zoom to 200 percent, narrow the window to 320 pixels, and try again on a real phone.
  5. Write up. Log each issue with the page, the step, what happened, severity (blocks purchase, hinders, cosmetic) and a suggested fix.

Fix anything that blocks purchase first. Retest after fixes and record the date; accessibility is an ongoing duty, not a one-time launch task.

Briefing Your Developer

Put these lines into your brief:

  • "The store must meet WCAG 2.2 Level AA for the home, category, product, search, cart, checkout and account pages."
  • "Use native HTML elements wherever possible; use ARIA only where native elements cannot do the job."
  • "Provide the results of keyboard and screen-reader testing before sign-off, plus an automated scan report."
  • "All third-party widgets must be tested with a keyboard and screen reader before they are added."
  • "Document any known non-conformance and the plan to fix it."

Do not accept claims such as "our theme is fully accessible" without evidence, and avoid overlay widgets that promise instant compliance with one line of script. Accessibility professionals and some disabled users have widely criticised such overlays, and they can interfere with assistive technology; they do not replace fixing the underlying code.

An Accessibility Statement

Publish a short accessibility statement in the footer: the standard you aim for (WCAG 2.2 AA), the date you last tested, known limitations, and a contact route (phone, email, WhatsApp) where shoppers can ask for help or report a barrier. Be honest about gaps. An accurate statement of partial conformance builds more trust than a claim of perfection.

India-Specific Notes

The RPwD Act, 2016, together with the Harmonised Guidelines and Standards for Universal Accessibility in India, frames accessibility obligations for the public sector and for services open to the public. The Government's GIGW 3.0 guidelines apply to government sites and reference WCAG. If your store serves enterprise or institutional buyers, they may include accessibility requirements in procurement. Rather than guess at legal exposure, ask a qualified lawyer, and in the meantime follow WCAG 2.2 AA, which is the technical yardstick regulators and buyers refer to. For an Indian view on the general website checklist, see our WCAG accessibility checklist for India.

Frequently Asked Questions

What accessibility standard should an Indian online store follow?

Build to WCAG 2.2 Level AA. It is the current W3C recommendation, it is what most accessibility audits and procurement requirements reference, and it is consistent with India's government guidance, which draws on WCAG.

What are the most common accessibility failures on ecommerce sites?

Missing or poor alt text, unlabeled form fields, colour-only variant swatches and status messages, filters that cannot be used by keyboard, silent add-to-cart feedback, low-contrast text and sticky elements that hide focused fields.

Do accessibility overlay plugins make my store compliant?

No. Overlays do not fix the underlying markup, can conflict with screen readers, and are widely criticised by accessibility practitioners. Fix the source code and test with real assistive technology.

How big should buttons be on a mobile store?

WCAG 2.2 Success Criterion 2.5.8 requires pointer targets of at least 24 by 24 CSS pixels, or enough spacing around smaller ones. For primary actions such as Add to cart, larger targets are better for thumbs.

Can I test accessibility myself?

Yes, to a point. Run an automated scan, then complete a purchase by keyboard, try a screen reader and zoom to 200 percent. For a formal conformance claim, commission an expert audit.

Building a Store Everyone Can Buy From

Govindani Infotech, a website design and development company at 2nd Floor, Landmark Plaza, 206 Satara Road, Parvati Paytha, Pune 411009, builds online stores on Shopify, WooCommerce and custom stacks. If you want a store built and tested with accessibility in the brief, see our website creation services and checkout systems, then contact us or call 092019 58274.

Sources:

About the author: written by the Govindani Infotech ecommerce development team in Pune.

Need Help With Your Digital Strategy?

Govindani Infotech helps Indian businesses and NGOs build websites, run ads, and grow online. Contact us for a free consultation.