- From: Bob <rmartinengo@gmail.com>
- Date: Mon, 8 Mar 2021 10:31:01 -0800
- To: public-agwg-comments@w3.org
- Message-ID: <CADgUSK3QjCUu9i9xk9h=NE=LJ3ip6AnDnG8m=Lw8pgsmQNpqMw@mail.gmail.com>
Sorry these comments are late - I wanted to see what other folks posted. My gut feeling is the main issues with v3 are inherent to the 'accessibility guidelines' model and can't be fixed within those confines. After reading the thoughtful responses, I am even more convinced of this. This comment (posted by Claire Grupe) sums up the problem: "The guidelines specifically note that WCAG 3.0 is designed to improve the usability of the web for those with certain disabilities and limitations. We recommend emphasizing in the literature that good overall usability guidelines are not covered in WCAG; that the inherent usability or conceptual model for a process or workflow is covered in usability for all users, and WCAG's guidance ensures that this overall usability is extendable to all audiences.* As it is currently written, it is unclear that overall usability is considered a minimum baseline requirement*, and may be potentially confusing." This is the Catch-22 of defining accessibility in terms of disability access rather than overall usability, and this is what I address in my paper. Thanks for your time, Robert G. Martinengo
Attachments
- application/pdf attachment: WCAG_comments_rmartinengo.pdf
Received on Monday, 8 March 2021 18:31:24 UTC