Made for everyone.
BENIBIX Insights aims to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA on every page. Here is what that means in practice, and where it is not there yet.
What does the site do to be accessible?
- Keyboard first. Every link, button, menu and form works with the keyboard, and focus is always visible.
- Screen readers. Pages use real headings, landmarks and labels. Icons that carry meaning have a text label; decorative art is hidden from assistive technology.
- Contrast in both themes. Text colours, including each platform's colour, are checked to reach at least 4.5 to 1 against their background, in light and in dark.
- Reduced motion. If your system asks for less motion, the pictures at the top of the pages stand still and nothing slides in.
- Zoom and small screens. Pages reflow down to a phone's width and up to 200% zoom without losing content.
- No time limits. Nothing on the site expires while you read, and a course remembers in your browser which lessons you marked as done.
What does not work well yet?
- The moving picture at the top of each page is drawn, and a screen reader reads it as one sentence that says what it shows. Everything it shows is also in the text of the page.
- In the picture on the Work page, pointing at a station names its pattern and a click goes to it. With a keyboard, the same patterns are in the list below it, each with its own heading.
- The code in the lessons is coloured to read more easily; a screen reader reads it as plain text, and the Copy button copies it exactly as it is.
How do I report a problem?
If something on the site is hard or impossible to use with the way you work, please tell me. Say which page, what you were trying to do, and what you use (a screen reader, keyboard only, zoom). Write to me at hello@benibix.com or with the contact form. I treat accessibility problems as bugs.