Re: Public Feedback on Familiar Design (Minimum) #49

+1 to Mike's revisions.


Jan McSorley
VP, Accessibility
Psychometrics and Testing Services

400 Center Ridge Drive, Suite E
Austin, TX  78753
M - (512) 673-9569
Twitter: @Jan_McSorley
Skype:  jan.mcsorley
www.linkedin.com/in/janmcsorley

Learn more at pearson.com

[image: Pearson]

*We put a man on the moon in the 1960's ... surely we can make information
technology fully accessible to people with disabilities.  It can be done
... it must be done ... it will be done!*

On Fri, Apr 14, 2017 at 12:10 PM, Michael Pluke <
Mike.Pluke@castle-consult.com> wrote:

> I’m definitely in favour of removing “easily” and “successfully” – this
> will never be accepted with these words in it. As a previous user interface
> will obviously have been used by users in a prior version, the last bullet
> should be cut down to just read “User interface from a prior version.”
>
>
>
> I think that we may have to go a little further than just removing
> “easily” from “ easily identifiable” as “identifiable is probably still an
> issue. How can someone test that a feature is “identifiable” – other than
> by running user tests to see whether the vast majority of users are able to
> identify that this feature is present? We know that requiring user testing
> to be able to see whether an SC has been met will not be accepted by the
> AGWG (or by people who will expect to use WCAG 2.1 in procurement). So I
> think that it will be necessary to remove “easily identifiable and”. Other
> SCs should ensure that the listed UI features are programmatically
> determinable, but nothing in WCAG currently requires that UI features are
> “identifiable” in the sense that they can be seen. There are however other
> SCs that cover aspects of the visibility of UI features such as contrast,
> etc.
>
>
>
> So I think that what we should be left with is:
>
>
>
> *Familiar design (Minimum): *Help, navigation to help and search forms
> are available to the user in one or more of the following ways:
>
>    - Platform specific: A platform specific user interface design.
>    - Adaptive interface: An adaptive user interface design that can be
>    personalized.
>    - User interface from a prior version.
>
> Best regards
>
> Mike
>
>
>
>
>
> *F**rom:* Thaddeus [mailto:inclusivethinking@gmail.com]
> *Sent:* 14 April 2017 17:35
> *To:* public-cognitive-a11y-tf <public-cognitive-a11y-tf@w3.org>
> *Cc:* Joshue O Connor <josh@interaccess.ie>
> *Subject:* Public Feedback on Familiar Design (Minimum) #49
>
>
>
> Good Morning Group,
>
>
>
> I was out for a couple of weeks and picking up on my SC Management.
>
>
>
> I seem to have the following consistent feedback on Familiar Design
>
>
>
> a. Easily and successfully are highly subjective terms. Please remove. -
> NOTE: this seems acceptable. Is it OK with the group to remove these terms?
>
>
>
> 'A user interface design that was used successfully by users in a prior
> version of the application' - this is inherently subjective and not a
> repeatable test. - NOTE: Historically there seems to have been a lot of
> pushback on this. Would we consider removing?
>
>
>
> Please bear with me as I get through managing these. It is a little
> overwhelming.
>
>
>
> Original SC Below:
>
>
>
> *Familiar design (Minimum): *Help, navigation to help and search forms
> are easily identifiable and available to the user in one or more of the
> following ways:
>
>    - Platform specific: A platform specific user interface design.
>    - Adaptive interface: An adaptive user interface design that can be
>    personalized.
>    - User interface from a prior version: A user interface design that
>    was used successfully by users in a prior version of the application.
>
>
> Exception: The style is an essential part of the main function of the
> site, such as for a game.
>
>
>
> Best!
>
> Thaddeus
>