- From: Juliette McShane Alexandria <mcshanejuliette@gmail.com>
- Date: Fri, 18 Aug 2023 12:58:30 -0700
- To: "Shivaji Kumar" <kumar140ster@gmail.com>, "" <w3c-wai-ig@w3.org>
- Message-ID: <Mailbird-36b2295f-5817-4fed-83e4-429dbce79cda@gmail.com>
Hi Shiva, I'm just going to dump some resources and say "it depends on what you mean by accessible. There are known issues, but the details/summary can be appropriate to use in some cases." https://www.scottohara.me/blog/2022/09/12/details-summary.html https://adrianroselli.com/2019/04/details-summary-are-not-insert-control-here.html https://cloudfour.com/thinks/a-details-element-as-a-burger-menu-is-not-accessible/ https://adrianroselli.com/2023/08/progressively-enhanced-html-accordion.html Best, Juliette On 8/18/2023 12:41:58 PM, Shivaji Kumar <kumar140ster@gmail.com> wrote: Dear listers, Is there any documentation on whether HTML "details" element is accessible? If possible, it would be great if you could also point to any testing done with screen reader and browser combination. For the context, my dev team is considering replacing our existing "accordion" element with "details", and is not sure if the "details" element meets different WCAG success criteria. Any thoughts/hints would be much appreciated Shivaji -- Check out my recent accessibility publication https://nfb.org/images/nfb/publications/jbir/jbir21/jbir110204.html JAWS® Certified Trainer, 2018 Twitter handle https://twitter.com/ShivKumar140 My Blog https://digitalaccess365.wordpress.com/ Linkedin www.linkedin.com/pub/shivaji-kumar/35/a73/11a/en
Received on Friday, 18 August 2023 19:58:58 UTC