Re: Accessibility of Details Element

Thanks George. I’m still unclear as to how screenreaders — let’s take VoiceOver as an example — convey the information in aria-details to the user. For example, as a test, I added aria-details (pointing to the id of a details element) to a form field. But when I enter the form field, nothing from aria-details is announced. Am I doing this incorrectly? (aria-described by works fine here, by the way). Although I am testing VO in Safari, I do see that the aria-details info is listed in the Chrome dev tools accessibility tab, so the browser recognizes it.

Thanks, Peter



> On Aug 20, 2023, at 4:46 PM, George Kerscher <kerscher@montana.com> wrote:
> 
> Hi,
> 
> It works the same with websites or in EPUB; EPUB is a zip file of XHTML.
> 
> Some people will put extended descriptions at the end of the chapter. When the extended description is just below the image, the usefulness of the NVDA add-on is not that important, but when the details is far away, this functionality is great.
> 
> Best
> George
> 
> 
> -----Original Message-----
> From: Peter Weil <peter.weil@wisc.edu> 
> Sent: Sunday, August 20, 2023 2:41 PM
> To: George Kerscher <kerscher@montana.com>
> Cc: Pyatt, Elizabeth J <ejp10@psu.edu>; Shivaji Kumar <kumar140ster@gmail.com>; w3c-wai-ig <w3c-wai-ig@w3.org>
> Subject: Re: Accessibility of Details Element
> 
> George,
> 
> This is very interesting, thank you.
> 
> I’ve never tried using  aria-details, given what I thought I last read about the generally poor support for it. Support must have improved dramatically not too long ago, but I haven’t seen anything about it.
> 
> The DAISY KB says:
> 
> "To remove any ambiguity, the aria-details attribute can be used to associate the details element with the relevant content item. If the information cannot be placed in logical sequence, the attribute allows users of assistive technologies to locate the element when they encounter the content it is associated with…. this works effectively with Jaws, NVDA, VoiceOver, and TalkBack”
> 
> https://kb.daisy.org/publishing/docs/html/details.html#ex

> 
> Would you please clarify exactly what “associate” means here, and exactly how — aside from the NVDA commands you cite — the attribute allows (enables? facilitates?) users to locate the element to which aria-details points? What is read out to the user?
> 
> I don’t know much about EPUB. Do the results of EPUB testing apply equally to browsers and websites?
> 
> Thanks very much,
> 
> Peter
> 
>> On Aug 19, 2023, at 10:01 AM, George Kerscher <kerscher@montana.com> wrote:
>> 
>> Hello,
>> 
>> We at DAISY have been testing the use of the HTML details element. It is currently being recommended immediately after an image that requires an extended description.
>> 
>> We also recommend using the aria-details attribute to point to the ID of the details element.
>> 
>> This works effectively with Jaws, NVDA, VoiceOver, and TalkBack. NVDA has an add-on that adds additional functionality. Here is from the Enhanced Annotation add-on documentation:
>> Commands
>> • NVDA+alt+d: moves the cursor to the element identified with aria-details.
>> • NVDA+alt+shift+d: moves the cursor to the original element, for example, an image with Further details like a long description. If NVDA+alt+d has been pressed several times to move to related annotations, it'll be possible to go back to each origin.
>> 
>> Here is a link to the test EPUB titles we use, and the test for details is in “Accessibility Tests Extended Descriptions.” You can download any of the test books from:
>> https://www.epubtest.org/test-books

>> 
>> Here is a link to the test results.
>> https://www.epubtest.org/results

>> 
>> And from the DAISY knowledge Base on the details element:
>> http://kb.daisy.org/publishing/docs/html/details.html#ex

>> 
>> Best
>> George
>> 
> 
> --
> Peter Weil
> Web Developer
> University Marketing Web Services
> Office of Strategic Communications
> University of Wisconsin–Madison
> 608-220-3089
> 
> 
> 
>

Received on Monday, 21 August 2023 12:22:35 UTC