[FEATURE] Accessibility: Incompatibility with screen readers (JAWS/NVDA)

[elessargng]

What problem are you trying to solve?

Hi,

I’ve noticed that botc.app is not fully accessible for users relying on screen readers like JAWS or NVDA. Some of the issues I encountered include:

Interactive elements (buttons, menus, options) are not properly detected by screen readers. Keyboard navigation does not always follow a logical order, and some elements are inaccessible without a mouse. The state of certain elements (e.g., whether an option is selected or not) is not properly conveyed to screen readers. Improving accessibility would make the app more inclusive and easier to use for visually impaired players. Please let me know if I can provide further details or help with testing.

Thanks!

Describe the solution you'd like

To improve accessibility, consider the following:

Ensure all interactive elements (buttons, links, menus) are properly labeled and readable by screen readers. Adding ARIA attributes (e.g., aria-label, aria-labelledby, aria-live) where necessary can help. Improve keyboard navigation by ensuring all elements can be accessed in a logical order using tab and shift + tab, and by providing visible focus indicators. (For example: Using tab you can't reach the checkbox of the Agreement in the register page) Use semantic HTML elements (,

,

, etc.) instead of relying solely on divs and spans. Announce changes in the UI using ARIA live regions (aria-live="polite" or aria-live="assertive") where needed. Adding sounds to certain events (raise/down your hand, mute/unmute mic...) Test with JAWS/NVDA and inspect accessibility properties using browser dev tools to verify improvements. This would make the app more inclusive for visually impaired users. Let me know if I can assist with testing.

Alternatives you have considered

No response

Comments

Thanks for your patient.

[gareth]

Thanks for the summary of the WCAG guidelines and recommendations that you think are relevant!

We have a ticket on our roadmap about improving accessibility and you're not the first person who's helped to give recommendations on what we should target. I've made a note of these, and when we get to this work we'll combine these with our own research/notes.

I've also noted that you want to be notified when there are changes to test. At the moment we can't easily open up testing for in-progress work, but we'll make sure you know when any changes are released so that you can give feedback on those.

[elessargng]

thank you!

[elessargng]

After the latest update, the grimoire is now much easier to read with a screen reader than before. Nice job!