Re: lvtf-ACTION-37

Jonathan,

Right, I agree we don't want specific contrast ratio now.

The current document is about user needs. In the user needs section, each user need explains the issue, provides examples where helpful, and states the user need.

As I understand it, the user need that is the fundamental issue is that users can tell the state of the control. That could be provided by contrast, or it could be provided other visual ways, for example, with text. I'm not even sure we will want to specify a specific contrast ratio, because it will be different for different users -- e.g., sufficient contrast for a person with low contrast sensitivity might be too bight for a person with photophobia.

So I was thinking that we want to make the user need broader than just about contrast -- it's about identifying the state. It might make sense to include an example of contrast.

~Shawn



On 3/9/2016 9:48 AM, Jonathan Avila wrote:
> Shawn,
> We could insert a specific contrast ratio now if you would like -- but I figured we hadn't decided on those types of things.  While your suggested user need appears to more broadly address the issue I feel like it's too open and could be seen as being met by programmatic methods rather than met visually.
>
> Jonathan
>
>
> -----Original Message-----
> From: Shawn Henry [mailto:shawn@w3.org]
> Sent: Wednesday, March 09, 2016 10:28 AM
> To: public-low-vision-a11y-tf@w3.org
> Subject: Re: lvtf-ACTION-37
>
> Let's keep this wording for draft possible SC wording in the future -- although we'd have to be more specific than "sufficient". :)
>
> In the current doc, we have broad user needs, rather than requirements -- skim through <http://w3c.github.io/low-vision-a11y-tf/requirements.html#user-needs>
>
> How about something like this for the broad User Need:
>  "Users can distinguish states, such as the active, selection, and focus states of buttons"
> and the intro explanation explains about luminosity/brightness.
>
> Or can we broaden it even more to cover other examples?
> Or do we focus only on luminosity/brightness on this and have it apply to broader things than states?
>
> ~Shawn
>
>
> On 3/3/2016 4:28 PM, Jim Allan wrote:
>> +1 on this version: “User Need: When differences in luminosity _alone_ are used to communicate meaning including active, selection, and focus states, the difference in luminosity is sufficient between different states.”
>>
>> having an additional user need for when luminosity is not sufficient is also needed.
>>
>> at some time in the future we will get to the definition of "sufficient" in this context. Not now, we need to finish the needs.
>>
>> Jim
>>
>> On Thu, Mar 3, 2016 at 11:10 AM, ALAN SMITH <alands289@gmail.com <mailto:alands289@gmail.com>> wrote:
>>
>>      I think we need the word “alone” as a clarification. Screenreaders will need something else, however, our user need is specific to low vision users to capture their unique requirements.
>>
>>      __ __
>>
>>      __ __
>>
>>      +1 on this version: “User Need: When differences in luminosity _alone_ are used to communicate meaning including active, selection, and focus states, the difference in luminosity is sufficient between different states.”____
>>
>>      __ __
>>
>>      Alan____
>>
>>      __ __
>>
>>      Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10
>>
>>      __ __
>>
>>      *From: *Jonathan Avila <mailto:jon.avila@ssbbartgroup.com>
>>      *Sent: *Thursday, March 3, 2016 8:20 AM
>>      *To: *Rochford, John <mailto:john.rochford@umassmed.edu>; public-low-vision-a11y-tf <mailto:public-low-vision-a11y-tf@w3.org>
>>      *Subject: *RE: lvtf-ACTION-37
>>
>>      __ __
>>
>>      John, perhaps it could add the word “alone” or something like that.  Feel free to change the wording on my behalf I am flexible.____
>>
>>      __ __
>>
>>      User Need: When differences in luminosity _alone_ are used to communicate meaning including active, selection, and focus states, the difference in luminosity is sufficient between different states.____
>>
>>      __ __
>>
>>      Jonathan ____
>>
>>      __ __
>>
>>      *From:*Rochford, John [mailto:john.rochford@umassmed.edu <mailto:john.rochford@umassmed.edu>]
>>      *Sent:* Thursday, March 03, 2016 7:29 AM
>>      *To:* Jonathan Avila; public-low-vision-a11y-tf
>>      *Subject:* RE: lvtf-ACTION-37____
>>
>>      __ __
>>
>>      Hi Jon,
>>
>>      __ __
>>
>>      I suggest that "or additional means other than luminosity are used to communicate meaning" is unnecessary; and contributes to making that long sentence confusing. I can provide more detail if you want.
>>
>>      __ __
>>
>>      John____
>>
>>      __ __
>>
>>      John Rochford <http://profiles.umassmed.edu/profiles/display/132901>
>>      UMass Medical School/E.K. Shriver Center
>>      Director, INDEX Program
>>      Instructor, Family Medicine & Community Health
>>      www.DisabilityInfo.org <http://www.DisabilityInfo.org>
>>      Twitter: @ClearHelper <https://twitter.com/clearhelper>____
>>
>>      __ __
>>
>>      -----Original Message-----
>>      From: Jonathan Avila [mailto:jon.avila@ssbbartgroup.com]
>>      Sent: Wednesday, March 02, 2016 2:35 PM
>>      To: public-low-vision-a11y-tf <public-low-vision-a11y-tf@w3.org <mailto:public-low-vision-a11y-tf@w3.org>>
>>      Subject: lvtf-ACTION-37
>>
>>      __ __
>>
>>      User Need: When differences in luminosity are used to communicate meaning including active, selection, and focus states, the difference in luminosity is sufficient between different states or additional means other than luminosity are used to communicate meaning.
>>
>>      __ __
>>
>>      __ __
>>
>>      __ __
>>
>>      Jonathan
>>
>>      __ __
>>
>>      __ __
>>
>>
>>
>>
>> --
>> Jim Allan, Accessibility Coordinator
>> Texas School for the Blind and Visually Impaired
>> 1100 W. 45th St., Austin, Texas 78756
>> voice 512.206.9315    fax: 512.206.9264 http://www.tsbvi.edu/
>> "We shape our tools and thereafter our tools shape us." McLuhan, 1964
>

Received on Wednesday, 16 March 2016 02:08:03 UTC