Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
I'd have thought that an issue for this would already be here, but it doesn't seem to be the case.
Steps to reproduce:
Open the following in Firefox or Chrome:
NVDA doesn't announce anything for the button or the something section beneath it.
NVDA should somehow announce that aria-controls is set on the button, referring to the something div.
NVDA Installed/portable/running from source:
Windows 10 October update
Name and version of other software in use when reproducing the issue:
In Chrome and Firefox, there is a relationship between the button and the div. On the button, the controllerFor relation refers to the div, and on the div, the controlledBy relation refers to the button.
In JAWS, when the button is focused, JAWS allows you to press jaws+alt+m to quickly jump to the controlled element. There are several disadvantages in this implementation:
I propose two separate gestures that allow to jump to controlled or controlling elements, respectively. If the number of elements is 1, NVDA should instantly jump to the particular element. If the number of elements is more then 1, I propose showing a context menu like shown when entering a keyboard input gesture in the input gestures dialog.
@leonardder, I think your proposed UX is worthwhile.
Have you already thought on how to signal the availability of such navigation with speech and braille?
It looks like firefox only gives us the first target even though maxtargets is 0. See https://bugzilla.mozilla.org/show_bug.cgi?id=1574428
The Mozilla bug was fixed in nightly, thanks to the work by @jcsteh.
I have a prototype implementation in https://github.com/leonardder/nvda/tree/ariaControls
It currently does the following:
I just removed the blocked label, but now realised this is blocked by #10098. Announcing these relations with sound is really preferred over some obnoxious text.