- From: Thaddeus <inclusivethinking@gmail.com>
- Date: Tue, 18 Apr 2017 18:24:39 -0700
- To: Gregg C Vanderheiden <greggvan@umd.edu>
- Cc: Mike Pluke <Mike.Pluke@castle-consult.com>, public-cognitive-a11y-tf <public-cognitive-a11y-tf@w3.org>, Joshue O Connor <josh@interaccess.ie>
- Message-ID: <CAOh2y+9zq=LyaRiss=OPozwwrYy6a7M13VcOsGVRj8t9oAzdPA@mail.gmail.com>
HI Gregg, 1. This is a level A. 2. The following exception addressed your second concern - Exception: The style is an essential part of the main function of the site, such as for a game. 3. The concept of personalization is found throughout much of our material. The is also a related SC here: https://github.com/w3c/wcag21/issues/6 Hope this answers all your questions. Best, Thaddeus On Mon, Apr 17, 2017 at 10:12 AM, Gregg C Vanderheiden <greggvan@umd.edu> wrote: > Hi > > A few questions > > what level is this proposed for? > > Does this eliminate any innovation or special interfaces for games or > education or ???? > > what does “personalized” mean? How do I test that my interface is > personalizable? > > > Just asking questions early that will be asked later. D > > Gregg C Vanderheiden > greggvan@umd.edu > > > > On Apr 14, 2017, at 1: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 > <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 > > >
Received on Wednesday, 19 April 2017 01:25:13 UTC