- From: Simon Harper <simon.harper@manchester.ac.uk>
- Date: Fri, 24 Sep 2010 11:00:16 +0100
- To: "Egan, Bim" <Bim.Egan@rnib.org.uk>
- CC: UAWG list <w3c-wai-ua@w3.org>
Hi there Bim, this is really just a problem of the browser not implementing the bindings in rationale way. Indeed, a modifier key would easy sort this out. Cheers Si. ======================= Simon Harper University of Manchester (UK) More: http://simon.harper.name/about/card/ On 23/09/2010 19:04, Egan, Bim wrote: > Sorry to butt in here, but it concerns me that as accesskey bindings > frequently conflict with keyboard access to browser toolbars or > plug-ins, and can also change settings in access technology that runs in > the background while being sensitive to all keystrokes, such as screen > readers, defined accesskeys could result in all HTML5 pages using them > being inaccessible to people who navigate via keyboard or use access > tech software, instead of the current situation where it is difficult > only on some sites using code that conforms to specification. > > Bim > > -----Original Message----- > From: w3c-wai-ua-request@w3.org [mailto:w3c-wai-ua-request@w3.org] On > Behalf Of Simon Harper > Sent: 23 September 2010 18:44 > To: UAWG list > Subject: Accesskey Discussion > > I seems to me that HTML5 is becoming increasingly platform like. In this > case I suggest that HTML5 specify a number of predefined accesskeys for > common functionality including those useful for WebApps. > > Cheers > Si. > > ======================= > > Simon Harper > University of Manchester (UK) > > More: http://simon.harper.name/about/card/ > > > > To report this e-mail as Spam, please forward it to: > spam@mailcontrol.com > >
Received on Friday, 24 September 2010 10:01:29 UTC