WebAIM - Web Accessibility In Mind

E-mail List Archives

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

for

From: Snahendu Bhattacharya
Date: Aug 26, 2013 9:41AM

Hi!

Thanks for replying. I will restructure my questions for further clarity.

Question 1. (Table caption in Chrome) Do we consider this as a potential
bug? This works fine with JAWS/IE. if yes, what can be possible solution
for this?

Question 2. ("Skip to main content" with Voiceover/iPad ) "Skip to main
content" is generally intended to Keyboard user. But if we consider screen
reader (here Voiceover), user, they are not able to activate the link by
double tapping while Voiceover is on. Screen reader is not reading from the
desired location. This happens for "webaim" website as well. if we open the
website in iPad and try to activate "skip to main content", we will find
the link is not taking to desired location for all the pages. same is
happening with my application as well. This works fine with JAWS/IE. What
might be possible issue for this?

Question 3. (<br> tag with Voiceover/iPad) Do we consider this as a
potential accessibility issue? This works fine with JAWS/IE.


Generally, if something is not working in specific browser/screen reader,
do we consider those as potential issues. or if the same is working with
any screen reader, should be considered as remediation?

Thanks & Regards,
Snahendu Bhattacharya



Snahendu Bhattacharya


On 26 August 2013 19:19, Jared Smith < <EMAIL REMOVED> > wrote:

> 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
> > > >