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 10:21AM

On Mon, Aug 26, 2013 at 9:41 AM, Snahendu Bhattacharya
< <EMAIL REMOVED> > wrote:

> Question 1. (Table caption in Chrome) Do we consider this as a potential
> bug?

Yes, it is a bug in Chrome.

> This works fine with JAWS/IE. if yes, what can be possible solution
> for this?

Don't use Chrome. There is such poor support for JAWS in Chrome that
it could hardly be considered a viable option for end users or for
testing.

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

This is a VoiceOver issue. Again, there's nothing you can do to fix
this (except perhaps log a bug with Apple).

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

As above, there's nothing you can do to fix the screen reader quirks.
Nor should you try to. This certainly would not be a compliance
failure on your part.

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

First of all, follow the guidelines. If you do things correctly,
there's a reasonable expectation that screen readers should support
your implementation of standards. When they fall short, it is
sometimes necessary to come up with workaround when the impact is
severe, but most of the time there's little you could or should do to
address screen reader bugs and quirks. In the cases you cite, the
impact of these bugs is relatively minor.

Jared