Accessibility
Lines aims to work for everyone: with a keyboard alone, with a screen reader (VoiceOver, NVDA, TalkBack), at large text sizes, with reduced motion, and in high contrast. The target is WCAG 2.2 level AA.
What every part of the app does
- Keyboard. Everything that can be clicked can be reached with Tab and used with Enter or Space. F6 and ⇧F6 move between the sidebar, the note list and the note, those showing (not a hidden sidebar, nor either in focus mode), each taking focus where it was left (the chosen list, the open note's row, the note's text). Enter on a note in the list opens it and moves into its text; a click leaves focus in the list. Lists and groups move with the arrow keys (the note list, the icon picker, segmented controls, menus). The note list draws only the rows near its view, so a long one stays fast; each row says its place in the whole list (
aria-posinsetandaria-setsize: "3 of 5,006"), and the open note's row is always there to take focus. Esc closes what's open and puts focus back where it was. Focus never drops to the page: after renaming a tag it's on the tag's row, after Esc in the note list's search field (which clears it) on the open note's row, after a menu item that opens a dialog it's back on what opened the menu, after Lock Now from an open locked note's lock button it's in the password field that opens it again, and closing the last tab puts it in the note list. In Safari and the Mac app, as everywhere on a Mac, Tab stops on buttons only with Keyboard navigation on (System Settings → Keyboard); without it, ⌥Tab does. - Focus. Focus is always visible:
:focus-visibledraws the accent outline (app.css). Nothing hides it. - Names. Every control has a name a screen reader says: its text, or
aria-labelfor a button that's only an icon (with the same text as itstitle, the tooltip). Icons beside text arearia-hidden. - Roles and states. Built from real elements first (
button,input,ul/li,nav,main, headings). Where a pattern needs more, the part is Bits UI's (menus, dialogs, popovers, selects, switches, sliders, radio groups, tabs), which follows the WAI-ARIA patterns for it: menus arerole="menu"withmenuitems; dialogs arerole="dialog"witharia-modal, a label, focus kept inside while open and given back when closed; segmented controls are radio groups; settings that turn on and off are switches (role="switch",aria-checked), each named by its label; selects are listboxes the arrow keys and typing move through; toggles sayaria-pressed; disclosuresaria-expanded; the open itemaria-current. - Announcements. Changes that happen out of sight are announced: a sync problem, "Copied", a note moved to the trash.
speak()insrc/lib/a11y.tssays a message through a polite live region. - Gestures on a touch screen (
src/lib/gestures.ts) are extras, each doing what a button does: a swipe from the edge is Back (or the sidebar's button), a pull down the search field, ⌘F's find bar or Refresh Feeds. So VoiceOver, TalkBack, Switch Control and a keyboard reach all of it without them; their drawings are hidden from screen readers, and where they go, focus goes as the button would leave it. Settings → General → Touch screen → Swipes and pulls turns them off, for anyone they get in the way of. They take no finger that's selecting text or dragging (held before it moves, or on a grip or a picture's corner), nor one scrolling a wide table sideways. - The search field on a phone is put away above the list until a pull shows it, as iOS's Mail and Notes do, but it's still in the page, not hidden: Tab, ⇧⌘F (Ctrl+Shift+F) and a screen reader reach it, and it shows as it takes focus. It stays while it's searching or has focus.
- Motion. With reduced motion turned on in the system, slides and swipes don't animate (a swipe or a pull down still follows the finger, then settles at once when it's let go), nor do a dragged block's drop line and its lines sliding into place, and GIFs from GIPHY are still.
- Size. Targets are at least 24 × 24 px (WCAG 2.2's minimum), 44 × 44 on touch screens. Text sizes are relative, so the system's text size and zoom work; nothing is cut off at 200% zoom. Notes' own text goes from 12 to 28 px, in Settings → Typography or with ⌘+ and ⌘− (Ctrl elsewhere), and ⌘0 brings back its usual size; each change is said aloud. On touch screens Lines' own text is at iOS's sizes (17 px for rows, fields and menus), and on iPhone and iPad it follows the text size chosen in iOS's Settings (Dynamic Type), from xSmall to xxxLarge.
- Zoom. In the iPhone, iPad and Android apps the page never zooms, as no app's screen does: notes' text is made bigger in Settings → Typography, the rest with the system's text size. On the web, pinching to zoom is left alone, as people rely on it: in Safari on iPhone and iPad Lines only keeps it from zooming into a field that takes focus (
maximum-scale=1, which Safari holds only for that, never for pinching); the search field and the fields in Settings and dialogs are 17 px on touch screens anyway, past the 16 px under which Safari zooms. Chrome and other browsers zoom as they always do (viewportinsrc/lib/device.ts). - Hide toolbars (Settings → Layout) keeps the bars out of sight only from the pointer: Tab and F6 reach them as always, and they show as soon as focus moves into them; on touch screens they always show. Icons off shows a button that's only an icon as its accessible name, the words a screen reader reads, and keeps the icons that tell something (checkmarks, the chevrons of what opens and closes), and shows a note's pinned and locked marks as the words screen readers already read for them.
- A long press (
src/lib/longPress.ts) is a touch screen's right-click: every menu it opens also opens with a right-click, the context-menu key or ⇧F10 on what has focus, so VoiceOver, TalkBack and a keyboard reach the same menus without holding. What's held sinks and dims a little as the finger stays and a tap is felt as the menu opens, both extra to the menu itself; with Reduce Motion it only dims. - The round + on phones (at the bottom of the note list; Settings → Layout → Add button on phones) is a button named for what it does where you are ("New note", "Add to Library", "Subscribe to a Feed"), the same name as the title bar's button it stands in for. Slid away as the list scrolls down or while the keyboard is up, it's still in the page: Tab reaches it, and it comes back as it takes focus. Its menu of other kinds, held open with a finger, opens with a right-click, the menu key or ⇧F10 too, as a menu named "New". Escape out of Add to Library puts focus back on it.
- Scroll bars are on unless turned off (Settings → Layout → Scroll bars). Off, they're gone everywhere, and everything still scrolls by trackpad, wheel, touch and the keyboard (arrows, Page Up and Down, Space, Home and End), so it's a choice of look; on is the default, as they show how long something is and can be dragged.
- Contrast. Settings → Theme → Contrast → Increased (or the system's Increase Contrast, which System follows) darkens each theme's grey text, accent and borders: text at least 9:1 against its background, secondary text 7:1 (AAA), faint text (dates, counts, hints), links and tags 4.5:1 (AA), borders 3:1, and any color a theme of your own gives formatting in notes (a heading's, bold's) 7:1 on the note. The colors are worked out from each theme's in light and dark, yours too (
moreContrastinsrc/lib/themes/palette.ts). The standard look keeps its lighter greys, which are below AA for faint text (see Limitations), except in the accessibility themes below. Nothing is told by color alone (a sync problem has its icon and its words, not only red). - Dark panes (Settings → Theme) take the theme's dark colors as dark mode does, with Increased contrast's, so text in them has the contrast it has in dark; Monochrome and Invert change them with the rest.
- Changing colors by right-clicking (Settings → Theme) opens with the menu key or ⇧F10 too, for what has focus, as a dialog named "Colors here, in
" whose fields are named by the color ("Sidebar", "Tags"); Esc closes it and focus goes back. The bar saying it's on is a status, read as its count changes. Colors chosen this way aren't checked for contrast: Increased contrast still works them out to its ratios. - Monochrome and Invert (Settings → Theme) show any theme in greys, or turned light for dark, for people who find color distracting or want less light, without the whole screen changing as the system's display filters do. Both keep the contrast between every two colors exactly (Monochrome keeps each color's luminance; Invert mirrors it so ratios hold), so Increased contrast and the accessibility themes keep their ratios with them. Pictures in notes aren't changed.
- Paper (Settings → Plugins → Paper) is off to begin with, and faint when chosen: its color at about a tenth of its strength behind the text (Opacity makes it stronger, up to 60%), so it takes little from the text's contrast. A color chosen for it goes grey with Monochrome and turns with Invert, as the theme's own do. Its patterns and textures are two groups of radio buttons: Tab reaches each, the arrow keys choose, and the pictures are hidden from screen readers, which read each choice's name.
- Backdrops sit behind the page, never behind text: the page keeps the theme's background, or a color chosen for it, and can be made no less than 60% solid, the rest blurred, so text keeps its contrast over any picture. The toolbar over a backdrop is frosted so its buttons stay readable. Monochrome turns the backdrop grey too. The backdrops are a group of radio buttons like the paper's; with no picture yet, choosing Image opens the file chooser, and Choose Image… is a button.
- Pictures from Wallhaven are described by the words they were found with, as Wallhaven's search gives no description; the picker is the same as Unsplash's and GIPHY's, by keyboard (arrows through the results, Enter to pick).
- Links to folders and files on the computer say which they are to screen readers ("Folder", "File") before their name, as their icon shows; following one that isn't there any more, or copying its path on the web, is said aloud.
- Line marks aren't told by color alone: each has its label on pointing at it, and a note's own are comments in the text, which a screen reader hears on the line being edited, where they're shown. Mark Lines is a key (⌘⇧M), listed in Settings → Shortcuts. The marks plugins add are only seen for now (Limitations).
- A mascot (Settings → Plugins → Mascots) is off to begin with, and only decoration: hidden from screen readers, never in the way of the keyboard, never over the text you're writing (it sits in the margin or past the line's end). Whatever it says is said again nowhere it matters. With the system's Reduce motion on it doesn't walk, hop, float or fall: it's at once where it goes, beside the line you're writing or back on the floor, and otherwise sits, naps and cheers where it is.
- Cursors (Settings → Cursor): a block or underline text cursor, or a thick bar, is easier to find than the thin one; Blink → Off keeps it still, as anyone bothered by blinking may want. With the system's Reduce motion on, it doesn't glide or trail, sparks don't fly, and nothing follows the pointer, whatever's chosen. The Retro and Dot pointers keep the system's text cursor over fields and notes; for a bigger pointer, the system's own size setting is the one to use, as it reaches every app.
- Copy what you select (Settings → Editor) is off to begin with; on, a selection made with the pointer is copied when it's let go, and screen readers hear "Copied". Selections made with the keyboard aren't copied, so moving through a note with ⇧ and the arrows never changes the clipboard on its own.
- Typing practice (a
```typingblock) is the keyboard's: its text field is named, its passage is its description, ↓ and ↑ go in and out of it as into any block and Esc back to the note, and screen readers hear how it went when it's done. The time stops while the keyboard is elsewhere, and there's no time limit. - Typing sounds (Settings → Editor) are off to begin with, and say nothing a screen reader doesn't: they're for the feel of typing, never the only sign of something. They play only for keys pressed in Lines, under the system's own volume and Volume in Settings.
- Presets (Settings → Presets) change shapes, type and lines, never what's there or how it's reached: every control keeps its name, keys and focus ring (Classic's a dotted one, as its time had). Their colors are themes like the others, with Increased contrast's colors worked out as theirs are. Neon's glows and scan lines go with Increased contrast, and Pixel and Adventure turn off their font's ligatures, which it draws poorly. Adventure's notched corners would cut off a focus ring around them, so its rings are drawn inside; Brutalist's are a thick ring in the accent, and Constructivist's, like Adventure's, are drawn inside its wedges. Aero's frosted glass and gel buttons turn solid with Increased contrast, and the shine on its colored buttons stays above their text. A preset never changes Contrast, Light or dark, or the text's size: those stay as you set them.
- Fonts installed on the device (Settings → Typography → Installed font) are found in a combobox (Bits UI's): typing narrows the list, which ↓ opens too; ↑ ↓ Page Up and Page Down move through it, Enter chooses and Esc closes it, Settings staying open. Screen readers hear how many fonts there are as it opens and once typing pauses, or why there are none ("No font called … is installed here"). Each font's name is drawn in that font, and read as its name; a symbol font (Webdings) draws its name as symbols, so it's best found by typing. A chosen font this device hasn't is said under the field, and read with it (its
aria-describedby). - Fonts for formatting (Settings → Typography) are the same combobox, one a row named for what it changes (Headings, Bold…), its fonts in groups a screen reader names (Recommended, Installed) after what none chosen is (Same as text, the code font, or a style's own for headings). Nothing changes until one is chosen. Formatting doesn't lean on its font alone: bold is still bold, italics slanted, links underlined and code on its background, whatever font each is in. A chosen font that isn't used here is said under its field, and read with it.
- Headings' color (Settings → Typography) is the text's to begin with. The accent keeps the contrast the theme gives it, Increased contrast's too; a color of your own is used as chosen, so one that reads well on both light and dark pages is best, and Monochrome and Invert change it as they change the theme's.
- Your own themes (Themes) get Increased contrast too: Lines works their darker grey text, faint text, accent (and the text on it) and tags out from their colors as they change, to the same ratios as its own themes. In their editor, each part's swatch is a button that opens Lines' color picker (below), named for the part ("Choose a color for Accent"), beside the name of the palette color it's drawn in; a part Lines draws a little darker or lighter to read says so in its note. The palette each scheme is drawn in is a select named for it ("Palette for light"); a theme of Lines' own shows its palette as a picture named with its colors ("Nord: Polar Night 1, Polar Night 2…"). The preview is a picture, hidden from screen readers, as the colors are all in the rows. Deleting asks first in the page, and focus goes back to the Theme heading after.
- Palettes (Settings → Theme) are a radio group, one Tab stop, the arrow keys moving through every palette, Lines' and yours, each named; their strips of colors are hidden from screen readers beside the name, and the colors are listed by name below. In a palette of yours, each color is a row of a list: its swatch (a button, "Choose a color for Teal"), its color as text and its name, each labelled ("Name of Teal"), and buttons named for it ("Move Teal up", "Remove Teal"). Moving one keeps focus on its arrow (or the other, once it reaches the end); removing one says so and puts focus on the next row's; adding one puts focus on its color. Deleting a palette asks first in the page, with focus on Cancel, and while themes of yours are drawn in it, a select names them and the palette they'll be drawn in instead. New and Import name what they make ("New Palette", "Import a Palette").
- The color picker (a color's swatch, in Settings and in the colors opened by right-clicking) opens with Enter or Space as a dialog named as its swatch is, with focus on the color chosen; Esc closes it and focus goes back to the swatch (in WebKit too, where clicking a button doesn't focus it). The palette's colors are a radio group, one Tab stop, the arrow keys moving through them and choosing, each named ("Polar Night 1", or from its look: "Teal", "Dark Gray 2") for screen readers and in its tooltip, the chosen one ringed in the text's color, which shows on every swatch. The square of saturation and brightness is a slider: ← and → change the saturation, ↑ and ↓ the brightness, 1% a press (⇧ 10%), and a screen reader hears both and the color ("Saturation 67%, brightness 60%, #336699"); the hue is a slider too, 1° a press (⇧ 10°), heard as "210°, #336699". The color is a text field as well, so any color can be typed rather than found. The eyedropper, where the browser has one, is a named button. In forced colors the swatches, the square and the hues keep their own colors.
- Themes for low vision and color blindness. Settings → Theme has a group of its own, Accessibility:
- High Contrast: black on white or white on black. Every tier of text (secondary and faint too) is at least 7:1 (AAA) on every surface it sits on: the panes, a hovered or selected row, chips, code, callouts, highlights, selected text. The accent (deep blue in light, cyan in dark) is 7:1 too; borders are 6:1 or more; a chosen segment is ringed rather than shaded. Callout, danger, success and code colors are 4.5:1 or more.
- Red-Green Friendly, for protanopia and deuteranopia (after GitHub's theme for them): built from the Okabe–Ito palette. Nothing relies on red against green: the accent and success are blue, danger is vermillion, and the five callout kinds and the code colors differ in lightness as well as hue.
- Blue-Yellow Friendly, for tritanopia: nothing relies on blue against green or yellow against violet. The accent and danger are red, success is blue.
- In both color-blind themes all text, faint text included, is at least 4.5:1 (AA) on every surface. Simulated with Machado et al.'s matrices, the callout kinds, danger/success/pin and the code colors stay at least 7 apart (CIEDE2000) for the color blindness each is for, where the Lines theme's callouts drop below 1 for deuteranopia.
- Forced colors. In Windows' contrast themes (forced colors) the system replaces Lines' colors and drops backgrounds and shadows, so
app.cssandeditor.cssmark what those showed with system colors instead: the open note's row, the current sidebar item, chosen options and sections, menu items, switches that are on and ticked checkboxes inHighlight, with their text inHighlightText(taken out of forced colors, which would otherwise draw a backplate over it); switches and sliders keep an outline, as their backgrounds are dropped; focus rings inHighlight; mentions and links inLinkText; chips, inline code and code blocks outlined; highlights inMark. Markdown hidden by making it transparent stays hidden (forced-color-adjust: none), as do the theme picker's swatches, which show each theme's own colors. - Language. The page's
langis the app's language, so screen readers read it right; notes are read as written.
The editor
The editor is CodeMirror, whose text is real text a screen reader reads, with its own keyboard handling. What Lines draws over it:
- The note is a text box named "Note", marked as language-unknown (
lang=""), so it's read in the device's languages rather than the app's. Drawn Markdown reads as its text. - Headings are headings (
role="heading"with their level), so a screen reader's heading navigation (VoiceOver's rotor, NVDA's H) moves through a note's sections. Quotes are quotes. Bullets say "bullet"; numbers read as written. - Markup that's hidden from sight but still in the text is said in words instead: a callout's
:::!lines read "Warning callout" … "End of warning callout" (a card's, "Card" … "End of card"), the properties'---lines "Properties" … "End of properties", a code block's fences "Code" … "End of code", and a page break is a separator named "Page break". With the cursor on the line, its Markdown is there as usual. Settings → Editor → Show Markdown can keep all of it in sight (Visible) or show it as written (Source), where a screen reader reads every character; Hidden keeps**,#and list markers out of sight and out of reach of the cursor, so they're never read, while headings, lists and checkboxes are still said as such. - Checkboxes are
role="checkbox"witharia-checked, named by their task; ⌘↵ on the line ticks them. - Chips (mentions, links drawn short like GitHub's and arXiv's), copy buttons, tables, images and files have names; images use their alt text (without a width written after a bar,
|400). - Audio is a group named by its file, with a Play (or Pause) button and a Position slider read as "0:12 of 3:15"; video has the browser's own controls. ↑ and ↓ stop on them, as on an image; with one selected, Enter plays it and puts focus in its player. In audio, Space pauses and plays, ← and → skip a few seconds, and Home and End (on the slider) go to the start and end; on a video, Tab reaches its controls. Esc puts focus back in the note with it selected. These are in Settings → Shortcuts, with a recording's.
- An image's or video's resize handle is for a pointer only; from the keyboard, the width is the number after the bar in its Markdown (
,[Sky.mp4|400](…)), shown while the cursor is on its line. A diagram's is the same, with its width after the language on its first line (```mermaid |400). - Symbols shown for typed characters (
->as →,!=as ≠) are read as the symbol ("right arrow", "not equal to"), as they look. With the cursor touching one, the typed characters are there to read and edit; Settings → Typography → Font ligatures turns them off for anyone who'd rather hear the characters. - Menus (
/,\,@) are CodeMirror's autocomplete, a listbox the screen reader follows. - Everything a click opens in a note, ⌥↵ opens from the cursor: a link, an attached file, a mention's note (made if it isn't there yet), a tag's notes. Buttons drawn in a note (copy, format, a table's controls, Open after a link the Library has already, named "Open it in your Library") are reached with Esc, then Tab, as CodeMirror leaves the editor.
- ⌥↑ and ⌥↓ on a heading's line move its section, as dragging its grip does; the cursor stays on the heading where it goes.
- A heading's chevron, which folds its section, is a button named for the heading ("Fold “Packing”", "Unfold “Packing”") that says whether it's open (
aria-expanded). It's out of the Tab order, so Esc and Tab from a note go on to what's next (its properties, beside or after it) rather than through one for every heading; the keys do the same from the cursor: ⌘⌥[ and ⌘⌥] (Ctrl+Shift+[ and ]) for the section it's in, ⌃⌥[ and ⌃⌥] (Ctrl+Alt+[ and ]) for all of them, and folding or unfolding one is said ("Folded “Packing”"). The "…" after a folded heading is a button named "Folded section: show it". What's folded is still in the note's text a screen reader reads by line, as the cursor opens a fold it goes into; folding hides it from sight only. On a touch screen the chevrons always show, a little taller to tap. - The format toolbar over selected text is a toolbar: Tab into it, ← and → between its buttons, Esc back to the text.
Spreadsheets
A spreadsheet's grid (src/plugins/spreadsheet/Grid.svelte, Spreadsheets), a spreadsheet note's or a ```csv block's in a Markdown note, is worked entirely from the keyboard, with the keys other spreadsheet apps use.
- One text field over the current cell takes the keyboard, named for the cell ("Cell B4") and holding what it shows, so a screen reader reads where focus is and what's there. Moving with the keys says the cell and its value ("B4: 1,650.50"), and inserting or deleting rows and columns says what happened.
- The grid is a
gridwith its rows, column letters and row numbers marked as such, and the selected cellsaria-selected. With the letters and numbers hidden (Settings), each cell is still read by its name (B2). Numbers below zero shown in parentheses or red are read with a minus. As it's inside the note's text box, a screen reader may not browse it as a table (Limitations). - The bar above a note's grid shows what's written in the current cell, a formula rather than its result. A block has no bar; the text field holds the formula as soon as the cell is changed (Return).
- Writing a formula, the suggested functions are a
listboxthe text field controls (aria-controls), and each one ↑ and ↓ reach is said with what it does. (Pointing at it witharia-activedescendantinstead makes WebKit take focus out of the field, closing the cell.) The argument hint describes the field (aria-describedby). The colors of references are also outlines and their cell names, never color alone. - The cells' menu opens with ⇧F10 (or the menu key), and gives focus back to the grid when it closes, as every menu in Lines does.
- What's done by pointer has keys or menu items too: moving cells is cutting and pasting; a block's size is inserting and deleting rows and columns; its name is the menu's Name, a text field above the grid; converting it to a table is the menu's Convert to Table. A table's Convert to Spreadsheet button, and a CSV file's, are reached like a note's other buttons (Esc, then Tab). The corner handles are hidden from screen readers.
- The selected cells' sum and average describe the text field (
aria-describedby), so a screen reader can read them with the cell; sorting, filling, moving and resizing say what they did. - Filling by dragging the selection's corner has keys too: ⌘D and ⌘R copy, and the menu's Autofill Down and Autofill Right go on from the cells written at the selection's start, as dragging does. Filling says how many cells were filled. The corner itself is hidden from screen readers, as it's only for the pointer; it's bigger on a touch screen.
- ↑ from the first row goes to the title; Return, Tab or ↓ from the title goes back into the grid.
- A block in a Markdown note isn't a trap: ↓ on the line above it goes into its first row and ↑ on the line below into its last, and ↑ from its first row or ↓ from its last goes back to the text. Its menu's Edit as CSV shows its text in its place, to read or change as text.
Scores
- A score drawn as marks (Settings → Little Touches) is an image named as it's said, "4 out of 5", "3.5 out of 5", its marks hidden from screen readers; with the cursor on its line it's the text as written. Filled and empty marks differ in shape (filled or an outline) as well as in color, and half of one is filled to its middle. A library note's rating is named the same, on its kind's scale: points ("85 out of 100"), a word ("A", "Thumbs Up").
- Rating needs no pointer. A shelf's row's menu (⇧F10 or the menu key) has Rate, a menu of its own that → or ↵ opens and ← closes, the scale's values as checked choices, the one set checked; with named ratings, a menu of each. In a note, typing a key in the properties offers the kind's ratings and then their values, as the "@" menu offers notes (↑ ↓, ↵ or Tab); or the value is typed. Whichever way, setting or taking one out says it ("Rated 4 out of 5", "Rating removed"), and ⌘Z takes it back. A click on a mark is the pointer's way to the same.
- Settings → Library → Ratings: each kind's scale is a select named for it ("Show scale"), and the pencil beside it, a button named "Show ratings" that says whether it's open, shows its named ratings as fields named by place ("Rating 1"), each renamed as it's left or with ↵, with buttons named for what they do ("Move Story up", "Remove Story"); focus stays on the rating moved. What's added, renamed, moved or removed is said. A mistake (a name taken) is an alert. A scale of your own is made in a form named "New Scale": its name, what it's in (a radio group), how many it's out of, its icon (a radio group of icons named by what they are, "Hearts"), or its words.
The Calendar
- The month above the note list is a
grid(a table) named by the month ("November 2026"), its columns headed by the weekdays (narrow letters on screen, the full names to a screen reader). It's one Tab stop, on the chosen day; the arrow keys move by day and week, Home and End to the week's ends, Page Up and Page Down by month (⇧ by year), as date pickers do, and focus follows into other months. - Each day is a button read with its full date and how many notes are on it ("Friday, November 28, 2026, 3 notes"); the chosen day's cell is
aria-selected, and today isaria-current="date". The dots under a day with notes, one for each of their colors, are hidden from screen readers, as the count says it: color is never all there is to go by. Changing month is announced, the month's name being a live region. - The icon picker's colors (a tag's or type's, Icon and Color) are a radio group, one Tab stop, ← and → moving between them, each named ("Green", "No Color") so a screen reader says which is chosen. Every theme's colors are at least 3:1 against its backgrounds, as icons need.
- ↵ on a day does what a double-click does: a new note dated that day. The list below is the note list as everywhere else, so F6 and the arrow keys reach the day's notes.
- The week or day beside it is a region named by its dates ("November 8 – 14, 2026", announced as it changes), with Day and Week as a radio group and named buttons to move. Each day's heading is a button named with its full date (today
aria-current="date") that shows the day alone. What's on a day is two lists, "All day, Monday, November 9, 2026" and the day's timed notes, each a button read with its title and time ("Design review, 10:00 – 11:00 AM"); Tab goes through them in order. The hour labels and the line at the time now are hidden from screen readers. Making an event at an hour or of whole days (dragging down the hours or across All day, or double-clicking), moving a note to another time and changing its length (dragging) are for a pointer; a new one's title is typed where it is, in a field named "Event name" that takes focus (Enter keeps it; Esc, or nothing typed, and the event is gone); by keyboard, ↵ on a day in the month makes a note for the day, and its times are typed in its properties (start,end), which is all a drag changes. After a drag, what was done is said ("Moved Standup to 1:00 – 2:00 PM"), and ⌘Z undoes it. A repeating event is read with "repeats" after its time, or its title for one all day. Each event has a menu, as a note in the list does (the context-menu key or ⇧F10 on it): Open, Rename, Repeat (a menu of how often, the one chosen checked, and said once chosen) (a field named "Event name", Enter keeping the name and Esc not, focus going back to the event either way), Icon and Color, and Move to Trash.
The sidebar's layout
- The Types and Tags headings are buttons with
aria-expanded, controlling the list under them, so folding a section is heard and done by keyboard (Enter or Space). - The places at the top are in sections, each a list; a named one's heading is a button like Types' (folding it,
aria-expanded), and its list is labelled by it. Move to New Section is in each place's menu (as New Section is in the empty space's), so a section is made by keyboard; its name is a text field named "Section name", ↵ to keep it, Esc to leave it. ⌥↑ and ⌥↓ move a place across into the next section up or down. Rename, Name Section and Delete Section are menu items. - A section heading's menu sorts what's in it: Sort by Name, Sort by Number of Notes and Sort Manually are checkbox items (
menuitemcheckbox), the one in use read as checked. - A divider between places is a button named "Divider", so it can be focused, moved with ⌥↑ and ⌥↓ and given its menu (the context-menu key or ⇧F10) like a row; it does nothing when pressed.
- Dragging a sidebar row has keys: with a row focused, ⌥↑ and ⌥↓ move it past the row shown above or below, focus staying on it, and "Moved up" or "Moved down" is said; they're the keys that move lines in a note, and they're listed in Settings → Shortcuts. Each row's menu (⇧F10 or the menu key) has Hide, and Show Hidden lists what's hidden as a menu of named items; hiding says how to bring it back. Dragging is for a pointer; a finger scrolls.
- Dragging a note out of the list as a file is for a pointer too; the share menu's Download does the same by keyboard.
The Inbox
- The Inbox is a row in the sidebar like the others, read with its count. Mark as Filed and Move to Inbox are in a note's menu (⇧F10 or the menu key in the list) and the menu and toolbar for picked notes, and what they did is said ("Filed", "Moved 3 notes to Inbox"). An empty Inbox says "Nothing to sort."
The Library
- A note that's just a link says "Looking up…" through the live region as it's looked up, "Added Dune: Part Two to the Library" once it's filled in, and "Couldn't look this link up" when it can't be; the words shown after the link in the note are the same, and hidden from screen readers so they're heard once. Nothing moves focus: the cursor stays in the note, at the end of its new title. ⌘Z puts the link back as any edit, and "Link put back" is said when it's put back from outside the note.
- The Library's shelves are sidebar rows like the others, read with their counts, reordered with ⌥↑ and ⌥↓; the + on its heading is a button named "Add to Library" (with feeds on, its menu has Add to Library and Subscribe to a Feed). Add to Library is a dialog of that name: what to search for is a radio group ("What to search for", the arrow keys choosing), its field is named, and its results are a listbox the arrow keys move through, each option named by its title and who made it, the count of what's found said as it changes; its covers are decoration. On a shelf, a row reads its title, what it's by and its status before its date; its cover is decoration, hidden from screen readers. Its menu (⇧F10 or the menu key) has the statuses as checked choices, and choosing one says it ("Status: Reading").
- AniList's and MyAnimeList's groups in Settings → Library: the token's field is named by its row ("Sign in"), signing in and out is said ("Signed in to AniList as ada"), waiting for the browser is a status with Cancel, and a token not taken is an alert. How keeping the list in step is going is the note under who's signed in; what importing would do and the import itself are as Readwise's.
- A link in a note has a menu of its own, from the keyboard too: with the cursor on the link, ⇧F10 or the menu key opens it there (Open Link, Copy Link, Add to Library), and closing it gives the keyboard back to the note. Adding the link is said as a note that's a link is ("Looking up…", "Added … to the Library", "Nothing found for this link").
- Each row of feeds is read by its kind (or a stream by its name) with its unread posts ("RSS Feeds, 12 unread"; "Feeds, 12 unread" when they're together; "Must read, 3 unread"), and each feed under it too, with why it couldn't be fetched if it couldn't; the button beside a row that shows its feeds is named for it ("Show the feeds in RSS Feeds") and says whether they're shown, and the list of them is named as the row. ⌥↑ and ⌥↓ move a row, with its feeds, as they move the Library's others. A feed's menu's Add to Stream is a submenu (→ opens it, ← closes it), and New Stream… and a stream's Rename… open a dialog of that name with its field named; what's done is said ("Added … to Work"). Dragging a feed onto a stream has the menu as its keyboard way. A feed's Filters… is a dialog named for it, its two fields labelled ("Only show posts with", "Hide posts with"), Esc closing it; a post filtered out says why in its row, among those dismissed. The box to subscribe is a dialog: its field's name says what it takes, "Looking for the feed…" and "Subscribed to …" are said, and why there's no feed is read with the field. In the list of posts, a row reads its title, "unread" if it is, where it's from and when, then its excerpt after a pause; ↑ and ↓ open the post above or below, and Tab reaches the list once. E or ⌫ dismisses the post focused and N dismisses it as not interesting, saying so ("Dismissed “…”"), and focus goes to the post opened or listed in its place, or, with none left, to Show Dismissed; ⌘Z puts it back. A row's Dismiss button, shown as it's pointed at or focused, is out of the Tab order, as the keys and the row's menu do the same; a dismissed post not interesting says so in its row. An open post is the note's read-only text, named "Post: …", read as a note is; Save to Library, Mark as Unread, Open in Browser, Not Interesting and Dismiss (Restore, for one dismissed) are named buttons over it, and in the row's menu; dismissing it opens the next and keeps focus on the button.
- A post's discussion (Hacker News') is a region under it named by how many comments there are ("312 comments"), its heading a level-two heading; "Loading comments…", then the count or why there are none, is said through a live region that's always there, and a failure is an alert with Try Again. Its comments are nested lists, so a screen reader says how deep each is. Each comment's header is a button, read as its author ("who posted it" after the poster's), whom it answers where it's too deep to be drawn in, and how long ago, that folds the comment with its replies (
aria-expanded; folded, it says how many replies went with it). The discussion is one stop for Tab, on the comment the keyboard was last on (a roving tab stop), and the first comment says the keys: ↓ and ↑ (or J and K) go to the next and previous comment shown, past those folded; → unfolds a comment, or goes to its first reply; ← folds it, or goes to the comment it answers; Home and End go to the first and last; ↵ and Space fold and unfold. Focus moves with the keys, so a comment not yet drawn is drawn, and one out of view comes into it. A comment's links are reached by Tab only from it (↵ opens one), so the thousands of links in a big thread aren't each a stop; they're named by their text and opened by Lines in the browser. Open on Hacker News is a button, and the byline's Comments moves focus to the discussion. Quotes areblockquotes. - An import into the Library (Settings → Library: Bookmarks, Readwise) says what it found before anything's written, said when it's found; focus goes to Import (to Cancel, with nothing to import), then to how it's going, a status with its progress bar named as it reads ("Importing… 250 of 1,000") and Stop, then to Undo Import, with what it did said; undone, focus stays where Undo was. Readwise's token field is named "Access token", its note read with it; while Readwise is asked, focus is on its Cancel, and when it can't be (a token it doesn't take), the message is said and focus goes back to the field, the token in it to correct.
- A book read in its note's place is a region named for the note. Read the Book over the note says whether it's pressed by its name (Back to the Note), and the keyboard goes into the book as it opens. A PDF is one document named for the book, its text the page's own, in order, to read and choose; an EPUB's frame is named for it, its chapter real text with its headings and links (each a link, Enter following it). ← and → (← going on in a right-to-left book), Page Up, Page Down and the space bar turn pages; every other key is Lines' as anywhere (⌘Z, F6). Contents and the search's matches are menus the arrow keys move through, the contents nested by indent, the matches under their chapter's or page's name as a group heading, the count found said as it's known. Pages and Scroll are a radio group, named on a phone where they're icons; the paintbrush says whether it's pressed; under the book, where it is ("Page 3 of 300", a chapter's name) is said as it changes. Keeping a quote says so ("Quote kept, from Page 3"), and gives the keyboard back to the book. On its shelf, a book's row says how far it's been read ("37% read").
- The podcast player is a region named "Podcast player": its episode's title and show are a button that opens it, its buttons are named (Back 15 seconds, Play or Pause, Forward 30 seconds, "Speed: 1.5×", Stop and close the player), and its position is a slider that ← and → move 5 seconds, read as "3:05 played, 28:17 left"; a message says when an episode couldn't be played. An episode row's play button is for a pointer, kept out of Tab's way; from the keyboard, Play Episode is in the row's menu and over the open post, and an
episodenote's Play button is reached as a note's other buttons are. A row says how much of an episode is left, or that it was played. - Notes while listening (Library) work from the keyboard: the player's keys (⌃⌘P, ⌃⌘←, ⌃⌘→) from anywhere, a note's text too, and ⌃⌘T or
/timeto write the time. A time in a note is a button named "Play from 12:34", reached with the cursor (⌥↵ plays it), and read as its text while the cursor's on it. Take Notes and Transcript are named buttons in the player, Take Notes busy while it saves, Transcript saying whether the transcript shows and which element it controls. Take Notes and Quote in Note move focus to the note's text, where they wrote; when they can't, or someone was typing elsewhere meanwhile, the live region says why (in the Trash, locked, couldn't be saved, the note's ready) and focus stays. Writing the time with nothing playing says so through the live region, and quietly after the cursor for a moment, hidden from screen readers so it's heard once. Enter that starts a note's next item with the time the episode is at says the time ("At 13:02") through the live region, as it isn't otherwise heard. The transcript is a list named "Transcript": one line takes Tab (the one playing, or the first), ↑ ↓ Home End move between lines, each a button that plays from it, read with its time and speaker; the line playing isaria-current, chapters read as "Chapter …", and the chapter's title above is a polite live region. Its height is capped so the sidebar stays usable.
Pane edges
- Several notes are picked from the keyboard too: ⇧↑ and ⇧↓ pick the way, ⌘A (Ctrl+A) picks every note, Esc lets them go, ⌫ moves them to the Trash. A picked row says "Selected" after its title, the count is announced as it changes ("3 notes selected"), and so is what's done to them ("Added #work to 3 notes"). The bar above the list is a toolbar of named icon buttons; the Add Tag box is a dialog whose field is a combobox, with its suggestions as a listbox (↑ ↓ to choose, Enter to add).
- The sidebar's and the note list's inner edges (their right edges, or left ones when they're on the right) are window splitters (
role="separator"with their width asaria-valuenow, named "Sidebar width" and "Note list width"), and Tab stops: ← and → move the edge by 10 px (⇧ by 50), Home and End go to the narrowest and widest, Enter back to the usual width. Focused or pointed at, the edge shows an accent line (Highlightin forced colors). - With the sidebar or the note list on the right (Settings → Layout), F6 still goes through the panes from left to right, and the button that shows the sidebar is on its side.
- Settings → Editor → Links is a table: each kind of link a row header and each click a column header (read as words, "Shift Command click"), and each choice a select named by both ("Mentions, Command click"). Whatever a click is set to, the keyboard reaches every link: ⌥↵ opens what the cursor is on.
- The outline (when it's on) is a navigation landmark named "Outline" holding one Tab stop, a "Headings" button (
aria-expanded). Enter, Space or ↓ opens its list of headings on the one being read (aria-current="location"); ↑ and ↓ (Home, End) move through them, Enter goes to one with the cursor there and focus back in the note, and Esc closes the list. Clicking a heading leaves focus and the cursor where they were. The current heading is inHighlightin forced colors. Screen readers can also move between headings the usual way, as each heading line is a heading of its level. - A note's properties drawn beside its text or after it (Settings → Layout → Properties) are a text field of their own named "Properties", with the same keys, menus and words for screen readers as at the top. ↑ from the note's first line goes into them, onto the last property (↓ from its last line onto the first, when they're after it), and the arrows come back out the same way, as if they were the line next to it; ⌘Z and ⇧⌘Z in either undo and redo the note's changes in order, the cursor going back to where each was. In Tab order (Esc, then Tab, as CodeMirror leaves a note) they come after the note's text: Tab puts the cursor at the end of the first property (or where it was in them) and focus stays there, and Esc and ⇧Tab go back to where the cursor was in the text. ⌘F in them opens their note's find bar. Find finds in them too, and its match shows there; closed, the cursor is on it. Where there's no room beside the text, they're at its top, read with it as before.
- Tabs (when they're on) are a tablist named "Open notes", one Tab stop: ← and → open the tab beside, Home and End the first and last, Delete closes one (each tab says so,
aria-keyshortcuts), and Enter keeps a preview tab, which screen readers hear as "preview" after its title. Their × buttons are for the pointer and hidden from screen readers; a tab's context menu also closes it, or the others. - A note open in a pane of its own is a region named "Beside: Finance", with its own toolbar (Swap the two notes, Close this note). Each line between two panes is a window splitter named "Size of the panes", its value the first pane's share in percent: ← → (↑ ↓ for panes one above another) move it, ⇧ by more, Enter shares the room evenly. Open to the Side and Open Below are in each note's menu (⇧F10 on its row), as well as ⌥-click and ⌥⇧-click; a note opens beside the pane last focused or clicked. Dragging a note onto a pane, or a pane by its grip ("Drag to move this note"), is for a pointer: the same is done by keyboard with Open to the Side, Open Below, Swap and Close. So is dragging a note onto a tag, a type, the Inbox or the Trash in the sidebar, which Add Tag, its
typeproperty, Move to Inbox and Move to Trash do from its menu, each said aloud.
Find in a note
- ⌘F (Ctrl+F) opens the find bar from anywhere while a note is open, with focus in its field, a search landmark named "Find in note". The count ("3 of 12") is a status that's read as it changes; the match case, regular expression and whole-word options are toggle buttons (
aria-pressed); the button that shows Replace says whether it's expanded. ↵ and ⇧↵ move through the matches, which CodeMirror announces with their line; Esc closes the bar and puts focus back in the note.
Photos, GIFs and papers from the web
/unsplashand/giphyopen a dialog named "Search Unsplash" ("Search GIPHY") with focus in its search field. The pictures are a listbox of options, one Tab stop: ↓ from the field goes into them, the arrow keys, Home and End move between them, ↑ from the top row goes back to the field, and ↵ puts the focused one in the note. Each is named by its description and who made it ("Snowy peak, by Jane Doe"). A status says when it's searching, how many it found, that nothing was found, or that the service couldn't be reached. Esc closes it and puts focus back in the note.- With reduced motion, GIFs show still: in the picker, and GIPHY's GIFs in notes (their first frame, which GIPHY serves).
/paperopens a dialog named "Search arXiv", the same way: the papers are a listbox, one Tab stop, ↓ from the field into them, ↑ and ↓ between them, ↵ to link to one. Each is named by its title, authors, year and subject ("Attention Is All You Need, Ashish Vaswani et al., 2017, cs.CL"). Before anything's typed, the status says what can be searched for.
Spotify and SoundCloud
- A link to either on a line of its own is a group named by the link's text (or "Track on Spotify"), with a button, "Play with Spotify". ↑ and ↓ stop on it; with it selected, Enter loads the site's player and puts focus in it, and Enter on a loaded one plays it again.
- The player is the site's own, in a frame titled "Spotify player: …": its buttons are named by the site, in the site's language. Keys pressed in it never reach Lines, so Esc can't leave it: Tab past its last button (and Open on Spotify, beside it) or ⇧Tab before its first goes back to the note's text with it selected. These are in Settings → Shortcuts.
- One that couldn't be loaded says so in words, in its place, with Open on its site.
Terminal recordings
- A recording (asciinema) is a group named "Terminal recording". ↑ and ↓ stop on it, as on an image; with it selected, Enter plays it and puts focus in the player. There Space pauses and plays, ← and → skip 5 seconds, a number from 0 to 9 jumps to that tenth of it, F is full screen, and Tab reaches its play and full-screen buttons. Esc puts focus back in the note with the recording selected. These are in Settings → Shortcuts.
- The terminal's text is real text, which a screen reader can read when the player has focus; asciinema's player doesn't announce it as it changes.
- The player's buttons are named in English ("Play", "Pause", "Toggle fullscreen mode"); that's asciinema's, which Lines doesn't translate. A recording that can't load says so in words, in its place.
- Its focus ring is the accent color, around the terminal.
Settings
- A modal dialog over the notes: Tab stays inside, Esc (or a click outside it) closes it, and focus goes back to what opened it. In the desktop apps, if Settings → General → Open Settings is In a window, a window of its own: Esc or ⌘W closes it, and the window's own buttons work as in any app.
- Its sections are a list, "Settings sections", the one showing marked as the current page (
aria-current). Appearance and Data are headings over theirs, buttons that open and close them (aria-expanded); closed over the section showing, a heading is marked as it would be and takes its place. The list is one stop for Tab: ↑ and ↓ move through it, headings too, Home and End go to the first and last, Enter or Space opens a section (or a heading), and Tab goes on into the section. It opens with the section asked for focused. Only the section scrolls, so the list stays in view. Each setting's control is named by its label, and its note is right after it. Privacy's "Open Sync" goes to the Sync section. - Narrow, the list and a section take turns: choosing a section opens it, and a Back button (named "All settings") returns to the list. Opened on a section (⌘/, the sidebar's sync button), it opens with that section's title focused.
- About → Updates (desktop apps): what Check now finds is said aloud ("Lines is up to date."), since the row changing isn't. The ↻ button the sidebar shows beside the version once an update is downloaded is named by what it does ("Restart to update to version 0.4.0").
Drawings
- A drawing in a note is an image named by its alt text ("Drawing" until it's changed). With it selected (↑ or ↓ stop on it), Enter opens it; its pencil button and double-clicking do the same with a pointer.
- A 3D model (an
```openscador```stlblock, or an attached model) is an image to a screen reader, "3D model" with its size ("20 × 20 × 20"), and says how to turn it. It's reached like the note's buttons (Esc, then Tab) and shows a focus ring: the arrow keys turn it, with ⇧ they move it, + and − zoom, and 0 puts it back, without moving the cursor in the note. Its Download Model is a named button in the block, reached the same way; its reset button is for a pointer, as 0 does the same. A model made from code has its code for a screen reader, shown by ↓ or ↑ into the block. - A Mermaid diagram's Copy and Edit as Drawing is a named button in the diagram, reached like the note's other buttons (Esc, then Tab), and shown when focused. If the diagram can't be converted, the drawing window says why, and it's announced.
- The drawing window is a modal dialog: Cancel and Save at the canvas's top right, icon buttons (× and ✓) named by
aria-label, Save's ⌘S in itsaria-keyshortcuts(in a row above it on narrow windows), with Tab kept inside and focus back in the note after. Esc in the canvas belongs to Excalidraw; on Save or Cancel it asks before discarding changes, and the question is announced. - Excalidraw's own toolbar and menus are labelled buttons and radio groups that work from the keyboard (its letters and numbers pick tools), but the canvas itself isn't readable by a screen reader: shapes and their text aren't in the accessibility tree. That's Excalidraw's, and Lines can't change it; a drawing's alt text is what a screen reader has.
The PDF preview
- A modal dialog (⌘P): Tab stays inside, Esc closes it and focus goes back. Paper and Typeset with are radio groups.
- Its pages are real text, so a screen reader reads the note in them, page by page ("Page 1 of 2" is each page's name); a paragraph that runs onto the next page is read once, on the page it starts on. Todo boxes say "Done" or "Not done", and math reads from KaTeX's MathML.
- "Laying out pages…", "2 pages, ready", the TeX download's progress and its errors are announced, as is where a PNG or PDF was saved.
- Save PNG opens a small popover with two buttons (One Image, One per Page), reached with Tab after the button; Esc closes it.
- TeX's PDF shows in the web view's own PDF viewer, whose accessibility is the browser's (a PDF from pdfLaTeX isn't tagged).
Checking
The release checklist (qa/checklist.md) has a section for this: Lighthouse's accessibility audit, a pass with the keyboard alone, and one with VoiceOver.
Every theme's highlighter, status and callout colors are its own (from its palette, or Lines' own adjusted to it). Where a palette's color falls short of what its part needs, Lines draws the part in it made just light or dark enough, its hue kept (GOALS in src/lib/themes/palette.ts), in your themes and imported ones too. tests/unit/plugins.test.ts checks that they still read: danger 4.5:1 on the note and in menus, success and callout icons 3:1, text 4.5:1 on the danger, success and pin buttons, the colors tags, types and events can have 3:1 on every background, and text on a highlight at 4.5:1 (or as much as the theme's text has on its background).
Increased contrast's colors are worked out from a theme's as it's shown, so a theme changed has them at once: each one is the theme's own color mixed toward its text (then toward black, or white in dark) until it reaches its ratio against the note's, the list's and the sidebar's backgrounds. A theme with its own text on the accent (on-accent) needs one that reads on the new accent too, 4.5:1.
The accessibility themes are checked more widely, since they promise more: each text color against every surface it can sit on, composited as the browser draws it (rows, chips, code, callout tints, highlights, selections), and their callout, status and code colors against each other under simulated color blindness (Machado et al. 2009, compared with CIEDE2000). A color changed in one of them needs both checks again.