- From: Bristow, Alan <Alan.Bristow@elections.ca>
- Date: Tue, 7 May 2024 12:58:50 +0000
- To: bryan rasmussen <rasmussen.bryan@gmail.com>, WAI IG <w3c-wai-ig@w3.org>
Received on Tuesday, 7 May 2024 12:58:58 UTC
Yes, in some scenarios, this puts it far better than I can: https://www.scottohara.me/blog/2019/01/12/lists-and-safari.html#a-fix-for-the-fix Regards, Alan . . . . - . . - - - Alan Bristow ( he / him / il ) Web Developer / Développeur Web Elections Canada / Élections Canada alan.bristow@elections.ca<mailto:alan.bristow@elections.ca> ________________________________ From: bryan rasmussen <rasmussen.bryan@gmail.com> Sent: 07 May 2024 08:49 To: WAI IG <w3c-wai-ig@w3.org> Subject: is there any accessibility downside to having role="list" on an ul element? Ce message a été envoyé par un expéditeur externe. Veuillez faire preuve de prudence et ne pas cliquer sur les liens ou ouvrir les pièces jointes à moins de reconnaître l'expéditeur et de savoir que le contenu est sûr. This message was sent from an external sender. Please exercise caution and do not click links or open attachments unless you recognize the sender and know the content is safe. A design component library we are using is putting role="list" on ul elements. Aside from just being sort of stupid are there any actual accessibility problems associated with that? Thanks, Bryan Rasmussen
Received on Tuesday, 7 May 2024 12:58:58 UTC