WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: HTML Rendering in IE

for

From: _mallory
Date: Sep 16, 2016 9:34AM

That has bugged me since forever as well, esp since NVDA users will
sometimes flag a multiline link as "redundant links". However I
don't think NVDA considered it a bug, but instead mentioned a different
navigation technique was preferred in these cases. Long enough ago that
I have no idea which.

_mallory

On Tue, Sep 13, 2016 at 10:38:58AM -0400, Birkir R. Gunnarsson wrote:
> NVDA shouldn't do that, because a span is an inline element. If these
> were divs or another blocklevel element, then there is a rationale for
> the screen reader to announce them as separate elements.
> Designers may need to style part of the link text differently, and
> that can help other users, such as people with cognitive impairments,
> which is why I think that while we may not like it for screen reader
> purposes, we can't really discourage it, not unless it is broken into
> spans for no reason.
>
>
>
> On 9/13/16, Jamous, JP < <EMAIL REMOVED> > wrote:
> > Personally, I don't like this multiple spans inside a link. Here is the read
> > deal.
> > http://www.bestbuy.com/site/apple-apple-tv-64gb-black/4907025.p?skuIdI07025
> >
> > Load the page in IE and navigate to H1. From there down-arrow and you will
> > eventually hit the link.
> >
> > NVDA breaks the 2 span elements as separate ones whether in IE or Firefox.
> > What is worse is it calls both Link, because they are inside the anchor
> > element.
> >
> >
> >
> >
> > **************************************************
> >
> > Jean-Pierre Jamous
> > Digital Accessibility Specialist & Developer
> > UI Accessibility Team
> >
> > SME for EBN Include
> > Digital Accessibility Specialist & Blind and Visually Impaired Expert
> >
> > The only limitations in life are those we set for ourselves
> >
> > **************************************************
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >