Made a list of WCAG techniques to HTML5

Thanks Mark...

Describedby works on a link in NVDA but for some reason JAWS repeats the
heading twice in IE, and doesn't work in JAWS with Firefox... on the other
hand aria label doesn't work in NVDA, yet.

The reason I recommend aria label is that the aria label text replaces the
anchor link text in the links list dialogue box which is a real bonus for
JAWS users... now they can use their tradition list of links are identify
the right one... not so with aria describedby.  I dropped a couple of text
files after the table.
http://davidmacd.com/WCAG/wcag-html5-techniques-review.html

 We don't have an ARIA describedby example on a link in the WCAG techniques
yet.

ARIA-labelledby is also sufficient Aria7 , is that then you have to put an
id also on the anchor element itself and reference both the anchor element
and the heading... because there is concern that a blind user could not
identify the link text if someone refers to it... but it certainly
sufficient if both refernces are used... just a little confusing and
finicky for webmasters who might scratch their head at the aria

Cheers,

David MacDonald



*Can**Adapt* *Solutions Inc.*

Tel:  613.235.4902

LinkedIn <http://www.linkedin.com/in/davidmacdonald100>

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 Mon, Mar 31, 2014 at 3:48 PM, Mark Sadecki <mark@w3.org> wrote:

> Thanks for this very useful work, David.
>
> I would suggest using aria-describedby for H80 and H81, assigning an ID to
> the
> relevant Heading and parent list element.  I think this results in the most
> meaningful experience for a screen reader user.  I also think this is a
> sufficient technique for H78 as well, given you can identify the fragment
> of
> text that best describes the purpose of the link (could be the Heading, or
> the
> paragraph text in the example given.)
>
> Mark
>
> On 3/31/14, 12:10 PM, David MacDonald wrote:
> > As we approach HTML5  techniques for WCAG, I went through the existing
> > techniques. Dropped them in a table and made notes beside them. Anything
> without
> > notes I think can be an HTML5 technique by simply adding HTML5 in the
> > applicability section. I took this opportunity to do a ROT exercise
> (redundant,
> > outdated, trivial) at the same time and made notes if I thought we
> should remove
> > or amend them.
> >
> > Out of 59 techniques, 13 techniques have notes on them. so 46 are ready
> to go
> > for HTML5.
> >
> > http://davidmacd.com/WCAG/wcag-html5-techniques-review.html
> >
> >
> > Cheers,
> >
> > David MacDonald
> >
> >
> >
> > *Can**Adapt**Solutions Inc.*
> >
> > Tel:  613.235.4902
> >
> > LinkedIn <http://www.linkedin.com/in/davidmacdonald100>
> >
> > 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, Mar 25, 2014 at 12:32 PM, Andrew Kirkpatrick <akirkpat@adobe.com
> > <mailto:akirkpat@adobe.com>> wrote:
> >
> >     http://www.w3.org/2014/03/25-wai-wcag-minutes.html____
> >
> >     __ __
> >
> >     Thanks,____
> >
> >     AWK____
> >
> >     __ __
> >
> >     Andrew Kirkpatrick____
> >
> >     Group Product Manager, Accessibility____
> >
> >     Adobe Systems ____
> >
> >     __ __
> >
> >     akirkpat@adobe.com <mailto:akirkpatrick@adobe.com>____
> >
> >     http://twitter.com/awkawk____
> >
> >     http://blogs.adobe.com/accessibility____
> >
> >     __ __
> >
> >
>
>
> --
> Mark Sadecki
> Web Accessibility Engineer
> World Wide Web Consortium, Web Accessibility Initiative
> Telephone: +1.617.715.4017
> Email: mark@w3.org
> Web: http://w3.org/People/mark
>
>
>