Re: Suggestion for "action" value: section 3.1.4

Hello Sailesh,
We discussed your email in our Personalization meeting this morning and were unclear as to what you mean by “balance” as a mid range value.
Could you provide us a use case and explain what button this would be associated with, as all our data-action’s are as we have defined action as: The action attribute provides the context of a button. It is typically used on a button element or element with role="button”.  Or if this is a destination then we have the definition as : The destination attribute categorizes the target of a hyperlink.

All of our other “actions” are specific types of buttons that we are adding more semantic information to so that 3rd party add-ons can customize those buttons for that particular user’s needs, ie. “Undo button, save button, home button”.

As for “select/deselect” we were unclear how this would work as these are states of checkboxes, radio buttons etc, which is already exposed to AT.  Here again if you can provide us with a use-case and what you would expect to happen in terms of a personalization affordance.

Thanks
EOM
Charles LaPierre
Technical Lead, DIAGRAM and Born Accessible
Twitter: @CLaPierreA11Y
Skype: charles_lapierre


On Oct 11, 2019, at 10:29 AM, Sailesh Panchang <sailesh.panchang@deque.com<mailto:sailesh.panchang@deque.com>> wrote:

Hello!
For action values (under 3.1 section):
1. Consider "balance"  which  will set  to mid-value of range.
2. Any reason why select / deselect are not in the list? These could
be applied  to a button  to indicate state on / off.
(It could also apply to checkbox and radio control ... but I see scope
is only button).
Reference draft at https://w3c.github.io/personalization-semantics/content/

Thanks,


--
Sailesh Panchang
Principal Accessibility Consultant
Deque Systems Inc
381 Elden Street, Suite 2000, Herndon, VA 20170
Mobile: 571-344-1765