Navigate to aria-details target and return to initial location

Question

Navigate to aria-details target and return to initial location

GeorgeKerscher opened this issue 2 years ago · 7 comments

We are delighted with how NVDA announces "has details" on an image that contains the "aria-details" attribute. We also love that using the NVDA key +D that the element contents is read.

However, we would like to see two new features added:

Move focus to the target of aria-details (perhaps NVDA key + alt + D)
and
Move focus back to the image containing the aria-details (perhaps NVDA key + shift + alt +d)

In the DAISY Consortium, we are developing best practices for publishers and authors for providing extended (long) descriptions. The best practices use the HTML details element that follows the image, or a link to another file that contains the extended description. In both options, the user would need to move to the details or the link and activate it. Having a keystroke to put focus on the details or the link is ideal. NVDA key + alt + D seems like a logical option.

Our best practices recommend that the details or the link immediately follows the image, and if the link is followed, a back link to the exact location must be provided. This makes it certain that the user will not get lost.

However it is probable that authors in the wild will place the extended (long) description almost anywhere. In these cases, the user would want to return to the image and hence the need for a way to return to the original image. NVDA key + shift + alt +D seems like a logical place for this.

We have our best practice recommendations that include examples that can be used for this testing feature. This can be found at:
Best Practices for Authoring Extended Descriptions

Answer 1 · 2022-07-24T06:29:08.000Z

Hi George, here Noelia:
Seems that the issue template headings are not present here. Hope this is not closed for this formal requirement. Anyway we can open a new issue if required using the template.
After private conversations about this, I created a plugin that I'll convert to a packaged add-on today. George won't provide support about code, that was created by me, but I will add him ass first author for his idea and tests of the various versions of my plugin. It contains two commands with the mentioned features.
I'll provide a link to the add-on here, will send to the mailing list and to addonFiles repo for wide testing and review, and so that it can be used while this is not included in NVDA, and, if needed, after discussing implementation details, I may create a pull request agains NVDA's repo.
Thanks

Answer 2 · 2022-07-24T13:43:04.000Z

Thank you. I did not find specific headings required for a feature request. If it gets closed because I messed up with formatting, we can open a new one.

Answer 3 · 2022-07-24T13:56:16.000Z

Not sure. Headings are in markdown with hastag symbols, and we hae to place the cursor under each of them to provide requested info.
I've sent the add-on to the international add-ons mailing list. In case someone wants to provide feedback, it maybe followed at:

https://nvda-addons.groups.io/g/nvda-addons/message/19336

The add-on, version 1.0-dev for testing, can be downloaded from:

https://github.com/nvdaes/enhancedAnnotations/releases/download/1.0-dev/enhancedAnnotations-1.0-dev.nvda-addon

Answer 4 · 2022-07-24T14:16:26.000Z

Hi, this usually happens if you open a default issue template (https://github.com/account /repo/issues/new). You’ll see headings if you use either the bug report or feature request template. Thanks.

Answer 5 · 2022-07-24T15:23:53.000Z

If this was closed, I think we may request to disable blank issues.
I'd wait during some days for a response. It's soon now, imo.

Answer 6 · 2022-07-24T19:44:15.000Z

May we limit the number of key presses? E.g. using double press of NVDA+D to move the focus to the target of aria-details? And using again NVDA+D double press to turn back to the image that has aria-details?
Note: this is only valid if the specification does not allows situations where such descriptions can be nested/chained.

Answer 7 · 2022-07-24T20:42:56.000Z

Hi Cyrille: but this may be problematic for people with physical disabilities, and a way to assign a keystroke at least to move to the first object identified with aria-details, and another one to come back, maybe ideal. I think that, if several keypresses are used in NVDA, we may need to keep the add-on published for those cases. Enviado desde mi iPhone

…

El 24 jul 2022, a las 21:44, Cyrille Bougot ***@***.***> escribió: May we limit the number of key presses? E.g. using double press of NVDA+D to move the focus to the target of aria-details? And using again NVDA+D double press to turn back to the image that has aria-details? Note: this is only valid if the specification does not allows situations where such descriptions can be nested/chained. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.