RE: [en] ARIA Authoring Practices Guide

Hi Valorie,

 

Thank you for your feedback. I'm glad to hear at least part of you is
thrilled with the new APG. Launch of the new design is just one more step in
our long journey toward an APG that better serves the needs of people
working on developing a more accessible web. Like any launch, it hasn't been
without oversights and compromises, including those you mentioned.

 

You wrote:

 

>While aria-label is used to on the Learn More buttons, it is not a
mechanism that helps people who use screen readers for cognitive support.
Primarily because the aria-label does not contain the visible text. 

> ...

>Two links adjacent on the page "View Patterns" and" Learn More" go to the
same place and are labelled differently.

 

These problems are noted in issue 2328:

https://github.com/w3c/aria-practices/issues/2328

 

The fix is in progress and should be in production by June 24.

 

You wrote:

 

>User experience - I now have to scroll through a long page of "cards" to
find the pattern I need with a lot of eye shifting left to right.

> ...

>Consider adding a list view in the future.

 

We have this issue open:

https://github.com/w3c/wai-aria-practices/issues/29

 

We are planning a usability study for later in the year and will consider
this issue along with other feedback as we make adjustments to the design.

 

I hope the work to address these issues lessens your sadness some.

 

Best,

Matt King

 

From: Valorie J Sundby <Valorie.J.Sundby@kp.org> 
Sent: Thursday, June 16, 2022 8:02 AM
To: public-aria-practices@w3.org
Subject: [en] ARIA Authoring Practices Guide

 

Part of me is thrilled with the new APG, another part of me is saddened to
see accessibility issues right away on the page. 

 

https://www.w3.org/WAI/ARIA/apg/ has failures:

*	F84: Failure of Success Criterion 2.4.9 due to using a non-specific
link such as "click here" or "more" without a mechanism to change the link
text to specific text. While aria-label is used to on the Learn More
buttons, it is not a mechanism that helps people who use screen readers for
cognitive support. Primarily because the aria-label does not contain the
visible text. Example: <a href="practices/landmark-regions/"
aria-label="View landmarks guide" class="button-link">Learn More</a>
*	F31: Failure of Success Criterion 3.2.4 due to using two different
labels for the same function on different Web pages within a set of Web
pages. Two links adjacent on the page "View Patterns" and" Learn More" go to
the same place and are labelled differently.  Again, the aria-label would be
confusing to those who use screen readers for cognitive support

 

User experience - I now have to scroll through a long page of "cards" to
find the pattern I need with a lot of eye shifting left to right. The simple
list was much easier to navigate for the seasoned accessibility
professional. Consider adding a list view in the future.

 

 

PTO alert: 

July 1-July 16.

 

Regards,

 

Valorie Sundby, CPWA, ADS (she/her)

Principal Accessibility Consultant 

Experience Design, Content & Accessibility

KP Digital

 

Kaiser Permanente Information Technology

(520) 269-9252

valorie.j.sundby@kp.org <mailto:valorie.j.sundby@kp.org> 

 

Need Help? Complete the
<https://jira-aes.kp.org/servicedesk/customer/portal/13/create/595>
Accessibility Intake Form

 

Accessibility is a journey, not a destination

 

 

NOTICE TO RECIPIENT:  If you are not the intended recipient of this e-mail,
you are prohibited from sharing, copying, or otherwise using or disclosing
its contents.  If you have received this e-mail in error, please notify the
sender immediately by reply e-mail and permanently delete this e-mail and
any attachments without reading, forwarding or saving them. v.173.295  Thank
you.