I can live with that.
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, Jun 14, 2018 at 5:12 AM, Alastair Campbell <acampbell@nomensa.com>
wrote:
> *> *I'm nervous about requiring momentary transient states to pass. Its
> new territory for WCAG. It hard on testers and hard on developers, for
> little good.
>
>
>
> It is also quite rare to find, you’ll see from the examples that only the
> default (un-styled) link and a quiz had ‘active’ states.
>
> The default button does have an active state, but does not rely on colour:
> The text moves down-right to create a 3d effect.
>
>
>
> As soon as you give a link a default colour, the ‘active’ and visited
> states disappear (unless you set :active :visited, or only use a:link). In
> general people use things like:
>
> a {color:blue;}
>
>
>
> So those states disappear, and aren’t really missed.
>
>
>
> Given that the intent is: “If you provide meaningful information via
> states then make sure people can discern them”, I don’t have a problem with
> adding something like what you proposed, how about:
>
>
>
> "momentary transition states such as 'active' are hard to register
> visually for all users and are generally not considered to convey
> information required for that component."
>
>
>
> I added ‘generally’ because there could be niche cases like the quiz where
> it does try to convey information in that state.
>
>
>
> But for the very accessibility/usability-aware, I don’t really want to
> punish people who provide hints with :visited, conveying that in a way
> other than using purple is not often recognised.
>
>
>
> -Alastair
>
Received on Thursday, 14 June 2018 12:34:53 UTC