Re: Response to Issue 659/660/386

It wasn't the reason for including the focus aspect (the reason for that 
was things like select lists) - but I accept that this is covered by that.

On 1/5/2018 9:18 AM, Alastair Campbell wrote:
> > So if I don't use a form element but use a JS keyboard event handler to 
> perform **exactly* *the same functionality my content would fail - but 
> if I use a form element it would pass? The effect on the end user is 
> exactly the same. I can't support anything which requires one method 
> to accomplish something where the result for the end user is the same.
> It is (a)nother case of not messing with default user-agent features.
> This scenario also fits into the last clause:
> “unless the keyboard shortcut for a user interface component is only 
> active when that component has focus.”
> Pressing enter to submit a form only works when an input in the form 
> is in focus, therefore that “short-cut” isn’t in scope. (I think that 
> was the reason for including the focus aspect in the first place?)
> -Alastair

Regards, James

<> James Nurthen | Accessibility Architect
Phone: +1 650 506 6781 <tel:+1%20650%20506%206781> | Mobile: +1 415 987 
1918 <tel:+1%20415%20987%201918> | Video: 
Oracle Corporate Architecture
500 Oracle Parkway | Redwood City, CA 94065
<> Oracle is committed to developing 
practices and products that help protect the environment

Received on Friday, 5 January 2018 17:41:03 UTC