RE: Issues with supporting "enter" key for activation of buttons in APG examples

Sorry for all the confusion I created on this issue.

Elements with Button role are activated on ENTER and SPACE, checkbox only changes state on SPACE.

Jon


From: Matt King [mailto:a11ythinker@gmail.com]
Sent: Friday, January 27, 2017 11:45 AM
To: 'Steve Faulkner' <faulkner.steve@gmail.com>; 'Joseph Scheuhammer' <clown@alum.mit.edu>
Cc: 'ARIA Working Group' <public-aria@w3.org>
Subject: RE: Issues with supporting "enter" key for activation of buttons in APG examples

Jon,

The discussion was about issue 233, which is about checkbox, not button.
https://github.com/w3c/aria-practices/issues/233


The APG says buttons work with both enter and space. We have not changed that, and there has not been any discussion about doing so … with the exception of this thread.

Based on long-standing native button conventions, I do not think we should change the guidance for buttons.

Matt
From: Steve Faulkner [mailto:faulkner.steve@gmail.com]
Sent: Friday, January 27, 2017 9:01 AM
To: Joseph Scheuhammer <clown@alum.mit.edu<mailto:clown@alum.mit.edu>>
Cc: ARIA Working Group <public-aria@w3.org<mailto:public-aria@w3.org>>
Subject: Re: Issues with supporting "enter" key for activation of buttons in APG examples


On 27 January 2017 at 16:54, Joseph Scheuhammer <clown@alum.mit.edu<mailto:clown@alum.mit.edu>> wrote:
I experimented with a <button>
element using FF and Safari on a Mac, and it did *not* respond to ENTER
when it had focus; only SPACE.

the mac and windows behaviours are different, this does not mean we should restrict to mac.

--

Regards

SteveF
Current Standards Work @W3C<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.paciellogroup.com_blog_2015_03_current-2Dstandards-2Dwork-2Dat-2Dw3c_&d=DwMFaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=REZD8fc2AwufInstfW3L5jSLVS8bjZtAodDOhat7yAI&m=wT5fVc-_EH19D7AdqMa6KdUS6X8tFx3qd7QvUm48aXc&s=XTJJhJt0u0LkMKCKoeJQnaYQQQhJ-AcTuBUhQ01nfZQ&e=>