Accessibility
This page describes the state of accessibility in SSCVeers as it actually is — including the parts that are not finished. It is not a conformance claim.
No conformance claim
SSCVeers does not claim conformance with WCAG 2.1 at level A, AA or AAA, or with any other accessibility standard. No formal audit has been carried out, no automated accessibility test runs against the code, and the interface has not been tested with a screen reader such as NVDA, JAWS, VoiceOver or TalkBack.
Saying otherwise would be easy and would be false. What follows instead is a specific account of what has been built, and what has not.
What has been done
- Keyboard operation. Interactive controls are real buttons and links rather than clickable containers, so they are reachable by Tab and activated by Enter or Space. The Settings section switcher is a proper tab list that moves with the arrow keys, Home and End.
- Visible focus. A focus ring is drawn on keyboard focus across buttons, inputs, tabs and navigation items. It is scoped so that mouse and touch users are not shown a ring they did not ask for.
- Skip links. The student area, the admin area and these policy pages each start with a “skip to content” link, so a keyboard user does not have to pass the whole navigation on every page.
- Announced changes. Errors are marked up so a screen reader interrupts and reads them; confirmations, loading messages and the offline banner are marked up as polite status updates that do not interrupt.
- Errors are never colour alone. A failure shows an icon and words, not just red text, so it is still legible without colour vision.
- Dialogs. The session-expiry dialog identifies itself as a dialog, moves focus into itself, keeps Tab inside it while it is open, and restores the page when it closes.
- Reduced motion. If your system asks for reduced motion, animations and transitions across the whole app are cut to effectively nothing.
- Text contrast. The lightest text colour used for real prose was too faint in both themes — roughly 2.5:1 on white — and has been corrected to at least 4.6:1 against every background it appears on, in light and dark mode.
- Dark mode. A full dark theme is available and is applied before the page paints, so there is no white flash for someone who finds it painful.
- Decorative icons are hidden. Icons that only repeat adjacent text are hidden from screen readers rather than read out twice.
Known gaps
These are real and current. They are listed because you are entitled to know before you rely on the product, not as a promise about when they will change.
- Nothing has been tested with assistive technology. Every item in the list above is correct by construction, not by observation. Real screen-reader behaviour may still be wrong.
- No automated checks. There is no accessibility linter or test in the build, so a regression would not be caught.
- Charts have no text alternative. Performance graphs are drawn on a canvas. The numbers behind them are shown elsewhere on those screens, but the charts themselves convey nothing to a screen reader.
- AI-generated content is not checked for structure. Tutor answers and generated notes are rendered from Markdown produced by a model, including mathematical notation. Heading order and the readability of that notation are whatever the model produced.
- Timed tests cannot be extended. Mock tests run against a fixed clock with no way to request more time, which will exclude some people from that feature.
- Not every screen reports failure yet. Several data screens still show an empty result when a request has actually failed, which is misleading whether or not you use assistive technology.
- Contrast has not been audited in full. One token was measured and fixed. The remaining colour pairs — particularly secondary text on tinted panels, and text inside coloured badges — have not been measured.
- Touch-target sizes have not been audited. Some icon-only buttons may be smaller than comfortable on a phone.
- Language marking. The page language is declared as English. Hindi and Hinglish content can appear inside answers and is not separately marked as such, so a screen reader may pronounce it as English.
Tell us about a barrier
If something here stops you using SSCVeers, please say so — a specific report is worth more than any audit. Write to kumarpushu74@gmail.com and, if you can, include the page, what you were trying to do, and the browser and assistive technology you were using.
There is no published response time for accessibility reports, so this page does not invent one. Reports are read by the person who operates SSCVeers.