QuillBase aims to meet WCAG 2.1 level AA — the international standard for making web software usable by people with disabilities, including people who use a keyboard only, a screen reader, or magnification.

We test the sign-in and sign-up pages, the home dashboard, spaces, reading and editing a page, profile and administration, in both the light and dark themes. Testing combines an automated check (axe) that runs against every one of those screens with keyboard-only walkthroughs by a person.

• Keyboard — Every control can be reached and used with Tab, Enter and Escape. A "Skip to main content" link is the first stop on every page, so the navigation rail and page tree can be bypassed. Dialogs take focus when they open, keep it while they are open, close with Escape, and hand focus back to the button that opened them.
• Contrast — Text and interface colours meet the 4.5:1 ratio AA asks for (3:1 for large text), in both the light and dark themes.
• Names and labels — Form fields have labels, and icon-only buttons — such as the expand and "more actions" controls in the page tree — carry names that screen readers announce.
• Visible focus — Whatever has keyboard focus shows a visible outline; focus is never silently hidden.
• Structure — Pages use landmarks (navigation, main content) and headings in order, so a screen reader can jump between regions.

These are known gaps. They are listed here rather than left for you to discover.

• Whiteboards — The whiteboard is a drawing canvas. Creating and arranging shapes needs a pointer, and a keyboard-only or screen-reader equivalent does not exist yet. Pages, which hold most written content, are fully usable without a mouse.
• The page editor — Writing, formatting and navigating text work with the keyboard. Some editor extras — dragging blocks to reorder them, resizing images and table columns — are still pointer-only.
• Imported content — Pages imported from Confluence keep the images that came with them. If an image had no alternative text there, it has none here, and only the person who owns the page can add it.

If any part of QuillBase stops you getting your work done, tell your workspace administrator — they can reach our support team and pass the problem on. Please say which page you were on and what you were trying to do, and we will take it from there.

We treat accessibility problems as defects, not feature requests.