WebAIM - Web Accessibility In Mind

E-mail List Archives

Thread: Unrecognizable Links by VO

for

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

From: JP Jamous
Date: Wed, Dec 14 2016 10:36AM
Subject: Unrecognizable Links by VO
No previous message | Next message →

Does anyone know why VO on iOS 10.1.1 recognizes most links but it does not
recognize some? Here is a page I am evaluating and if you hit the "Menu", it
is a properly composed link. However, VO on the iPhone reads it as static
text.



https://m.virtuwell.com



I am wondering if it has something to do with the styling of the link?

From: Moore,Michael (Accessibility) (HHSC)
Date: Wed, Dec 14 2016 10:50AM
Subject: Re: Unrecognizable Links by VO
← Previous message | Next message →

Probably because it is missing the href attribute so it is not a link.

Mike Moore
Accessibility Coordinator
Texas Health and Human Services Commission
Civil Rights Office
(512) 438-3431 (Office)

From: Birkir R. Gunnarsson
Date: Wed, Dec 14 2016 10:51AM
Subject: Re: Unrecognizable Links by VO
← Previous message | Next message →

It looks like there is no "href" attribute on the anchor element. the
<a> tag has to have an href to be keybord accessible and to be a link,
<a> element without one is what is called a "neutered link" and is not
really a link (should not be mapped as link in the Accessibility API).
Adding an href to this should fix the problem (better yet, use a
<button> because this widget should be a button and I think it is
styled like a button.




On 12/14/16, JP Jamous < = EMAIL ADDRESS REMOVED = > wrote:
> Does anyone know why VO on iOS 10.1.1 recognizes most links but it does not
> recognize some? Here is a page I am evaluating and if you hit the "Menu", it
> is a properly composed link. However, VO on the iPhone reads it as static
> text.
>
>
>
> https://m.virtuwell.com
>
>
>
> I am wondering if it has something to do with the styling of the link?
>
> > > > >


--
Work hard. Have fun. Make history.

From: Birkir R. Gunnarsson
Date: Wed, Dec 14 2016 10:51AM
Subject: Re: Unrecognizable Links by VO
← Previous message | Next message →

On 12/14/16, Birkir R. Gunnarsson < = EMAIL ADDRESS REMOVED = > wrote:
> It looks like there is no "href" attribute on the anchor element. the
> <a> tag has to have an href to be keybord accessible and to be a link,
> <a> element without one is what is called a "neutered link" and is not
> really a link (should not be mapped as link in the Accessibility API).
> Adding an href to this should fix the problem (better yet, use a
> <button> because this widget should be a button and I think it is
> styled like a button.
>
>
>
>
> On 12/14/16, JP Jamous < = EMAIL ADDRESS REMOVED = > wrote:
>> Does anyone know why VO on iOS 10.1.1 recognizes most links but it does
>> not
>> recognize some? Here is a page I am evaluating and if you hit the "Menu",
>> it
>> is a properly composed link. However, VO on the iPhone reads it as static
>> text.
>>
>>
>>
>> https://m.virtuwell.com
>>
>>
>>
>> I am wondering if it has something to do with the styling of the link?
>>
>> >> >> >> >>
>
>
> --
> Work hard. Have fun. Make history.
>


--
Work hard. Have fun. Make history.

From: JP Jamous
Date: Wed, Dec 14 2016 10:56AM
Subject: Re: Unrecognizable Links by VO
← Previous message | Next message →

Thank you Birkir. I just looked at the DOM and noticed that it does not have a href. It makes lots of sense now.

From: Birkir R. Gunnarsson
Date: Wed, Dec 14 2016 11:03AM
Subject: Re: Unrecognizable Links by VO
← Previous message | Next message →

I am glad I made a lot of sense today. Don't count on it being a trend. *grin*

On 12/14/16, JP Jamous < = EMAIL ADDRESS REMOVED = > wrote:
> Thank you Birkir. I just looked at the DOM and noticed that it does not have
> a href. It makes lots of sense now.
>
>

From: JP Jamous
Date: Wed, Dec 14 2016 11:06AM
Subject: Re: Unrecognizable Links by VO
← Previous message | No next message

Thank you for the heads up. LOL