WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: link only saying "click here"

for

From: Birkir R. Gunnarsson
Date: Nov 19, 2014 1:18PM

Andrew

This is an unfortunate development though.
Any assistive technology application can choose to announce
programmatic context, either upon user request or in response to a
user verbosity setting.
Just because Jaws is the only screen reader that has bothered to
support preceeding heading as a programatic context, should not force
the group to essentially remove it as a useful technique.
This is, in my view, a much clearer programmatic context than being
contained in same paragraph or sentence, for instance, and on par with
using row / or column headers in a table to provide programmatic
context.
That being said, I don't want to steer this discussion way off course,
and I am sure there were similar discussions on-going when that
particular decision was made.
I am just a little surprised at the rationale.
I try first to bug the assistive technology vendors until they give
up, give in, and implement the durn feature I want .. granted it does
not always work. ;)
Thumbs up for NVDA for being open and responsive to any issues being filed.
-Birkir


On 11/19/14, Andrew Kirkpatrick < <EMAIL REMOVED> > wrote:
> Birkir,
> The Group made the decision to move the technique H80 to be advisory as a
> result of support among assistive technologies being limited to JAWS. If a
> developer were to define what they need to rely on for accessibility support
> to be limited to JAWS then they might still make use of H80 in complying
> with WCAG.
> AWK
>
>