W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > April to June 2014

Fwd: Re: [WebAIM] Google Chrome blocks accessibility for keyboard users. Your input is needed.

From: Jim Allan <jimallan@tsbvi.edu>
Date: Fri, 18 Apr 2014 10:38:00 -0500
Message-ID: <CA+=z1Wk3RobQUAtir3oBCooyCF=2orrJ2e98_DV8roSGOr-FhA@mail.gmail.com>
To: WAI-ua <w3c-wai-ua@w3.org>
Sigh,  browsers givith and browsers taketh away. Please file a bug, and
lets get back some lost functionality.
Jim
---------- Forwarded message ----------
From: "Steve Faulkner" <faulkner.steve@gmail.com>
Date: Apr 18, 2014 4:16 AM
Subject: Re: [WebAIM] Google Chrome blocks accessibility for keyboard
users. Your input is needed.
To: "WebAIM Discussion List" <webaim-forum@list.webaim.org>
Cc: "webaim-forum@list.webaim.org" <webaim-forum@list.webaim.org>

No problem, also tweeted @googleaccess
> https://twitter.com/stevefaulkner/status/457069200381849600
>
> Sent from my iPhone
>
> > On 18 Apr 2014, at 08:51, Jonathan H <digitaltoast@gmail.com> wrote:
> >
> > Hi; first posting here.
> >
> > To cut a month-long story short, it was brought to my attention by a
> > keyboard-only tester of a site I'm developing, that they cannot save
> > SOME of the files when using Google Chrome.
> >
> > After hours of testing between browsers, operating systems, trying
> > different doctypes etc, I finally ended up with this example page:
> > http://goo.gl/6oyiGc
> >
> > Forget about the fact that the links are just to pages; it makes no
> > difference, imagine they are files. Now try and download some of them
> > with the keyboard. Remember, you're saving the target, not the current
> > page.
> > "Save link as", not "save as". See the problem now?!
> >
> > Unfortunately, the developers of Google Chrome think being able to use
> > the browser if you're a keyboard user is a "feature request", removed
> > the "bug" tag and changed it to "feature request" and lowered the
> > priority.
> > Even though they agree that it used to behave correctly.
> >
> > Remember, the menu key should EXACTLY emulate a right mouse click
> > which of course blind/keyboard only users won't generally use. Any
> > difference is a problem; any difference which depends arbitrarily on
> > where in a list of words it is a bug.
> >
> > So would people mind taking a few moments to "star" this issue to give
> > it some weight, and maybe add a comment?
> > https://code.google.com/p/chromium/issues/detail?id=362147
> > You just need to be signed in with your regular Google/Gmail account.
> >
> > It's pretty much confirmed as a bug in my threads at
> >
> http://stackoverflow.com/questions/23084579/how-can-i-diff-all-attributes-and-properties-of-two-dom-elements
> > and
> https://forum.jquery.com/topic/can-i-use-jquery-to-export-compare-or-repair-a-dom-element-giving-trouble-in-one-browser
> >
> > PS - techy bit: If you're a bit handy with the Blink DOM renderer or
> > carry any weight in the accessible browser development community, your
> > input is greatly appreciated!
> >
> > Thanks again.
> > _______________________________________________
> > To manage your subscription, visit http://list.webaim.org/
> > Address list messages to webaim-forum@list.webaim.org
> _______________________________________________
> To manage your subscription, visit http://list.webaim.org/
> Address list messages to webaim-forum@list.webaim.org
>
Received on Friday, 18 April 2014 15:38:24 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:49:45 UTC