E-mail List Archives
Re: Preceding headings and link context [wasWCAG 2.0: multiple buttons with the same name accessible]
From: Jason Kiss
Date: Nov 20, 2014 3:17PM
- Next message: L Snider: "Re: Google Automatic Alts?"
- Previous message: Andrew Kirkpatrick: "Re: Preceding headings and link context [wasWCAG 2.0: multiple buttons with the same name accessible]"
- Next message in Thread: Olaf Drümmer: "Re: Preceding headings and link context [wasWCAG 2.0: multiple buttons with the same name accessible]"
- Previous message in Thread: Andrew Kirkpatrick: "Re: Preceding headings and link context [wasWCAG 2.0: multiple buttons with the same name accessible]"
- View all messages in this Thread
Thanks, Andrew. I appreciate the reply, and yes, it does help. I've a
follow up question below.
On Fri, Nov 21, 2014 at 10:42 AM, Andrew Kirkpatrick < <EMAIL REMOVED> > wrote:
<snip>
> So, what does that mean? You could make an argument that by providing a custom attribute with more information for a link with poor link text that you are enabling programmatic determinability. And you'd be right that assistive technologies can get to the information, but then the question of accessibility support kicks in - the information needs to be programmatically available AND there needs to be user agent support so people can actually use what you create. In the case of the prior heading there is some assistive technology support, and since the providers are determining what browsers and AT are part of their conformance claims, it is possible that a provider might say "you need to use IE or FF with JAWS" as part of that claim.
Agreed, but given that all screen readers (at least as far as I'm
aware) enable quick access to a link's preceding heading (albeit
simultaneously moving focus to that heading), wouldn't we consider the
relationship between the link and that heading both programmatically
determinable AND effectively fully accessibility supported by screen
readers?
Thanks,
Jason
>
> What the techniques do for authors is provide a set of ways that they can meet the success criteria. There are many techniques that the group hasn't published, so the techniques don't describe the only way to meet the success criteria, but what they do provide is a way to meet a given SC in a way that allows the author to say "the WCAG group indicates that in their opinion this works". If an author wants to do something that the group hasn't published as a technique, or that the group feels is less than ideal, he still can but will need to provide more of the information that provides backing to the idea that the technique used meets the success criteria.
>
> Does this help?
> AWK
>
>
- Next message: L Snider: "Re: Google Automatic Alts?"
- Previous message: Andrew Kirkpatrick: "Re: Preceding headings and link context [wasWCAG 2.0: multiple buttons with the same name accessible]"
- Next message in Thread: Olaf Drümmer: "Re: Preceding headings and link context [wasWCAG 2.0: multiple buttons with the same name accessible]"
- Previous message in Thread: Andrew Kirkpatrick: "Re: Preceding headings and link context [wasWCAG 2.0: multiple buttons with the same name accessible]"
- View all messages in this Thread