[BRAND NAME]

Accessibility

What we have built, what we know is not good enough yet, and how to tell us when something blocks you.

On this page

What we are aiming for

WCAG 2.2 Level AA across the whole shopping journey — browsing, filtering, product pages, bag, checkout and confirmation. Not just the homepage.

What is built in

  • Keyboard — every control is reachable and operable by keyboard, with a visible focus ring that meets contrast requirements. Drawers and dialogs trap focus while open and return it to the control that opened them.
  • Skip link — first thing in the tab order on every page.
  • Semantic structure — one h1 per page, headings in order, landmarks for header, navigation, main and footer, and real lists for lists.
  • Forms — every field has a visible persistent label, not a placeholder standing in for one. Errors are announced, tied to their field with aria-describedby, and your input is preserved.
  • Colour is never the only signal — colour swatches carry text labels, out-of-stock options are crossed as well as greyed, and stock states are words.
  • Contrast — body text is at least 4.5:1 against its background and large text at least 3:1.
  • Touch targets — interactive controls are at least 44 by 44 CSS pixels.
  • Screen-reader feedback — bag and wishlist changes, filter result counts and validation are announced through polite live regions.
  • Reduced motion — prefers-reduced-motion removes transitions, hover zooms and the loading shimmer.
  • Zoom and reflow — usable at 400% zoom and at 320 CSS pixels wide without two-dimensional scrolling.
  • Degrades without JavaScript — every product, collection, guide and policy page renders and reads normally. Controls that cannot work without it are hidden rather than left dead on the page, and replaced with links that do work.

Known limitations in this build

Stated plainly rather than omitted. These would be addressed before a real launch.

  • No audit by a third party, and no testing with real assistive-technology users. Automated checks and manual keyboard and screen-reader passes are not a substitute for either.
  • Inventory sarees use photographs of the actual catalogued item. Fibre, weave, dimensions and provenance still need supplier confirmation and are labelled as unconfirmed rather than inferred from the image.
  • The bag, checkout, wishlist, search and collection filtering require JavaScript. Without it you can still browse every collection and product page, and the collection pages offer the pre-built occasion and fabric collections instead of a filter form that would not work. Purchasing is not possible without JavaScript.
  • The interactive first-saree questionnaire requires JavaScript; the equivalent result is reachable with collection filters.
  • No captions or transcripts are needed yet because there is no video or audio. If video is added, both become required.

Tell us about a barrier

If something on this site stops you doing what you came to do, email hello@example.com with "Accessibility" in the subject line. Tell us the page and what happened, and what you were using if you know. We will reply within one working day and tell you either when it will be fixed or how to get what you needed another way in the meantime.

You can also call us and we will place an order for you over the phone.

In plain English

Term

See the full glossary