- From: James Nurthen <nurthen@adobe.com>
- Date: Tue, 2 Jun 2020 18:14:11 +0000
- To: "Schnabel, Stefan" <stefan.schnabel@sap.com>
- CC: ARIA Working Group <public-aria@w3.org>
- Message-ID: <MN2PR02MB699099B57A7C0E808FAD7D26A68B0@MN2PR02MB6990.namprd02.prod.outlook.com>
If there is not one already can you please create an issue and tag it with the Agenda label. Thanks, James James Nurthen (he/him) | Accessibility Engineer | Adobe | T 415 832 2734 | nurthen@adobe.com From: Schnabel, Stefan <stefan.schnabel@sap.com> Date: Tuesday, June 2, 2020 at 11:13 AM To: James Nurthen <nurthen@adobe.com> Cc: ARIA Working Group <public-aria@w3.org> Subject: RE: Function explanations for aria-keyshortcuts values Hi James, I’d prefer ARIA since the respective paragraph “Authors SHOULD provide a way to expose keyboard shortcuts so that all users may discover them, such as through the use of a tooltip.” in the spec could be enhanced to give at least two good example patterns for explanation text of aria-keyshortcuts values for all users. Browser default tooltips cannot be invoked with keyboard and are therefore a poor substitute for visual indication of keyshortcut functions or all users. Also spec does not explicitly mention for instance Save Ctrl+S menu item pattern for visible labels (with ctrl+s osibly NOT being part of the label text causing redundancy with spoken keyshortcuts attribute), nor give info if shortcut itself should be always present in aria-describedby reference texts used as tooltip replacement in cases visible tooltips make no sense (there are scenarios for that). Also, the important role of product documentation for assigned keyshortcuts is not mentioned. APG then can take this as starting point for subsequent elaboration of different examples. Regards Stefan From: James Nurthen <nurthen@adobe.com> Sent: Dienstag, 2. Juni 2020 19:43 To: Schnabel, Stefan <stefan.schnabel@sap.com> Cc: ARIA Working Group <public-aria@w3.org> Subject: Re: Function explanations for aria-keyshortcuts values Authoring Practices has an open issue on this https://github.com/w3c/aria-practices/issues/253 It is targeted for 1.2 Release 2 Are you asking for this to be on an APG agenda or an ARIA agenda? James Nurthen (he/him) | Accessibility Engineer | Adobe | T 415 832 2734 | nurthen@adobe.com<mailto:nurthen@adobe.com> From: Schnabel, Stefan <stefan.schnabel@sap.com<mailto:stefan.schnabel@sap.com>> Date: Tuesday, June 2, 2020 at 4:58 AM To: James Nurthen <nurthen@adobe.com<mailto:nurthen@adobe.com>> Cc: ARIA Working Group <public-aria@w3.org<mailto:public-aria@w3.org>> Subject: Function explanations for aria-keyshortcuts values Hi James, Can we please put a short discussion for that on agenda for one of the next meetings? Latest https://w3c.github.io/aria-practices/ contains no information about aria-keyshortcuts. Background is that it is unclear/not defined * Which means are to be used in priority to explain shortcut function for non-visible label scenarios (tooltip, hidden text, app documentation) * If tooltip and/or non-visible descriptions should, may, or may not contain shortcut values (redundancy in speech) * If ARIA spec chapter for aria-keyshortcuts could be extended by respective instructions (editorial change) Thanks + Best Regards Stefan Schnabel Usability Design Senior Expert - Accessibility IEG SAP User Experience
Received on Tuesday, 2 June 2020 18:14:26 UTC