Accessibility statement
Accessibility
We want Puffin to work for everyone, however you see, hear, move, or read. This page says where Puffin stands today, what we’re still checking, and how to tell us when something gets in your way.
Updated Oct 29, 2026
What we aim for
We aim for the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA, the common standard for accessible websites and apps. The aim covers the Puffin app and this site.
A full audit to that standard has to pass before Puffin opens to everyone.
Where Puffin stands today
Puffin doesn’t fully meet WCAG 2.2 AA yet.
Our first full audit, on Oct 21, 2026, tested the Puffin web app on computers and phones, in light and dark. It found problems in a few shared parts, many of them in the calendar. We’ve fixed many of them, and each one that’s left is on our list to fix.
What works today
In the Puffin app
- Pages start with a link that skips to the main content.
- You can turn off single-key shortcuts in Settings, so a stray key press does nothing.
- Settings has Reduce transparency, which makes the glass solid, and Increase contrast, which makes text and edges stronger.
- When your device asks for reduced motion, Puffin’s animations stop.
- Pages work at 200 percent zoom, and on a screen 320 pixels wide, without scrolling sideways.
- Signing in works with paste and with password managers.
- In our automated screen reader checks, the changes you make are announced, such as adding something, undoing it, or accepting a proposal.
On this site
- Every page reads and works without JavaScript.
- Each page has one main heading and starts with a link that skips to its content.
- When your device asks for reduced motion, the front page shows its story as still pictures. The story also has its own Reduce motion button.
- The moving pictures are hidden from screen readers, and the words beside them say what they show.
- When your device asks for reduced transparency, the glass turns solid.
What we’re still checking
- A full audit to WCAG 2.2 AA, before Puffin opens to everyone.
- Testing with the VoiceOver and NVDA screen readers. Our checks so far read what Puffin tells a screen reader, without one running.
- Speech input, such as Voice Control and Dragon.
- Firefox, zooming text on its own, and phones turned sideways.
Problems we know about
- In the calendar, some block titles are cut short when you widen the spacing of letters and words.
- After some actions, keyboard focus moves to the top of the page instead of staying where you were.
- When two proposals wait side by side, a screen reader hears their Accept, Edit, and Dismiss buttons without each proposal’s title.
Tell us about a barrier
If something in Puffin or on this site gets in your way, write to team@puffincalendar.com.
Tell us the page, what you were trying to do, and the device, browser, and any assistive technology you use.
Inside Puffin, you can also use the feedback control on any screen.