CODEWITHSUNDEEP
javascripthtmlaccessibilityusability
DADU
DADU

Reputation: 7048

HTML5 details and summary usability concern

The new HTML5 details and summary elements, are currently implemented in Chrome 12.

I find one thing that is concerning me and I would like to hear your thoughts on the matter.

When the open attribute is set, any child nodes besides the summary element, "content" of the details element are removed from the document flow.

If the element is open, the open attribute is removed when the animation is finished. Otherwise, the content will be invisible immediately while the animation is still running.

This is all fine but what about accessibility? Folks using assistive technology. They will have to wait the duration of the slide up animation before they have a confirmation that the details element is closed (because only then, the open attribute is removed)?

Upvotes: 2

Views: 777

Answers (2)

RobG
RobG

Reputation: 147393

Make your pages functional without any script at all, that will help usability a lot. Only add script where it enhances usability - things that slide up/down or fade in/out may look cool the first time, but after making users wait several times for effects to do their thing before they can access the content being revealed, it quickly becomes tiresome.

Upvotes: 0

Knu
Knu

Reputation: 15136

Why don't you set aria-expanded to false just before the closing animation?

Upvotes: 3

Related Questions