- From: navin gurnani <navinkumargurnani@gmail.com>
- Date: Sat, 26 Apr 2025 20:32:39 +0530
- To: w3c-wai-ig@w3.org
- Message-ID: <CAHvq6e8_FaRaMmKDaLdgWGFYTyoWy=gqwUj2V+NKKEq8QBkC-Q@mail.gmail.com>
Hi Peter, Bernat, and all, Thanks for this insightful discussion — it's been very helpful to read everyone's testing results and experiences. I completely agree with the point that *user experience and accessibility should take precedence over theoretical markup purity*, especially when browser-specific behaviors (like Safari's historical handling of list semantics) can impact real users. It’s reassuring to see that newer versions of Safari seem to have improved this behavior, but until support is consistent across environments, adding role="list" where needed remains a practical and user-first solution, even if it triggers validator warnings.. At the end of the day, *prioritizing accessibility over validation warnings* aligns with the core principle of "users over authors over implementers over specifiers." And as John mentioned, there’s precedence for using ARIA in ways that improve the experience even if it wasn't fully embraced by validators initially. Thanks again for everyone's testing and thoughtful contributions. By the way, I recently shared a post on improving accessible design practices at my organization <https://www.salesso.com> as well Best regards, Navin Gurnani
Received on Monday, 28 April 2025 05:49:47 UTC