WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: link only saying "click here"

for

From: Birkir R. Gunnarsson
Date: Nov 19, 2014 2:37PM

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


On 11/19/14, Andrew Kirkpatrick < <EMAIL 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
>
> -----Original Message-----
> From: <EMAIL REMOVED>
> [mailto: <EMAIL REMOVED> ] On Behalf Of Don Mauck
> Sent: Wednesday, November 19, 2014 3:22 PM
> To: WebAIM Discussion List
> Subject: Re: [WebAIM] link only saying "click here"
>
> I strongly agree. The rational of this makes no sense to me at all!
>
> -----Original Message-----
> From: Birkir R. Gunnarsson [mailto: <EMAIL REMOVED> ]
> Sent: Wednesday, November 19, 2014 1:18 PM
> To: WebAIM Discussion List
> Subject: Re: [WebAIM] link only saying "click here"
>
> 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
>>
>> -----Original Message-----
>> From: <EMAIL REMOVED>
>> [mailto: <EMAIL REMOVED> ] On Behalf Of Birkir R.
>> Gunnarsson
>> Sent: Wednesday, November 19, 2014 2:28 PM
>> To: WebAIM Discussion List
>> Subject: Re: [WebAIM] link only saying "click here"
>>
>> 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 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
>>>
>>> -----Original Message-----
>>> From: <EMAIL REMOVED>
>>> [mailto: <EMAIL REMOVED> ] On Behalf Of Don Mauck
>>> Sent: Tuesday, November 18, 2014 3:09 PM
>>> To: WebAIM Discussion List
>>> Subject: Re: [WebAIM] link only saying "click here"
>>>
>>> I would think this would fall under 2.4.4.
>>>
>>> -----Original Message-----
>>> From: mark [mailto: <EMAIL REMOVED> ]
>>> Sent: Tuesday, November 18, 2014 12:35 PM
>>> To: <EMAIL REMOVED>
>>> Subject: Re: [WebAIM] link only saying "click here"
>>>
>>> Op 29-10-14 om 16:14 schreef Stanzel, Susan - FSA, Kansas City, MO:
>>>> Hi Listers,
>>>>
>>>> Here is the link for the description of this. My tester tells me
>>>> this is a tripple A requirement. I can't believe this. Is there some
>>>> other double A level requirement which could be sited?
>>>>
>>>> http://www.w3.org/TR/2014/NOTE-WCAG20-TECHS-20140916/F84
>>>>
>>>>
>>> there is SC 2.2.4 which says a link should not be ambiguous and is a
>>> level A req.
>>> Mark
>>> >>> >>> list messages to <EMAIL REMOVED>
>>> >>> >>> list messages to <EMAIL REMOVED>
>>> >>> >>> list messages to <EMAIL REMOVED>
>>>
>>
>>
>> --
>> Work hard. Have fun. Make history.
>> >> >> list messages to <EMAIL REMOVED>
>> >> >> list messages to <EMAIL REMOVED>
>>
>
>
> --
> Work hard. Have fun. Make history.
> > > messages to <EMAIL REMOVED>
> > > messages to <EMAIL REMOVED>
> > > >


--
Work hard. Have fun. Make history.