A sweep of the public site's 95 pages at thirteen screen widths, from a 320-pixel phone to a 3840-pixel monitor, in both themes. Links in legal documents are underlined again, code samples and wide tables can be reached from the keyboard, small text was raised to a readable size, and signed-out visits no longer log an error.
What changed
The public site's 95 pages, including sample company, comparison and changelog pages, were loaded at thirteen widths (320, 375, 390, 428, 768, 810, 1024, 1280, 1366, 1440, 1920, 2560 and 3840 pixels) in the dark and light themes and checked for sideways scrolling, console errors, broken internal links, missing image descriptions, heading order and page metadata. None of the pages scrolled sideways at any width. What was fixed: links inside legal documents had lost their underline to a later style rule, so they were told apart from the surrounding text by color alone, which fails WCAG 1.4.1; they are underlined again. Code samples and wide tables that scroll sideways on a phone can now be reached and scrolled from the keyboard. The selected tab above a code sample in the light theme is back to its dark ink, which meets the 4.5:1 contrast minimum. The cookie banner's buttons, the note in the navigation menus, the line under legal document titles, and several counts and dates were raised from 12 or 13 pixels to 14. Eleven pages that set their own sharing details had dropped the sharing image and now carry it. Sideways-scrolling regions draw a thin scrollbar in the theme's colors on Windows and Linux instead of the system's thick gray one. A visitor who is not signed in no longer triggers a failed request in the browser console on every page. Two passages of the Acceptable Use Policy were rewritten in plainer words, with their meaning unchanged and a revision note.
Why it changed
An automated accessibility check (axe-core, against the Web Content Accessibility Guidelines 2.2 at level AA) and a layout check across widths found a handful of defects the page-by-page reviews had missed.
Who is affected
- Affected: Everyone reading the public site, and in particular keyboard and screen-reader users. No endpoint a developer calls changed its answer for a signed-in session.
- Availability: Public. No account needed.
- Release stage: Available.
- Areas: Platform, Legal.
What to do
No action required. Nothing to do. A client that read a 401 from /api/auth/session as signed out now receives a 200 with authenticated set to false, which every client in this site already reads the same way.
Dates
- Announced: September 28, 2026, the day this entry was written. Entries are never backdated.
- Released: September 28, 2026.
What this does not fix
Signed-in workspace pages were not part of this sweep, because they need an account and live data. Safari and Firefox were checked against the CSS they are known to read, not driven directly.