- From: Katie Haritos-Shea GMAIL <ryladog@gmail.com>
- Date: Tue, 19 Jul 2016 10:45:44 -0400
- To: "'David MacDonald'" <david100@sympatico.ca>
- Cc: "'WCAG'" <w3c-wai-gl@w3.org>
- Message-ID: <00a201d1e1cc$3b0ada40$b1208ec0$@gmail.com>
That looks good David, but we need to take into account Gregg and Jasons’ comment concerning the additional context, maybe this is more applicable to:
* 2.4.9,
* or a new SC that is only about Using an Accessible Name for Links
* or as a technique for 2.4.4 plus context, or 2.4.9 – called Using an Accessible Name for Links
* katie *
Katie Haritos-Shea
Principal ICT Accessibility Architect (WCAG/Section 508/ADA/AODA)
Cell: 703-371-5545 | <mailto:ryladog@gmail.com> ryladog@gmail.com | Oakton, VA | <http://www.linkedin.com/in/katieharitosshea/> LinkedIn Profile | Office: 703-371-5545 | <https://twitter.com/Ryladog> @ryladog
From: David MacDonald [mailto:david100@sympatico.ca]
Sent: Tuesday, July 19, 2016 10:21 AM
To: Katie Haritos-Shea <ryladog@gmail.com>
Cc: WCAG <w3c-wai-gl@w3.org>
Subject: Re: (WCAG 2.1) Do we want to replace "programmatically determined link context" in 2.4.4 with "Accessible Name"?
How about this?
Accessible Name
:
The accessible name is the name of a user interface element. Each platform accessibility API provides the accessible name property. The value of the accessible name may be derived from a visible (e.g., the visible text in a link) or invisible (e.g., alternate text that reports to the accessible name) property of the user interface element.
Adapted from https://www.w3.org/TR/wai-aria/terms
Cheers,
David MacDonald
CanAdapt Solutions Inc.
Tel: 613.235.4902
LinkedIn <http://www.linkedin.com/in/davidmacdonald100>
twitter.com/davidmacd <http://twitter.com/davidmacd>
<https://github.com/DavidMacDonald> GitHub
www.Can-Adapt.com <http://www.can-adapt.com/>
Adapting the web to all users
Including those with disabilities
If you are not the intended recipient, please review our privacy policy <http://www.davidmacd.com/disclaimer.html>
On Tue, Jul 19, 2016 at 10:13 AM, David MacDonald <david100@sympatico.ca> wrote:
Agree
Cheers,
David MacDonald
CanAdapt Solutions Inc.
Tel: 613.235.4902 <tel:613.235.4902>
LinkedIn <http://www.linkedin.com/in/davidmacdonald100>
twitter.com/davidmacd <http://twitter.com/davidmacd>
<https://github.com/DavidMacDonald> GitHub
www.Can-Adapt.com <http://www.can-adapt.com/>
Adapting the web to all users
Including those with disabilities
If you are not the intended recipient, please review our privacy policy <http://www.davidmacd.com/disclaimer.html>
On Tue, Jul 19, 2016 at 9:27 AM, Katie Haritos-Shea <ryladog@gmail.com <mailto:ryladog@gmail.com> > wrote:
I like this idea, but, only if we have a very clear defonition of Accessible Name that makes it clear it is not limited to the ARIA usage.
Katie Haritos-Shea
703-371-5545 <tel:703-371-5545>
On Jul 19, 2016 9:14 AM, "David MacDonald" <david100@sympatico.ca <mailto:david100@sympatico.ca> > wrote:
***This is proposed for version 2.1. NOT for 2.0 ***
Do we want to consider replacing
"
programmatically determined link context" with "Accessible name" in 2.4.4.
This will simplify the requirement, eliminate that awkward definition that few developers understood, and ensure that when screen reader users pull up a list of links on on conforming page, they will not get "learn more" etc... because screen readers provide the accessible name in the links list, not just the link text. So an aria-label or aria-labelledby will render a meaningful text in the list. AccessibleName wasn't well understood or supported back in 2006-2008.
===Current===
2.4.4 Link Purpose (In Context): The purpose of each link can be determined from the link text alone or from the link text together with its
programmatically determined link context, except where the purpose of the link would be ambiguous to users in general. (Level A)
=== Proposal change===
2.4.4 Link Purpose (In Context): The purpose of each link can be determined from the link text alone or Accessible Name, except where the purpose of the link would be ambiguous to users in general. (Level A)
Cheers,
David MacDonald
CanAdapt Solutions Inc.
Tel: 613.235.4902 <tel:613.235.4902>
LinkedIn <http://www.linkedin.com/in/davidmacdonald100>
twitter.com/davidmacd <http://twitter.com/davidmacd>
<https://github.com/DavidMacDonald> GitHub
www.Can-Adapt.com <http://www.can-adapt.com/>
Adapting the web to all users
Including those with disabilities
If you are not the intended recipient, please review our privacy policy <http://www.davidmacd.com/disclaimer.html>
Received on Tuesday, 19 July 2016 14:46:16 UTC