Accessibility
What works. What doesn't yet.
Margin should work whether you use a keyboard, a screen reader, voice control or a zoomed-in screen. This page says how close it is, what we know is broken, what we haven't tested, and how to tell us about a barrier.
Last updated · 26 October 2026
The standard
We aim for the Web Content Accessibility Guidelines (WCAG) 2.2, level AA, for the Margin extension and for this website.
The extension partially conforms to WCAG 2.2 AA. That means some parts of it do not meet the standard yet; they are listed below. This is our own assessment, made on 24 October 2026. It is not a third-party audit.
This website has not been audited yet. No one has checked it against WCAG 2.2 AA the way the extension was checked. That audit is next.
The desk dashboard is not on sale, and this statement does not cover it.
What we checked
On 24 October 2026 we audited the extension's current code, which is newer than the version in the Chrome Web Store today. It covered the popup, the side panel, the settings page, the syllabus preview, the welcome page, and the study and Circles screens that are opening in stages. Each page ran in Chromium as the real extension. We used automated checks (axe-core), measured text contrast directly, walked every page with the keyboard alone, measured the size of every control, and checked reflow at 320 pixels wide and at 200% zoom, reduced motion, and the names that assistive technology reads out.
What holds up
- Text contrast meets 4.5:1 everywhere we measured, and 3:1 for large text.
- Every keyboard stop but one shows a visible focus outline, there are no keyboard traps, and the tab order follows the reading order. The one exception is listed below.
- Every control is at least 24 by 24 pixels, or spaced as WCAG allows.
- When your system asks for reduced motion, no animation runs.
- Status messages are marked so screen readers can announce them.
- The settings, welcome, preview and study pages reflow at 320 pixels wide with no sideways scrolling.
Known problems
Still open
- The side panel at 200% zoom. The row of tabs runs off the side, and the titles of upcoming items wrap one letter per line. WCAG 1.4.10, 1.4.4
- Undo after “Mark done”. In the side panel the undo stays for 10 seconds, and nothing else there brings the item back. WCAG 2.2.1
- Buttons that are read out differently from how they look. The Circles block-length buttons show “25 min” but are announced as “25 minutes”, which voice control may not match. WCAG 2.5.3
- Page structure. The popup, the side panel and the study page have no top-level heading, and the popup has no main landmark. Two header cells in the settings page's calendar-feed table are empty, and the settings page's section buttons are read with the number run into the word (“01Sources”). The note on the settings page's save bar sits outside every landmark. WCAG 1.3.1
Fixed, not yet released
Fixes for these five are written but are not yet in the version on the Chrome Web Store. Until they are, they are problems too.
- In the side panel, when nothing was snoozed, an empty control with no name still took a Tab stop. WCAG 4.1.2
- On the study page, the course pickers had no name a screen reader could read. WCAG 4.1.2
- On the settings page, a focused link near the bottom could be hidden under the save bar. WCAG 2.4.11
- In the side panel, the “Mark done” button was named “Mark ‘Quiz 2’ done”, so saying “click Mark done” did not find it. WCAG 2.5.3
- In the syllabus preview, the PDF picker showed no focus outline. WCAG 2.4.7
What we haven't tested
- A real screen reader. We have not run NVDA, JAWS or VoiceOver. Names were read from the browser's accessibility tree.
- Windows high-contrast (forced colors) mode. Some toggles and check circles are drawn with backgrounds and may not show.
- Some states. The list of your Todoist tasks after you connect Todoist, buying and unlocking the Margin Pass, and the popup's messages when a sync really fails.
- Other browsers. Margin runs in Chrome and other Chromium-based browsers; Firefox and Safari are not supported.
- This website, as above.
Tell us about a barrier
If something in Margin doesn't work with the way you use a computer, write to support@margin.computer with “Accessibility” in the subject. Say what you were trying to do, where, and what you use: a screen reader, zoom, voice control, a keyboard, or anything else. We aim to reply within three business days.
If you need something on this website in another format, ask in the same email.
We update this page when a fix reaches the Chrome Web Store, and after each new audit. Other ways to reach us are on the contact page.
Marginalia.
Self-assessed against WCAG 2.2 level AA, 24 October 2026.