Re: ARIA 1.1: primary button attribute proposal

Looks great :) Couple of questions.
> Indicates that an element is the primary action which is intended to occur within the button's landmark or dialog.
> 
I think we can leave out “which is intended”; primary action in itself means that something is going to occur. It feels more complicated than it is.
> The Ok button in a dialog, or the Search action in a Search region.
> 
On OS X OK buttons are labelled with all caps “OK”. How is this done on other platforms? And I think that “Search action” should be “Search button”; that would make it consistent with the other examples.

+1 on the rest.

—Michiel

> On 03 Dec 2015, at 19:39, James Nurthen <james.nurthen@oracle.com> wrote:
> 
> I completely forgot about the call today - my agenda entry must have timed out.
> I do want this too. I had an initial proposal which I put forward at TPAC but we decided we wanted to make some changes.
> 
> This was the original proposal
> 
> 
> The minutes from TPAC are here 
> http://www.w3.org/2015/10/26-aria-minutes.html#item03 <http://www.w3.org/2015/10/26-aria-minutes.html#item03>
> 
> 
> I propose the following update based on these minutes
> 
> aria-primaryaction (property)§ <x-msg://24/#aria-primaryaction>
> Indicates that an element is the primary action which is intended to occur within the button's landmark or dialog. Generally, this would only be present if there is a different visual indication for the primary action.
> 
> A keyboard user would normally activate the primary action through use of the enter key, even if they are not focussed on the current control. Typically this is used for features such as the Next button in a Wizard, The Ok button in a dialog, or the Search action in a Search region.
> 
> Authors should ensure that there is only one primary action within a landmark region or a dialog. If it is placed on a button that is not within a landmark or dialog container it is considered to be an author error.
> 
> Characteristics:
> Characteristic Value
> Used in Roles: Button
> Inherits into Roles: 
> Value: true/false <x-msg://24/#valuetype_true-false>
> If this is good I'd be happy for someone else to make these updates.
> 
> Regards,
> James
> 
> 
> On 12/3/2015 10:27 AM, Michiel Bijl wrote:
>> Hi James,
>> 
>> On the ARIA call today we discussed the primary button attribute proposal. It was questioned whether we wanted it for 1.1 or if we should push it to 2.0. I said I’d like to have it in and was willing to write a proposal if that is what it takes to get it in 1.1. You said a couple weeks back that you were working on it. But haven’t asked since then. So maybe it’s ready, I don’t know.
>> 
>> If you haven’t worked on it, is it okay if I have a crack at it?
>> 
>> —Michiel
>> 
> 
> -- 
> Regards, James
> <oracle_sig_logo.gif> <http://www.oracle.com/>
> James Nurthen | Principal Engineer, Accessibility
> Phone: +1 650 506 6781 <tel:+1%20650%20506%206781> | Mobile: +1 415 987 1918 <tel:+1%20415%20987%201918> | Video:  <sip:james.nurthen@oracle.com>james.nurthen@oracle.com <mailto:james.nurthen@oracle.com> 
> Oracle Corporate Architecture
> 500 Oracle Parkway | Redwood Cty, CA 94065 
> <green-for-email-sig_0.gif> <http://www.oracle.com/commitment> Oracle is committed to developing practices and products that help protect the environment
>