Using BoodleBox with a screen reader

Goal

Know how BoodleBox is structured for screen readers, so you can move around quickly and follow chats as they happen.

Page structure

• Pages have a descriptive title and an ordered set of headings. Use your screen reader's heading navigation to jump between sections.

• Pages use landmarks for navigation and main content. The first links on each page are "Skip to page navigation" and "Skip to site navigation".

• Tables announce their column and row headers.

Chats

• The chat history is a list, with one item per message. Each message is announced by its sender and when it was sent.

• Attached knowledge is announced with who added it and when.

• The "New" divider that marks unread messages is read as its own item.

• Chat type marks (shared, view-only, locked) are announced in the sidebar.

• For how AI replies are announced, see Working with AI responses using assistive technology.

Controls

• Buttons have names, including icon-only buttons. Our build checks that every icon-only button and every dialog has one.

• Menu buttons say whether they are expanded or collapsed. Sidebar folders say whether they are expanded or collapsed and which list they control.

• Dialogs have a name, which is read when they open.

• A control that's temporarily unavailable, such as the bot picker in comment mode, stays reachable and explains why it's unavailable.

Messages and errors

• Success and information messages are announced politely, after your screen reader finishes what it's reading. Warnings and errors are announced right away.

• Form fields read their label, any hint, and any error. Errors are announced as soon as they appear.

• Saving status, upload errors and "Copied!" confirmations are announced.

Still stuck?

If something isn't announced, or is announced wrongly, please tell us which screen reader and browser you use. See Requesting accommodations or reporting an accessibility issue.