RE: Should WCAG2.1 provide requirements or guidance on buttons vs. links?

From: David MacDonald [mailto:david100@sympatico.ca]
Sent: Thursday, July 14, 2016 10:33 AM

 I'm suggesting they be introduced in the 2.1 suite because the WCAG 2 only requires that controls be keyboard operable, not that a control is activated with the standard keys, and the web is a bit wishy washy now on links vs buttons, so we'd have to put a stake in the ground on the difference, and make decisions on the grey areas, like opening a dialogue box.

[Jason] The “standard keys” tend to be operating system dependent. Currently, unfortunately, we don’t have a device-neutral way of specifying the actions available in a Web application, even for the common cases. This is a problem that IndieUI Events were intended to solve (an important development effort which may still continue under other working groups).


________________________________

This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited.


Thank you for your compliance.

________________________________