Accessibility statement

1. Why this matters here

The NCERT books themselves take accessibility seriously — Class 6 Ganita Prakash pauses mid-chapter to note that visually challenged students read scales whose markings are raised and can be felt. A companion to that book should hold itself to the same standard. Accessibility at PrepShorts is not a compliance checkbox; it is part of being faithful to the book.

2. What works today

• Keyboard, for everything a student does. The player, the checks, the test builder and the dashboards are reachable and operable by keyboard, with a 2px focus ring on every stop that clears the 3:1 contrast WCAG asks of it — measured at 5.08:1 on the page and 3.43:1 on a primary button, and refused by the build below that. One control in the office view is not there yet — it is named in the gaps below.
• Contrast. Body text sits well past the AA 4.5:1 ratio on our near-white ground; accent-coloured text uses the deep steps of the ramp for the same reason.
• Captions. Every video carries subtitles, cut to the same section landmarks the video is. A full reading transcript sits under the player as well, in the same section order, so a video can be read rather than watched.
• Structure for screen readers. Pages use real headings, labelled form fields, and alt text on figures that describes what the figure teaches, not just what it shows.
• Skipping the menu. Every page that has a menu to skip opens with a “Skip to content” link — the first thing the Tab key reaches, jumping straight past the eight to fourteen navigation links to the page itself. The 22 pages without one are the moved-address stubs and the 404: they carry no navigation block, so there is nothing to bypass. The main menu is named for a screen reader that lists landmarks. This was missing until 8 September 2026 and is recorded here because it was a Level A gap under an AA claim.
• Reflow. Every page is fluid to 390px and beyond, honours browser text-zoom to 200%, and never traps content in a fixed-width block.
• No motion traps. Nothing flashes, autoplays with sound, or moves in a way that can’t be paused; the player respects reduced-motion preferences.
• Language. Most of the interface and most pages are in English, tagged as such so a screen reader pronounces them properly. Some lessons have the video recorded a second time in Hindi, and each of those has its own Hindi page at the same address with /hi on the end: that document is tagged Hindi throughout \u2014 the heading, the summary, the words to know, the check questions and the transcript \u2014 so a screen reader changes voice for the page and not only for the video. Both documents name the other in hreflang, and the switch under the player is a pair of links rather than a setting, so it says where it goes and works with the keyboard, the back button and a screen reader alike. The chapter and module titles in the breadcrumb are still English, because there is no Hindi source for them yet. There is no site-wide language setting. This statement is dated 10 September 2026 and will be updated the day that changes.

3. Known gaps, honestly

Two, named plainly. The weak-topic grid prints its counts on the surface rather than only in a tooltip, but the cells themselves are not focusable, so a keyboard reader gets the numbers and not the navigation. Audio description for videos is partial: sections whose meaning depends on a drawn figure are described in the narration by design, but there is no separate described-audio track. This section is a list of what is wrong, and it shrinks as they close — sortable headers now announce their direction with aria-sort, and the reading transcript shipped, so both have left this list.

4. How we test

Every release is checked by automated audits, and two kinds of them. Some run in the build and refuse it on a failure: the focus indicator against the 3:1 non-text ratio, landmarks, control labelling, duplicate identifiers and the skip link. Others drive a real browser over sixty-three screens and check text contrast against the AA ratios along with layout and type. Naming them separately is deliberate — this page listed heading structure and a 200% text-zoom pass among the automated checks for a few hours on 9 September 2026, and neither is automated at all. Sixty-three screens are rendered in a real browser at three widths on every run, and checked against the layout and type rules — that suite does not press keys, and this page claimed for a few hours on 9 September 2026 that it did. Keyboard-only passes are done by hand, not on a schedule we can name. Screen-reader passes with NVDA and TalkBack are not yet part of every release — this page said they were until 9 September 2026, and no record of one exists; it is named here rather than quietly dropped, because a testing claim that cannot be shown is the same kind of defect as an accessibility one. We have not commissioned an external audit against WCAG 2.2 AA. When we do, the summary will be published here — saying so in advance of the first one would be exactly the kind of claim this page exists to avoid. Real classrooms are part of testing: pilot schools include students who use assistive technology, and their reports outrank our checklists.

5. Tell us what’s in your way

If anything in PrepShorts is hard to use with your eyes, ears, hands or attention, write to access@prepshorts.com — a student, parent or teacher’s plain description is exactly the right format. We acknowledge within 48 hours, and accessibility fixes ship in the next release, not the next term. If you need any document on this site in another format, ask and we will provide it.