Re: WCAG-ISSUE-20 (David): JAWS and NVDA now read the link text AND the title contents by default [HTML & ARIA Techniques TF]

Hi James

Yes, you are right. That is what is happening. So I think we can delete
that line in H33 now.
http://www.w3.org/TR/html-aapi/#a-element



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 Fri, May 23, 2014 at 10:10 AM, James Nurthen <james.nurthen@oracle.com>wrote:

> Doesn't the accessible description calculation say to use title for the
> description if it was not used in the Name calculation. Are you sure this
> is not what is happening?
>
>
>
> On May 23, 2014, at 6:20 AM, Web Content Accessibility Guidelines Working
> Group Issue Tracker <sysbot+tracker@w3.org> wrote:
>
> > WCAG-ISSUE-20 (David): JAWS and NVDA now read the link text AND the
> title contents by default [HTML & ARIA Techniques TF]
> >
> > http://www.w3.org/WAI/GL/track/issues/20
> >
> > Raised by: David MacDonald
> > On product: HTML & ARIA Techniques TF
> >
> > H33 user agent notes says "Current user agents and assistive technology
> provide no feedback to the user when links have title attribute content
> available."
> >
> > Testing with both JAWs and NVDA seem to provide title fine now in
> addition to link text, even though the accessible name calculation says it
> should be either/or... I think this line can be deleted
> >
> >
> >
> >
>
>
>
>