WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: skip link breaks back button

for

From: Cliff Tyllick
Date: Mar 18, 2014 3:11PM

You know what would be a great service to the community? A set of pages with the basics of:
* How to tell it's a bug (which, for the sake of this discussion, we'll say is "an issue to be brought to the attention of the responsible party").
* How to isolate the bug (browser? OS? AT? Javascript? HTML spec?).
* Where to report each type of bug—for example, is there a specific site to file TalkBack bugs? Or do I use the Android issue queue? And where is the Android issue queue—if that's what it's called.
* Tips for searching issue queues to be sure you have found a new, unreported bug.
If nothing else, a page that just points to each respective page where users can report a bug would be a big help. I have several project teams that would be using it now.

Cliff Tyllick
Corporate Accessibility Technology Office
AT&T



On Tuesday, March 18, 2014 3:09 PM, Jim Allan < <EMAIL REMOVED> > wrote:

complain to the browsers, file bugs


On Mon, Mar 17, 2014 at 11:08 AM, Jared Smith < <EMAIL REMOVED> > wrote:

> On Mon, Mar 17, 2014 at 9:48 AM, Cameron Cundiff wrote:
> > Skip links have been fixed in Chrome's rendering engine:
> >
> > https://code.google.com/p/chromium/issues/detail?id7721
>
> This only fixes the in-page link issue for screen reader users. Screen
> readers set keyboard focus to elements that are scrolled to (they
> wouldn't need to do this if the browser itself set focus). This does
> not resolve the issues for sighted keyboard users, thus the continued
> need for the scripting 'hacks'.
>
> Jared
> > > >



--
Jim Allan, Accessibility Coordinator & Webmaster
Texas School for the Blind and Visually Impaired
1100 W. 45th St., Austin, Texas 78756
voice 512.206.9315    fax: 512.206.9264  http://www.tsbvi.edu/
"We shape our tools and thereafter our tools shape us." McLuhan, 1964