Accessibility statement

011. The standard I build to

All pages of quietlybuild.in, including the checkout, Your orders and your library, are built to meet WCAG 2.2 at level AA. Where I know the site falls short, I say so in section 4 rather than claim more than I have checked.

022. What that means on this site

• Keyboard. Everything works by keyboard, with a clear focus outline. A “Skip to content” link comes first. The checkout opens as a dialog that holds your focus and returns it when it closes.
• Screen readers. Each page has one main heading and headings in order. Tables have proper headers. Changes such as a price split or a form result are announced.
• Images. Pictures of real product pages carry a text description. Decorative drawings are hidden from screen readers, and anything they show is also said in the text.
• Colour and contrast. Text and controls meet the AA contrast levels in both themes, and colour is never the only way something is shown.
• Zoom and small screens. Pages reflow from 320 pixels wide without sideways scrolling, and text can be enlarged to 200% or spaced out without losing anything.
• Forms. Every field has a label. Errors are shown next to the field, in words, with a suggestion. There are no puzzles and no passwords: your orders are reached through a link. If a payment is retried, the checkout remembers what you typed.
• Movement. If your device is set to reduce motion, animation is switched off. Nothing flashes. The drawing on the home page plays once and has a still version.
• Help in one place. The Contact link sits in the same place in the footer on all pages.
• Targets. Buttons and other controls are at least 24 by 24 pixels, with space around them, and the main buttons are 44 pixels high. Links inside sentences follow the size of the text.

033. How it is checked

Before each release, all pages are tested in both themes with the axe-core automated checker, and by hand: with a keyboard alone, with VoiceOver on macOS and iOS, and with TalkBack on Android, at widths from 320 to 1440 pixels.

This statement was written on 12 October 2026. I review it whenever the site changes in a way that could affect access, and at least once a year.

044. Known limits

• Razorpay’s payment window is made by Razorpay, and I can’t change how it works with assistive technology. It closes after 15 minutes without payment; the details you typed on my page stay, so you can start again. If you can’t use the window, write to me and I can send you a Razorpay payment link to pay on its own page instead.
• Previews of product pages are images of real pages. Their descriptions say what each page shows; they don’t reproduce all its text.
• The product files (PDF, Word and Excel) haven’t yet been checked against an accessibility standard. The PDFs contain real text that you can select and have read aloud, but their structure hasn’t been tested page by page. If a file doesn’t work with your assistive technology, write to me and I will find a format that does wherever I can.
• Other sites. Links to Razorpay and to government pages lead to sites whose accessibility I don’t control.

055. Tell me about a barrier

Write to hello@quietlybuild.in with “Accessibility” in the subject. Tell me the page, what you were trying to do, and the device, browser and any assistive technology you use. I reply within two working days, and tell you when it is fixed.

If a barrier stops you buying, or using something you bought, you can also use the form on the Contact and complaints page: you get a ticket number, and I resolve it within one month.