Accessibility

Last updated: October 2026

Our goal

Re:Vault aims to meet WCAG 2.2 at level AA. It is built for the way school Chromebooks are used: a keyboard, a touchscreen and a trackpad at the same time, tablet mode and the on-screen keyboard.

What works

• Keyboard: Re:Vault's own pages and tools are built to work from the keyboard, with a visible focus ring in every look. A few gaps are listed below. Alt+L always gets back to the address bar, even from inside a page. Keyboard shortcuts.
• Seeing: a High Contrast look, text contrast checked for every look, and focus rings and button borders that stay in Windows high contrast mode.
• Motion: your device's reduce motion setting is followed, and Lite mode turns off blur, shadows and animations.
• Zoom and reflow: pages work at 200% and 400% zoom, and nothing scrolls sideways at 320 pixels wide.
• Touch: targets are at least 24 pixels (one exception is listed below), nothing depends on hover, and anything you can drag also has a button or key.
• Screen readers: controls have names, frames have titles, and results, timers and messages are announced.

How we check it

We run automated checks on every page in several looks and screen sizes (laptop, tablet mode, phone, 200% and 400% zoom), and run automated walk-throughs of the main tasks by keyboard and by touch. The last full check was October 5, 2026. It found no critical or serious issues, and 9 moderate ones that are listed below.

What still needs work

• Re:Vault has not yet been tested with a real screen reader. We check it with the browser's accessibility tree and automated tools only.
• Websites and books opened inside Re:Vault are other people's pages, so their accessibility is out of our hands. Re:Vault gives each one a title, moves focus into it, and Alt+L always gets back out.
• The Linux screen is a picture. Use the Console tab for text.
• Settings is long. Use its search box, or press Ctrl+K and type the setting's name.
• On the Linux page opened on its own (not in a Re:Vault tab), leaving the terminal with Esc then Tab moves focus to the browser's own toolbar, because the terminal is the last thing on the page.
• Long-press menus (on tabs and in desktop mode) are checked by reading the code and through their keyboard path, not by our automated touch checks. The same menus open with Shift+F10 or the menu key.
• When text spacing is overridden, long book, tab and look names are cut short with an ellipsis. The full name is in the tooltip and in what a screen reader reads.
• Our automated checks report 9 moderate "region" results: the search suggestions and the tab menu are attached to the end of the page, and the desktop area in desktop mode sits outside a page landmark.
• In desktop mode, the top resize corners of a window are 16 pixels, smaller than our 24-pixel target, so they never cover the close button.
• In desktop mode, Meta+arrows, Alt+Tab and Alt+F4 are ChromeOS shortcuts that never reach the page. The window menu (Shift+F10, the menu key or Alt+Space) has the same actions.
• The strongest "Hide addresses" level swaps letters for look-alike characters, which screen readers can't read well. Leave it at Standard or Off if you use one. This page always shows plain text.

Tell us

If something in Re:Vault doesn't work for you, email hello@ajhsvault.org. Tell us what you were trying to do and on which device, and a person will get back to you.