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

>> If these are “failures”, they would be so according to the existing
success criteria as you indicate. Besides possible clarification of 3.2.4,
are there other issues here that would need to be taken up in the
development of WCAG 2.1 (the Guidelines, not the non-normative Techniques
or Failures)?

 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.

Cheers,
David MacDonald



*Can**Adapt* *Solutions Inc.*
Tel:  613.235.4902

LinkedIn
<http://www.linkedin.com/in/davidmacdonald100>

twitter.com/davidmacd

GitHub <https://github.com/DavidMacDonald>

www.Can-Adapt.com <http://www.can-adapt.com/>



*  Adapting the web to all users*
*            Including those with disabilities*

If you are not the intended recipient, please review our privacy policy
<http://www.davidmacd.com/disclaimer.html>

On Thu, Jul 14, 2016 at 9:15 AM, White, Jason J <jjwhite@ets.org> wrote:

>
>
>
>
> *From:* David MacDonald [mailto:david100@sympatico.ca]
> *Sent:* Wednesday, July 13, 2016 4:25 PM
>
> There are two possible failures under 1.3.1 and 2.1.1 that occur to me.
>
>
>
> ·        Failure of 4.1.2 due to using a link as a button, without a
> button role.
>
> ·        Failure of 2.1.1 due to using a link for a button without
> trapping spacebar to activate button
>
>
> *[Jason] *If these are “failures”, they would be so according to the
> existing success criteria as you indicate. Besides possible clarification
> of 3.2.4, are there other issues here that would need to be taken up in the
> development of WCAG 2.1 (the Guidelines, not the non-normative Techniques
> or Failures)?
>
>
>
> ------------------------------
>
> 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.
> ------------------------------
>