WebAIM - Web Accessibility In Mind

E-mail List Archives

Thread: link only saying "click here"

for

Number of posts in this thread: 7 (In chronological order)

From: Birkir R. Gunnarsson
Date: Wed, Nov 19 2014 12:28PM
Subject: link only saying "click here"
No previous message | Next message →

Hi

I thought a recent decision meant that preceeding heading was not
considered programatically determinable context.
I am not saying it shouldn't be, just that I heard a WCAG group made
this decision.
Thanks
-Birkir

On 11/18/14, Andrew Kirkpatrick < = EMAIL ADDRESS REMOVED = > wrote:
> Susan,
> Depends on the context of the link. Check out
> http://www.w3.org/TR/2014/NOTE-WCAG20-TECHS-20140916/F63 for more examples.
> AWK
>
>

From: Andrew Kirkpatrick
Date: Wed, Nov 19 2014 12:35PM
Subject: Re: link only saying "click here"
← Previous message | Next message →

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

From: Birkir R. Gunnarsson
Date: Wed, Nov 19 2014 1:18PM
Subject: Re: link only saying "click here"
← Previous message | Next message →

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 ADDRESS 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
>
>

From: Don Mauck
Date: Wed, Nov 19 2014 1:22PM
Subject: Re: link only saying "click here"
← Previous message | Next message →

I strongly agree. The rational of this makes no sense to me at all!

From: Andrew Kirkpatrick
Date: Wed, Nov 19 2014 2:29PM
Subject: Re: link only saying "click here"
← Previous message | Next message →

Birkir and Don,
If you don't agree with changes (or anything else) in the WCAG documents I encourage you to submit public comments.
AWK

From: Birkir R. Gunnarsson
Date: Wed, Nov 19 2014 2:37PM
Subject: Re: link only saying "click here"
← Previous message | Next message →

I certainly will do that. :)
The more people who contribute, the better the end product.


On 11/19/14, Andrew Kirkpatrick < = EMAIL ADDRESS REMOVED = > wrote:
> Birkir and Don,
> If you don't agree with changes (or anything else) in the WCAG documents I
> encourage you to submit public comments.
> AWK
>
>

From: Stanzel, Susan - FSA, Kansas City, MO
Date: Fri, Nov 21 2014 10:24AM
Subject: Re: link only saying "click here"
← Previous message | No next message

Hi WebAIM,

I have a similar situation. There is general help near the top of each page and then there is specific help lower on the page. It happens on each page I am testing. Now that I understand this would I be correct in letting this go? I would rather the first link say something like "General HELP" instead of both saying "H#P".

Susie