You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would just like to point out using Definition Lists for an accordion is not really accessibility friendly (ADA/508), I would suggest moving to ULs or something else that a screenreader won't give special treatment for and confuse the user.
Right on, thanks for the resources. I'm trying to remember why I chose a definition list over unordered list (I know I debated it), but can't quite recall why. I'll look into this again.
I think you are using definition lists because they allow for two internal html elements - dt and dd. The dt works conveniently as an accordion trigger and the dd for content; all without the need for extra classes or markup. ULs, by comparison only have li tags, so you would have to complicate the markup to make it work.
Personally, I like your existing DL solution (once you allow for anchors in the dd's that is).
After having some time to look at this, you're right in your assumption as to why I used definition lists, @afingret. I'm going to stick with that for now, unless there is overwhelming support in favor of using a normal unordered list.
Would just like to point out using Definition Lists for an accordion is not really accessibility friendly (ADA/508), I would suggest moving to ULs or something else that a screenreader won't give special treatment for and confuse the user.
More Info on this issue:
http://snook.ca/archives/html_and_css/definition-lists-v-tables
http://www.w3.org/TR/WCAG20-TECHS/H40.html
The text was updated successfully, but these errors were encountered: