Accessibility

What we are aiming at

WCAG 2.2 level AA, which is the standard the European Accessibility Act points at through EN 301 549, and the one the equivalent laws in the United States, Canada and Australia are read against. It is a target rather than a certificate: what follows says where the product meets it, where it does not, and what to do if you find something this page has missed.

What works

• Every control can be reached and used from a keyboard, and the one that has focus is outlined so you can see where you are. Tab moves forward, shift-tab back, space and enter act.
• A skip link is the first thing a keyboard reaches on every page, so the navigation does not have to be tabbed through twice.
• Text meets the contrast rule. Body text, hints and captions are all at 4.5:1 or better against the surface behind them, and the edge of anything you type into is at 3:1 or better.
• Nothing moves if you have asked it not to. A system set to reduce motion turns off the animations here, including the spinners.
• The page works at any zoom up to 200% and reflows at 400% without a second scrollbar.
• Errors are spoken as well as coloured. A message about something going wrong is announced by a screen reader rather than only turning red, and it says what to do next.
• Nothing depends on colour alone. Where a colour carries meaning, a word carries it too.

What does not, yet

Said plainly, because a statement that claims everything is a statement nobody can rely on.

• The relationship graph in the workbench is a picture. It draws tables and the links between them on a canvas, and a screen reader cannot read it. Everything it shows is also in the lists and tables beside it, which can be read - but the picture itself is visual, and making it navigable is work we have not done.
• Some tables are wide. On a narrow screen they scroll sideways in their own box. That is deliberate and beats reflowing a column of numbers into confetti, but it is harder to use.
• No independent audit has been done. What is above is our own testing: keyboard, screen reader, zoom, contrast measured from the palette rather than eyeballed. An audit by somebody else is worth more, and we have not bought one yet.

If something is in your way

Write to hello@i2b.app and say what you were trying to do and what stopped you. It reaches the founder, not a queue. We answer within five working days and say either when it will be fixed or why it will not be.

If you are a customer and something here prevents you from using what you paid for, that is a fault like any other: the refund promise in the Terms applies.

If our answer does not satisfy you, you may complain to the authority that enforces this where you live - in Bulgaria the Commission for Consumer Protection, elsewhere in the EU the body named in your country's implementation of the European Accessibility Act, and outside it the equivalent authority.

How this was prepared

Self-assessed against WCAG 2.2 AA. Contrast is computed from the colour palette rather than sampled, so every combination in the product is covered rather than the ones somebody thought to check. Keyboard and screen-reader testing is done on the paths a customer actually takes: signing in, getting a price, ordering, the account, and the legal pages.