Accessibility
Software that runs a business has to work for everyone in the business. We hold this site to the same standard we hold client builds: WCAG 2.1 AA as the working target, and a plain channel for telling us when something is in your way.
Last updated 1 September 2026
C-1What is in place
- Contrast. Body text sits at 6:1 or better against its ground; secondary text and labels at or above 4.5:1 for reading sizes.
- Keyboard. Everything interactive is reachable and operable by keyboard, with a visible focus indicator and a skip link on long pages.
- Motion. Every animation on the site, including the hero drawing and the three-body figure, respects the system's reduced-motion preference: content renders complete and still.
- Structure. Semantic landmarks and heading order throughout, so screen readers get the drawing set's structure, not a soup of divs.
- Figures. Drawings and charts carry written descriptions; the calculators state their inputs and results in text.
- Zoom and reflow. Layouts reflow to 400% zoom and down to small phones without horizontal scrolling of the page body.
C-2Known imperfections
Known gaps: the live three-body simulation is decorative and described in text, but its motion cannot itself be conveyed non-visually; the dimension annotations on the hero drawing are hidden on small screens rather than restyled; and the demonstration designs on the designs section are show pieces built to each fictional brand's aesthetic and, while built to the same baseline, they get less ongoing audit attention than the main set. When a page and this statement disagree, tell us; the page is at fault.
C-3In client work
Accessibility in the systems we build is not an upsell. Operational software gets used at 6am in a ute, by tired people, on cracked screens, sometimes with gloves; accessible design and usable design are the same discipline. Client builds target the same WCAG baseline, with any project-specific requirements captured in the scope document.
C-4Tell us
If anything on this site is hard to use with your eyes, ears, hands or assistive technology, email hello@blinco.tech with the page and what got in the way. A person reads it, and fixes go into the next release.