Open kevincrafts opened 3 years ago
The test was done with this page, so the elements in question here are the expand shortcodes.
@kevincrafts Is this a bug or a quirk?
I had followed instructions on how to do expandable content with appropriate aria controls, so maybe it's a quirk? We can see if there are better methods available now than when this was done 2-3 years ago.
@kevincrafts Is waiting on more information from DAO
I need to reconnect with Laura Hamrick on this for more information from their end.
From Laura Hamrick:
We’ve encountered 3 different accordions on WE sites with varying levels of accessibility.
The one I believe Kevin Darcy sent feedback on was for the accordion shortcode (example). This one I think only encounters issues with JAWS, and they are relatively minor. There may be an issue related to the “+” graphic at the start of the link text – I will defer to Mike on this one since it’s a more subtle issue.
There is another accordion type in the WE FAQ template (example) – I think Mike indicated that this was the most problematic of all 3 accordion types. The clickable question doesn’t indicate to the screen reader user that it is expandable or actionable. It also forces JAWS into “forms mode”, which Mike can expand on if you have questions about what causes that or why it’s an issue.
There’s another example on the Buff Pass FAQ page that uses a unique accordion template. This one has an issue where it moves JAWS into forms mode and then I believe the screen reader is unable to read the expanded content.
I think of the 3, the shortcode version is the most usable, and #2 is probably what we would prioritize. Again, will defer to Mike for further analysis and support.
From Kevin Darcy in the Accessibility office: