Posted by Shyamala on September 15, 2013 at 3:30am
The Current implementation of element provides a button role. Not sure if this is sufficient from the understandings at: http://accessibleculture.org/articles/2012/03/screen-readers-and-details....
As is not accessible on all browsers,To polyfill for accessibility we need to:
1) set tabindex ="0" - make it keyboard focusable
2) assign ARIA role button -> DONE!
3) aria-expanded attribute that changes based on state
4) non-summary content to be hidden by using dispaly:none when elements are collapsed
5) Any links within summary could be confusing (Not applicable in this case)
Show less
Thoughts???
Comments
Not sure
Hi Shyamala,
Thanks for reporting this. I'm not sure. I can contact Jason Kiss about this and see if he can give some feedback. He's great, and really like his blog.
I think the source issue where this was discussed was https://drupal.org/node/1168246
Let's see we get this right.
--
OpenConcept | Twitter @mgifford | Drupal Security Guide