Accordion Example: Restructure to remove dl element
#815
Comments
mcking65
added
enhancement
|
‘if the author does not want the panels to be landmark regions, that the section elements should be replaced with div elements.’. As the region is only announced, or displayed in the Regions dialog, when the accordion section is expanded—what accessibility issues would this cause? If negligible would it need the div option? |
|
I'm not clear on the use of section and how this relates to the ARIA Accordion design pattern. As far as I understand we are not, and should not be, saying that within the APG that authors have to use specific HTML elements to achieve proper ARIA usage, because it's impossible to predict how authors will have to implement ARIA in all cases. For example, what if an author has to create an accordion that does not use section elements and they cannot. How will this pattern show the proper syntax of ARIA usage to make this accessible? The role=region aspect is important in this latter case, and also when dealing with nested accordions. Omiting the use of regions in such cases makes it impossible to reliably identify proper nesting structures and associated boundaries. |
|
In case it helps I set up an accordion with different design patterns. https://www.a11ycats.com.au/aria-testing/ Update: The div section in this is not constructed as I wanted. I'll update and post when completed. sorry about that. |
…ve focus styling To resolve issue #815: 1. Replace `dl` with `div` 2. Replace `dt` with `h3` 3. Replace `dd` with `div` 4. Update documentation tables. Also: 1. Improve visual focus styling so it is more apparent that arrow keys move focus from header to header. 2. Add accessibility features section that describes the focus styling.
Accordion Example: Restructure to use `div` instead of `dl` and improve focus styling To resolve issue #815: 1. Replace `dl` with `div` 2. Replace `dt` with `h3` 3. Replace `dd` with `div` 4. Update documentation tables. Also: 1. Improve visual focus styling so it is more apparent that arrow keys move focus from header to header. 2. Add accessibility features section that describes the focus styling.
…ve focus styling To resolve issue w3c#815: 1. Replace `dl` with `div` 2. Replace `dt` with `h3` 3. Replace `dd` with `div` 4. Update documentation tables. Also: 1. Improve visual focus styling so it is more apparent that arrow keys move focus from header to header. 2. Add accessibility features section that describes the focus styling.
…ve focus styling To resolve issue w3c#815: 1. Replace `dl` with `div` 2. Replace `dt` with `h3` 3. Replace `dd` with `div` 4. Update documentation tables. Also: 1. Improve visual focus styling so it is more apparent that arrow keys move focus from header to header. 2. Add accessibility features section that describes the focus styling.
For issue #815, remove the exclusions in the VNU configuration that permitted accordion-related roles on `dl`, `dt`, and `dt`.
github-project-automation
bot
moved this to Complete
in Accordion Patterns and Examples Development Project
As discussed in w3c/html-aria#110, due to a recent change, the ARIA in HTML spec does not currently allow role presentation on
dl, heading ondt, or region ondd. As a result, the accordion example does not validate.While the APG TF would like to see the ARIA in HTML spec changed to allow retrofitting of existing content, it does agree that an accordion can be made using less ARIA markup with a different set of HTML elements and that doing so would better illustrate appropriate use of ARIA. This issue calls for the accordion example to be changed to use a
divfor the container, heading elements for the headings, andsectionelements for the panels. This will also mean that a note should be added to state that if the author does not want the panels to be landmark regions, that the section elements should be replaced with div elements.To-do
The text was updated successfully, but these errors were encountered: