Accessibility Statement

Last updated: August 20, 2026

We want SeeNote, a tool whose entire purpose is making dense documents easier to read, to be usable by everyone, including people who rely on assistive technology. This statement covers the seenote.co website and the SeeNote Chrome extension.

Standard we aim for

We target WCAG 2.1 Level AA, the standard referenced by most accessibility regulations worldwide.

What is implemented on this website

The extension

Keyboard-first operation is a core design goal of SeeNote, not an accessibility afterthought: opening, chaining, and closing note windows works entirely from the keyboard, and windows are announced to screen readers as dialogs with focus management. Pressing ? on any filing opens a panel listing every shortcut, along with what each button in a note window's header does. Those buttons carry icons, and a tooltip hides their meaning behind a hover that most people never perform.

The notes index is a keyboard-navigable dialog: open it with S, filter or arrow-key through every note in the filing, press Enter to open one in the same window, and Escape to close, with focus returning to where you were reading. Screen readers announce it as a dialog containing a listbox of notes. When a filing has no detectable notes, the panel says so instead of showing an empty list.

We will publish an updated statement covering the shipped extension at launch.

Known limitations

Feedback and contact

If you encounter any barrier using this website or the extension, please tell us: hello@seenote.co (subject line "Accessibility" helps us prioritize). We aim to respond within a few business days and to fix verified barriers as quickly as possible.