RE: Fwd: PFWG-ISSUE-704 (Indication of Primary Button): Should there be an ARIA method to indicate the primary button? [ARIA 1.1]

What about allowing aria-selected on buttons?
This button would be selected in the sense that when you press enter it will get activated.


-----Original Message-----
From: Bryan Garaventa [mailto:bryan.garaventa@ssbbartgroup.com] 
Sent: Wednesday, February 25, 2015 4:58 PM
To: Joseph Scheuhammer; Joanmarie Diggs; James Nurthen
Cc: W3C WAI Protocols & Formats
Subject: RE: Fwd: PFWG-ISSUE-704 (Indication of Primary Button): Should there be an ARIA method to indicate the primary button? [ARIA 1.1]

I see what you mean, I was mainly thinking of the conveyance of a styling difference, one button styled differently as part of a set. I think the concept would fit, but basically you would need a new attribute that functionally does the same thing.


-----Original Message-----
From: Joseph Scheuhammer [mailto:clown@alum.mit.edu] 
Sent: Wednesday, February 25, 2015 1:15 PM
To: Bryan Garaventa; Joanmarie Diggs; James Nurthen
Cc: W3C WAI Protocols & Formats
Subject: Re: Fwd: PFWG-ISSUE-704 (Indication of Primary Button): Should there be an ARIA method to indicate the primary button? [ARIA 1.1]

> Wouldn't this be a good use case for aria-current? Since this is now token based, we could add a primarybutton token or something like.

That depends on the use case.  I think James' use case is, for example, a dialog that has multiple buttons for dismissing.  One of those buttons is designated the default button, frequently activated by a return key press.

An example:  A dialog that says "You have unsaved changes.  Do you want to save the changes before closing?", with "Don't Save", "Cancel", and "Save" buttons.  Here, the "Save" button is the default.

If that's the use case, aria-current is not the right attribute.

--
;;;;joseph.

'Array(16).join("wat" - 1) + " Batman!"'
            - G. Bernhardt -

Received on Wednesday, 25 February 2015 22:00:42 UTC