Accessibility
The target is WCAG 2.2 AA practices. That is a target, not a certification, and this page says what has actually been tested.
Last reviewed
What is claimed
This site was built against WCAG 2.2 AA practices and tested with automated checks and manual keyboard review. No formal conformance is claimed and no audit has been carried out by a third party. Claiming full conformance without an independent audit would be exactly the kind of unearned statement this site avoids elsewhere.
What has been built in
- Semantic landmarks, one
h1per page and a logical heading order. - A skip link to the main content as the first focusable element.
- Complete keyboard operation, with a visible focus outline everywhere and no keyboard traps. The mobile menu is a disclosure rather than a modal, so there is no focus to trap.
- Status badges that do not depend on colour: the label is always written out, and the marker shape differs per status.
- Text that reflows without horizontal scrolling from 320px upwards, and at 200% zoom.
- Touch targets of at least 44px in the mobile navigation.
- Decorative images marked as decorative, and meaningful ones described.
- Reduced motion respected from the first paint via CSS, not after hydration. The 3D hero is not loaded at all under reduced motion or on small screens, and the site is complete without it.
- No flashing or strobing content anywhere.
The 3D hero specifically
The animated network on the home page is decorative. It carries no information that is not also in the product list below it, it contains nothing interactive, and it is hidden from assistive technology. Anyone with reduced motion enabled, a data saver on, a small screen, a low-memory device or no WebGL sees a static drawing instead and loses nothing.
Known limitations
Being specific is more useful than a general apology:
- No screen reader testing on assistive technology I do not have access to. The markup follows the practices, but VoiceOver, JAWS and NVDA behave differently and I have not been able to check all of them.
- The status table on the status page scrolls horizontally inside its own container on narrow screens. Real table semantics were preferred over a card layout so that row and column headers stay associated, which is the better trade for screen reader users and slightly worse for a small-screen mouse.
- Colour contrast has been checked against the palette, but only automated checking has been done — not a manual review of every state.
- The products have not been assessed here. This statement covers this site only.
Reporting a barrier
If something on this site was difficult or impossible to use — with a keyboard, a screen reader, magnification, voice control, or because of motion or contrast — please email kpleelaaravind@gmail.com. Tell me what you were trying to do and what happened, and the assistive technology and browser if you know them.
One person reads these, so a reply may take a few days. Accessibility bugs are treated as bugs, not as feature requests.
This page covers the main ITISYOU website only. Each product publishes its own policies, because what they do genuinely differs — see the network. Questions to kpleelaaravind@gmail.com.