WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Accessibility :: Issues with <br>, Issues with Chrome, Is it Skipping

for

From: Jared Smith
Date: Aug 26, 2013 7:49AM

Snahendu Bhattacharya wrote:

> 1. In my application, Table <caption> are not read out by JAWS while
> testing in Chrome. Is that a expected behavior?

Screen reader support in Chrome is quite limited. Many things will not
work as expected.

> 2. While testing an iPad application we have found "Skip to main content"
> is not working on several occasion, though we have followed the standard
> mentioned by WCAG or WebAIM. Surprisingly while we opened WebAIM site in
> Tablet, all the instances of "skip to main content" didn't work as
> expected. Is this a expected behavior?

What is your anticipated behavior? A "skip" link is primarily intended
for keyboard users. Are you using a keyboard with your iPad? The skip
links on the WebAIM site do provide some utility for touch users with
VoiceOver. For example, you can navigate to the skip link, activate
it, and then begin navigating via rover actions directly at the main
content. In other words, it seems to be working as intended for me.

> 3. We have used <br> tag in table column header for split the text in a
> specific format. While reading with VO in iPad, it takes more than one
> swipe to read the entire column header. Is it to be considered as potential
> Accessibility bug?

If you're reading line by line, then yes, it would naturally take two
swipes to read two lines of header text.

Jared