- From: Sean Murphy (seanmmur) <seanmmur@cisco.com>
- Date: Sun, 5 Feb 2017 23:48:11 +0000
- To: Adam Cooper <cooperad@bigpond.com>, "'Ajay Sharma'" <ajaysharma89003@gmail.com>
- CC: "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
Hi AJ, Some keystrokes are common to all OS and should be used by default even if the WCAG 2.0 doesn't mention them. Such as escape to cancel or close a dialog. As a screen reader user, I rarely use the shortcut keys. Only time I have ever used them is within Safari O'Reilly online books to jump between sections. Otherwise, I avoid using them. This is more of a personal choice then an accessibility requirement. The main reason why I don't use them is what Adam hinted at. Some shortcut keys conflict with using the standard browser shortcut keys available. Sean Murphy Accessibility Software engineer -----Original Message----- From: Adam Cooper [mailto:cooperad@bigpond.com] Sent: Sunday, 5 February 2017 10:54 AM To: 'Ajay Sharma' <ajaysharma89003@gmail.com> Cc: w3c-wai-ig@w3.org Subject: RE: Guidelines to implement shortcut keys Hi Ajay, Short answer: no. WCAG doesn't 'mandate' features as such. The key (no pun intended) for 2.1.1 is 'function'. That is, if closing a dialog can be achieved by activating a close control with keyboard input then this criterion is satisfied. It doesn't mandate mapping the ESC to this function. I don't believe 2.4.5 has anything to do with keyboard input. if you are planning to implement keyboard shortcuts, you may want to consider: - the intended/target user group - any potential assignment conflicts - whether there is already a user-agent provided shortcut - different cross-browser & implementation behaviours - whether the shortcut is to focus or activate something - how the shortcut is conveyed to users There are plenty of well-intentioned implementations out there which, in my view, hinder rather than help ... best to use them sparingly and with a strong use case. cheers, Adam -----Original Message----- From: Ajay Sharma [mailto:ajaysharma89003@gmail.com] Sent: Saturday, February 04, 2017 4:26 PM To: w3c-wai-ig@w3.org Subject: Guidelines to implement shortcut keys Hello and Greetings, Wanted to know whether implementation of shortcut keys for tasks such as jumping to next or previous page, closing the modal dialog by using escape key and providing quick access to the major functionality of the website or a software is mandate under any WCAG guideline? If yes, which would be the correct guideline to map such things with? Although I was not able to find any guideline that directly address this issue but a couple of SCs that is 2.1.1 keyboard and 2.4.5 multiple ways seems close. Please share your thoughts. Thanks, Ajay This email has been scanned by BullGuard antivirus protection. For more info visit www.bullguard.com
Received on Sunday, 5 February 2017 23:48:46 UTC