W3C home > Mailing lists > Public > public-agwg-comments@w3.org > February 2021

Comments WCAG3.0 Editor's Draft

From: Talyah Aviran <talyah@uxaccess.com>
Date: Sun, 31 Jan 2021 18:24:06 +0200
Message-ID: <CADfc=nftiJNa1GKi3ABK2tJysYrQnr6DReSb5yEmF7dOYyX7Kw@mail.gmail.com>
To: public-agwg-comments@w3.org
Hi Silver Team,
My name is Talyah Aviran. I have been an advocate and an active
professional  of web and digital accessibility content for the last 13
years. Since I am also a certified usability analyst, I believe that
digital accessibility starts from the design phase of a product.

I went through the W3C Editor's Draft 20 January 2021 of WCAG 3.0 and I
have a few remarks.
You did a remarkable job there. I really like the direction of the new
approach to the guidelines.
*How Tos* - In recent months I have been working with large companies to
assist them in embedding digital accessibility practices into their product
lifecycle. Product teams sometimes have no accessibility knowledge at all
to be able to start implementing the guidelines. They basically have no
clue and must learn how to include accessibility in their procedures from
this day forward and to start thinking "inclusive" or "accessible".
This is where consultants come in and try to educate, teach, direct,
document and lead the teams to web accessibility independence.
The new set of guidelines can really help by defining the role of each team
in the product life cycle: Product Managers, UX, Development and QA.
Looking at the new guideline structure, I expected to find these roles in
the How Tos. I expected to find the product manager role in the Plan tab,
the UX role in the Design tab and the development role in the Develop tab.
I am not saying that the current content of the tabs is confusing but if
the content could be role centered, it would assist product teams to
understand their role in the grand scheme of things. Adding a QA tab for
the QA team would have been perfect. The QA tab can direct the readers to
the Outcome pages that detail the methods.
*Outcome - Functional categories* - The list of functional categories is
good but it would be better to link each functional category to resources
that will describe the impact of this guideline on the category. For
example, link each cognitive category to the relevant location in the COGA
working draft.

Thank you,

*Talyah Aviran*

Certified Professional in Web Accessibility (CPWA)

Certified Usability Analyst (HFI CUA)

*eMail:* t <talyaav@gmail.com>alyah@uxaccess.com

*Website: *https://uxaccess.com

*US:* +1 470.809.9455

*IL:* +972 55 8852121

*Profile: *My LinkedIn Profile <http://www.linkedin.com/in/talyahaviran>
Received on Monday, 1 February 2021 16:19:38 UTC

This archive was generated by hypermail 2.4.0 : Monday, 1 February 2021 16:19:39 UTC