Our commitment
Sidenote is a small, independent project, not a large organisation with a formal accessibility programme. We still treat accessibility as part of quality: the site and app are built with semantic HTML, keyboard access and readable contrast, and we fix reported barriers as time allows. This page is an honest statement of where we are, not a certification.
What we have done
- Semantic landmarks, a skip link and a visible focus ring on every interactive element.
- Keyboard access to navigation, dialogs, the command palette, the editor toolbar and the note list.
- Text contrast on this site meets WCAG AA in both the light and dark palettes; the app's palettes are designed to the same target. The site follows your system colour scheme.
- Respect for
prefers-reduced-motion: the companion and other motion are reduced or turned off. - Responsive layout that reflows at 320 CSS pixels on this site and at phone widths in the app.
- Descriptive alt text for meaningful images; decorative images are marked empty.
- Form controls with visible labels or accessible names, and status messages announced with live regions.
- No autoplaying media, no flashing content and no time limits on writing.
Known limitations
- The rich-text editor is the most complex surface. Some screen-reader and browser combinations may announce toolbar state inconsistently.
- Notebook reordering supports drag-and-drop; move and reorder actions are also available through menus and dialogs, but the drag interaction itself is not keyboard-operable.
- LaTeX and table content can be difficult to navigate with a screen reader; the raw Markdown view is an alternative.
- PDF output depends on the browser's print engine, so its tagging and reading order vary.
- The site and app have not yet had an independent accessibility audit.
Tell us about a barrier
If something blocks you, please open an issue labelled accessibility at github.com/awbuilds/sidenote/issues with the page, the browser or assistive technology, and what you expected. For anything sensitive, use the private channel.
We aim to respond within ten working days and to fix confirmed barriers in the next release where feasible.
Enforcement
This is a free, individual project without a formal accessibility officer or a complaints tribunal. If a response does not resolve your concern, say so in the same thread and we will escalate it within the project. Nothing here limits any right you have under applicable accessibility law.
Statement date
This statement was prepared on 3 November 2026 and describes the website and hosted app at that date.