Accessibility · Last checked 25 September 2026
What I tested, and where it still falls short.
I aim for WCAG 2.2 at level AA on every page of this site. It is a voluntary aim, my own choice: not a certificate, and no outside body has audited the site. This page says what I tested, what still falls short, and how to tell me about a problem.
The short version
- The aim is WCAG 2.2 at level AA. It is a voluntary aim: I chose the standard, and I say plainly where the site misses it.
- On 25 September 2026 I tested every page: the keyboard alone, the names a screen reader reads out, contrast by day and by night, 200% zoom, reduced motion, the browser’s data saver, and JavaScript switched off.
- What falls short: the films are silent, and what they show is in text (the one walk-through in my own voice has captions, and its words are written out beside it); the red notes on them are handwriting; and the booking page, WhatsApp and the clients’ own sites are other people’s, which I cannot test or fix.
- If something here does not work for you, email hello@quietlybuild.in or WhatsApp +91 62399 02728. I reply within one working day.
01 · The aim
WCAG 2.2 at level AA, by choice.
The Web Content Accessibility Guidelines are the W3C’s rules for making a website work for people who use it differently: with a keyboard instead of a mouse, with a screen reader, zoomed in, with motion turned off, or on a slow connection. Level AA is the middle of three levels, and the one public-sector rules usually ask for.
This is a voluntary aim, and the choice is mine. I hold the site to it because a website is for everyone who needs to read it, and a studio that builds websites should be able to show its own working.
An aim is not a promise that every page meets every rule. Where I know a page falls short, section 03 says so.
02 · What I tested
What I tested, and what I found.
All 18 pages of the site, the page for a wrong address included, on 25 September 2026, in Chrome on a Mac, at a phone’s size (390 pixels wide) and a laptop’s (1440), by day and by night. I used Chrome’s own accessibility tools and a script that goes through every page the same way each time. Where the test found a problem, I fixed it the same day, and it says so below.
- The keyboard alone
- Every page, from the top, with the Tab key alone, on a phone, a laptop and a short laptop screen (1280 by 720). The first Tab shows “Skip to the content”, and Enter goes there. Every link, button and field is reached in the order you read it, and nothing traps the keyboard. Whatever has focus carries a red ring, at least 3.7 to 1 against what is behind it, and is never hidden behind the header, the phone’s bottom bar or a panel that stays put while the page scrolls. (The specimen invoice’s side panel was taller than a laptop screen and hid its last link; it now scrolls within the screen.) The menu opens with Enter and closes with Escape, and focus goes back to it.WCAG 2.1.1, 2.1.2, 2.4.1, 2.4.3, 2.4.7 and 2.4.11
- What a screen reader reads out
- Chrome’s accessibility tree, page by page. Every link, button and field has a name that says what it does, and a link that opens a new tab says so. Each page has one main heading and no skipped levels. Every picture that carries meaning is described; the drawings that only decorate are hidden from screen readers. Each film’s button says which film it plays or pauses.WCAG 1.1.1, 1.3.1, 2.4.6, 2.5.3 and 4.1.2
- Contrast, day and night
- Every piece of text on all 18 pages, measured against what is behind it on a phone and a laptop, by day and by night: 13,444 measurements in all. The lowest is 5.44 to 1 by day and 6.32 to 1 by night, against the 4.5 to 1 level AA asks for. The only text below it is what is faded on purpose for a moment (section 03).WCAG 1.4.3
- 200% zoom, and a narrow screen
- A laptop at 200% and at 400% zoom (a window 640 and 320 pixels wide), and a phone with the wider letter, word, line and paragraph spacing WCAG describes. Nothing scrolls sideways and nothing is cut off. The test found two places that did, and both are fixed: the price in very large type, and the currency table in the terms.WCAG 1.4.4, 1.4.10 and 1.4.12
- Reduced motion
- With reduce motion turned on, nothing moves by itself. No film plays or downloads until you press Play, the sections do not slide over each other, the hotel’s drawing stands still, and pages do not fade into each other.WCAG 2.2.2
- The data saver
- With the browser’s data saver on, the same: each film shows its still, and downloads only when you press Play.
- JavaScript switched off
- Every page shows all its words and links, the menu opens and closes, nothing scrolls sideways, and the call times show in India time.
- Things you tap or click
- Every button, and every link that is not inside a sentence, is at least 24 by 24 pixels or has that much clear space around it. The footer’s links on a phone were a pixel too close together, and now are not.WCAG 2.5.8
03 · Where it falls short
What I know is not good enough yet.
- The films
- They are silent screen recordings of clients’ websites, so there is no sound to caption. What each one shows is in text: its still carries a description, and a screen reader hears the notes drawn on it as a list. Every film has a Pause button, only one plays at a time, and none plays by itself under reduced motion or the data saver. One film is different: a walk-through of a hotel’s site in my own voice. It plays only when you press Play, with the browser’s own controls, it has captions, and every word of it is written out under it. What is on screen is said in the words, so it has no separate audio description.
- The red notes on the films
- They are in a handwriting typeface, which some people find hard to read. A screen reader gets them as plain text, but on screen they appear only as handwriting, and there is not yet a way to show them in plain type.
- The drawings
- The payments drawn to scale and the hotel’s page drawn from lines to live are pictures. Every amount is written out in words beside the bars, and the hotel’s three steps are in text, so nothing is only in a drawing. The labels inside the hotel’s drawing fade as its film takes over, and on a phone the hotel’s next step stays faint until you scroll to it, so for a moment those words are fainter than 4.5 to 1.
- Other people’s pages
- The booking page on Cal.com, WhatsApp, the clients’ own websites, the GST portal and the regulators’ registers are not mine, and I have not tested them. If the booking page does not work for you, WhatsApp or email me two or three times that suit you and I will arrange the call.
- How it was tested
- By me, with Chrome’s tools and my own script. It has not yet been tried by hand with JAWS, NVDA or VoiceOver, or by someone who uses a screen reader every day, and Safari and Firefox have not been checked item by item. If you use any of them and something is wrong, I would like to know.
04 · Tell me about a problem
Write to me, and I reply within one working day.
- hello@quietlybuild.in. Put “Accessibility” in the subject line.
Tell me the page, what you were trying to do and what happened. The device, the browser, or the screen reader or magnifier you use helps too, if you know it, but you do not have to.
I reply in writing within one working day, and say what I will change and when. If something on this site stops you, I will send you what you need another way, by email or on a call, while I fix it.
05 · When it was checked
Last checked 25 September 2026.
Every page of the site, by me, Aditya Vashistha. The check I run before every upload repeats part of it by itself: one main heading on each page and no skipped levels, a description on every image that needs one, every film muted (except the voiced walk-through, which it checks for captions and for waiting until you press Play), nothing the site’s security policy would block. The rest I test again by hand whenever the way the pages look or work changes, and I change the date above when I do.