Accessibility issues in the ChoiceScript game UI for screen reader users

General
1

Hello everyone,

I’ve been messing around with Choice Script for a toy project, and I’ve run into a few accessibility issues. For context, I’m blind, and I primarily use Windows with the free NVDA screen reader, though I also use an iPhone. All tests were performed with the latest version of Firefox.

Here are the two major issues I’ve found:

  1. For *input_text and *input_number fields, NVDA announces them as “edit.” The visual label also appears not to be present, though the variable bound to the input box is given as part of the name attribute (e.g., < input name="name"...>. there is no <label> element or aria-label attribute associated with the field. It’s worth noting that there is already code in the engine to add <label> tags to radio buttons and associate the ids correctly (with the for attribute).
  2. When pressing the Next button, NVDA starts reading newly printed text. So far, so good, this is generally how we want to announce updates to a screen reader. However, it stops reading when it encounters a *paragraph_break.

As alluded to above, I’ve looked through the engine briefly, but I don’t know nearly enough about modern JS or ChoiceScript’s internals to implement these fixes myself, but I have a solid grasp of HTML, programming, and accessibility testing and would love to help where I can.

I also have access to JAWS, Narrator, Chrome, Edge, iOS, and ChromeVox/ChromeOS for testing how stuff works with different screen readers.

Any help with these issues would be greatly appreciated, especially since you folks clearly prioritize accessibility.

11 Likes