Accessibility Statement
What this site does, and honestly, what it hasn't done yet.
Our aim
SkillAIVibe should be usable if you navigate by keyboard, read with a screen reader, need larger text, or prefer reduced motion. This is a text-first educational site, which makes that goal realistic — there are no videos to caption, no carousels, no pop-ups, and no autoplaying anything.
What the site currently does
- Keyboard navigation. Every link, button, and search box is reachable and operable by keyboard, with a visible focus outline so you can always see where you are.
- Skip link. A "Skip to content" link is the first thing focused on every page, so keyboard and screen reader users can bypass the navigation.
- Semantic structure. Pages use real headings, lists, navigation landmarks, and a single main content region, so assistive technology can navigate by structure rather than guesswork.
- Labelled controls. Search inputs have real labels, and icon-only controls (like the menu toggle and search icon) carry text alternatives rather than relying on the icon alone.
- Reduced motion. The small hover animations on cards and buttons are disabled automatically if your system is set to reduce motion.
- Light and dark themes. The site follows your system colour scheme rather than forcing one.
- Responsive text. Layouts use relative units and reflow rather than breaking when you zoom in or use a small screen.
- No content behind interaction. Every article, lesson, and definition is present in the page itself — nothing requires JavaScript, hovering, or an account to read.
Where we fall short
We'd rather list these than claim a level of compliance we haven't earned:
- This site has not been formally audited against WCAG 2.1 or 2.2 by an accessibility professional, and we don't claim a conformance level. Our checks have been self-conducted.
- Colour contrast has been chosen carefully but not verified exhaustively across every element and both themes.
- We have not tested with the full range of screen readers and assistive technologies in real-world use.
Saying "we aim to comply with WCAG" and leaving it there is common and close to meaningless. The list above is what we actually know.
Tell us if something breaks
If any part of this site is hard or impossible to use with your setup, please tell us through the Contact page and describe what happened and what you were using. Specific reports are genuinely more useful than general ones, and accessibility bugs get treated as real bugs rather than nice-to-haves.
If a page is inaccessible to you and you need its content, say so — we'll send it to you in a readable format while we fix the underlying problem.
Third-party sites
Our AI Tools Directory links to external products we don't control. We can't make any promises about the accessibility of those sites once you leave ours.