Re: [browser-accessibility-dev] Web Application Reserved Keystrokes in JAWS

[Victor Tsaran]

What's the latest on this discussion? Everyone agrees we need a solution, right?

Sent from a Mobile device

On May 27, 2015, at 8:51 AM, 'Dominic Mazzoni' via Browser Accessibility Development <browser-acce...@googlegroups.com> wrote:

I'm happy with taking a conservative approach. I do think it'd be good to announce shortcut keys to users when they encounter a control, and now NVDA users have an option to get the same behavior as JAWS users, the only difference is that NVDA users explicitly toggle that mode. I think it will be really interesting to see what fraction of users end up liking this mode (whether in NVDA or in JAWS) and what fraction end up not using it, but maybe become more aware of accessing these shortcuts via the passthrough key thanks to Facebook's popularity.

On Tue, May 26, 2015 at 4:50 PM, James Teh <ja...@nvaccess.org> wrote:

On 27/05/2015 1:34 AM, Nektarios Paisios wrote:

Since this implementation is user activated, can the aria-key proposal
move forward?

I guess that depends on your intent for it. At this stage, I don't see this being used to automatically activate anything in NVDA. However, I certainly think it is probably worthwhile to expose the shortcut keys to users. This could even be useful for keyboard-only, non-screen reader users (though displaying these visually would probably require a browser extension).

That said, I don't think this is going to fly for keys which don't have on-screen controls. Having off-screen buttons for Next tweet, Previous tweet, etc. just so we can expose the key seems like a really ugly hack to me, especially because they only make sense when focus is within the list. In general, I think off-screen text is almost always a bad thing, with a few very rare exceptions.

Jamie

--
James Teh
Executive Director, NV Access Limited
Ph +61 7 3149 3306
www.nvaccess.org
Facebook: http://www.facebook.com/NVAccess
Twitter: @NVAccess
SIP: ja...@nvaccess.org

--
You received this message because you are subscribed to the Google Groups "Browser Accessibility Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to browser-accessibil...@googlegroups.com.
To post to this group, send email to browser-acce...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/browser-accessibility-dev/CAFz-FYww7tfjsLxWdR7NVXZAT_dffkHJ3%3DuesxG-ipvYUqwLBw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Dominic Mazzoni]

The proposal to expose keyboard shortcuts got discussed by the W3C group. It's been somewhat controversial even though we didn't even try to tackle cases like offscreen controls or web app reserved shortcuts. If you'd like to see this part of the standard I'd encourage you to get involved.

I think this would be a step in the right direction but I agree it wouldn't solve all of the underlying issues. I'd love to hear additional ideas for what we could do next.

[Nektarios Paisios]

Could you provide a link to the relevant mailing list in the W3C Group?
Nektarios.

[Dominic Mazzoni]

Here are the two threads:

https://lists.w3.org/Archives/Public/public-pfwg/2015Jun/0066.html

https://lists.w3.org/Archives/Public/public-pfwg/2015Jun/0029.html