1.10.0
Surfaces you read through, and focus you can see
- •The policy, terms and documentation pages name no model vendor. What a page needs to say about where your data goes it says in categories, and the sub-processors are named where a data processing agreement is required to name them
- •Data retention is written from the running system rather than from intent: ninety days of events, thirty of the feed, a year of the audit log, and artefacts kept until you delete them
- •The header on the legal and documentation pages is opaque. It had been eighty per cent, written when a blur was going to frost the rest, and the blur was removed from the product a while ago — so paragraph text was printing across the wordmark on a phone
- •The cookie table is read as a list on a phone. Four columns in a 367px column meant the column naming each cookie’s flags was off screen, and the sentence explaining what a cookie does ran sixteen lines at two words a line
- •Inline code is no longer printed with the backticks an author types around it
- •Keyboard focus stays where you can see it: the site header and the consent banner both used to sit on top of the control you had just tabbed to — every footer link, entirely covered
- •Asking your system for increased contrast now reaches the words. The rule existed and applied to the document root, which is not where the text takes its colour from; body text goes from 7:1 to 16:1
- •The fourth check the accessibility statement names now runs on every change, on the pages anyone can open