Re: Visual indicators

+1

A somewhat simple example is the latest Android version of the Facebook 
App now has the "Post" button at the top right in plain text on the 
background colour. It's in all caps and slightly grey (for extra 
confusion for those used to grey meaning disabled) it is also slightly 
raised above the font baseline. Otherwise, it is visually almost 
identical to the 'Create Post' title just to it's left.

This even confused me as I scanned for an obvious button to use to 
complete the process of posting. I think this is the sort of example we 
want to fail in the SC.

Steve

On 28/04/2020 22:06, Rachael Bradley Montgomery wrote:
> Hello David,
> 
> I personally (no chair hat) don't support limiting the scope of this to 
> the legal or financial transactions. I would rather it stay in line with 
> hidden controls which scopes to "Controls needed to progress or complete 
> a process..."
> 
> Regards,
> 
> Rachael
> 
> 
> 
> On Tue, Apr 28, 2020 at 3:09 PM David MacDonald <david@can-adapt.com 
> <mailto:david@can-adapt.com>> wrote:
> 
>     HI All
> 
>     At the end of the meeting today, I described the history of the
>     visual indicators SC and how we are on the edge of the consensus
>     couple of weeks ago and then splintered out into numerous
>     iterations.  It sounds like there was just a misunderstanding about
>     this previous version and COGA appears to be in agreement with the
>     language.
> 
>     I've made a clean copy and have updated the understanding
>     document. Of course there would be discussion about exemptions in
>     the definition of process but I think were pretty close to something
>     that is tight enough that authors would know when it applies and
>     when it doesn't apply.
> 
>     Lisa will be getting some additional examples this week to build out
>     the understanding a little bit further. I think the text in this
>     version is something that we may be able to rally around and get
>     consensus. Understanding that we would want to go further once
>     personalization is mature which would be in the next major version
>     of WCAG.
> 
>     I've made a copy of the previous versions and we have a full archive
>     of all comments and discussions and versions leading up to this
>     point for anybody who wants them.
> 
>     https://docs.google.com/document/d/1WhZAbswvPHs7A3stfqM_ATsaBHPeGbHtARcmaKMck1U/edit?usp=sharing
> 
>     Cheers,
>     David MacDonald
> 
>     *Can**Adapt**Solutions Inc.*
> 
>     Mobile:  613.806.9005
> 
>     LinkedIn
>     <http://www.linkedin.com/in/davidmacdonald100>
> 
>     twitter.com/davidmacd <http://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>
> 
> 
> 
> -- 
> Rachael Montgomery, PhD
> Director, Accessible Community
> rachael@accessiblecommunity.org <mailto:rachael@accessiblecommunity.org>
> 
> "I will paint this day with laughter;
> I will frame this night in song."
>   - Og Mandino
>

Received on Wednesday, 29 April 2020 08:42:18 UTC