Accessibility.
We want everyone who visits the Mirador website to be able to read the site, use the console and reach us. This statement covers mirador.systems.
The standard we work to
The target is the Web Content Accessibility Guidelines 2.2 at level AA. The site works with a keyboard alone, shows where the focus is, names every control, and keeps the text readable at 200 and 400 percent zoom without scrolling sideways.
Where the site falls short
- The black hole on the home page is drawn on a canvas, which a screen reader cannot read. A text description stands in for the picture, and a pause button stops the movement. With reduced motion switched on, the picture holds still.
- The console in the hero plays a short sequence on a loop. A pause button stops the sequence, and with reduced motion switched on the console shows the end of the sequence and never moves.
- The trace beside No SDK to write is drawn on a canvas too. A text description gives every step and the time the step took, and the drawing plays once, for under five seconds, then holds.
- In the full console at /console, the colour that marks a critical status reads at a contrast of 4.29 to 1 against the panels, under the 4.5 to 1 the standard asks for small text. Every critical status also carries the word Critical, so the colour never stands alone.
Tell us about a problem
If anything on the site is hard to use, write to hello@mirador.systems and say which page and what happened. Ahmed replies personally within one working day.
How we test
We check every change with automated tests for contrast, names, roles and focus, and by working through the home page, the console, the security page and the contact form with a keyboard alone.