Accessibility at Roost
Roost has no screen to look at: it is a background daemon, a command-line tool, and two plain-text status endpoints. Here is what that means for access today, read from its code, and what nobody has checked. We do not claim a conformance level for Roost.
What Roost supports today
Each line says what the product does, how we know, and where to look. “Not yet tested” means exactly that: we have not checked, and we do not claim it.
Supported
Keyboard operation
Everything is done from the keyboard. The ten roostctl commands are typed in a terminal, and the health and status endpoints answer ordinary requests. Nothing needs a pointer.
Evidence
- src/roost/cli.py in the Roost repo wires the ten commands (init, status, top, refresh, restart, reload, verify, flip, revert, doctor); each has its own test file under tests/
Not yet tested
Screen reader landmarks and labels
roostctl prints plain text, one row or one line per item, which a terminal screen reader can read. Nobody has tried one. The live view, roostctl top, redraws the whole screen on a timer, and how that reads aloud has not been checked.
Not yet tested
Contrast in light and dark
roostctl sets no colors of its own, so contrast is whatever the terminal theme provides. No measurement exists.
Partly supported
Reduced motion
roostctl status, doctor, and verify print once and stop. Only roostctl top redraws, on an interval you choose with a flag, and it does not animate anything.
Evidence
- src/roost/cli_http.py in the Roost repo: top clears and redraws the table every --interval seconds; the other commands print and exit
Not yet tested
Text resize and zoom
Text size is the terminal's own setting, so a larger font works as it does for any command. Roost itself has no layout to break, but no one has tested it at a larger size.
Not supported
Mobile and touch
Roost is a macOS background process. It has no phone or tablet version and no remote interface: it listens on the local machine only.
No WCAG conformance level is claimed for Roost, which has no graphical interface to test. No one has used its command-line tool with a screen reader, so every claim below says what was read in the code and what was not tried.
What does not work yet
- Roost's command-line tool has not been tried with a screen reader, and roostctl top redraws the screen on a timer.
- There is no graphical interface and no measured color contrast for the terminal output.
- Roost's requirements document sets no accessibility targets.
How this site is built and checked
This site targets WCAG 2.2 level AA. That is a target we build and test toward, not a certification, and no one has audited it for conformance.
Structure
A skip link, labeled landmarks (header, navigation, main, footer), one h1 per page, and headings that do not skip levels.
Keyboard and focus
Links and buttons are native elements, so they work from the keyboard. Focus is drawn as a visible ring, and the menu closes with Escape.
Contrast
Text meets 4.5 to 1 in both the light and dark themes, checked against the stylesheet by the test suite.
Motion
Transitions and animation switch off when your system asks for reduced motion.
Small screens and zoom
Layouts hold at 375 pixels wide with no sideways scrolling, text resizes with the browser, and touch targets are at least 44 pixels.
Automated scan
Every page is scanned with axe-core at 375 and 1440 pixels in light and dark, and the checks fail on any serious or critical violation. Automated tools find only part of the problems, so this is a floor, not proof.
Images
Every product screenshot has a text description and comes in a light and a dark version that follows your theme.
Your theme choice
The theme follows your system setting until you pick one with the button in the header.
Tell us what is in your way
If something here or in Roost does not work for you, write to Renkara Media Group. Say what you were doing, what you used, and what happened, and a person will answer.
Statement last reviewed 10/29/2026.