-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
visual clutter (Split from #61 2.4.5 language) #73
Comments
point 1a: Lighting is included in "environment" -- in this sentence and in the list later. |
point 1b:
vs
Is "functional vision" too jargony? Do we need to explain it? The title of that section is "Functional Vision". |
point 2: I think visual clutter is an aspect of the info design, rather than the environment. We should make sure it's adequately covered in the user needs. |
reply: we will create a user need or expand other needs to include clutter |
Action items from 9 June telecon:
|
Done.
still open ^ ^ ^
Done. |
I would like for us to re-think creating a new User Need for visual clutter. It is a usability issue for everyone, is a more significant issue for many people with cognitive disabilities, and seems only somewhat more of an issue for people with low vision. We have a user need for increasing margins and borders:
I propose that visual clutter doesn't quite meet the threshold for including in this LV user needs doc at this time, and we mark it as a Best Practice. (Hopefully before too long we'll get to working more on Best Practice doc!) We can add it to the LV user needs doc later if warranted. |
+1 to marking as a best practice. |
#61
from https://lists.w3.org/Archives/Public/public-low-vision-comments/2016AprJun/0003.html
Section 2.5: Functional Vision
· Paragraph after Issue 2. Other factors – such as inflammation, medication, fatigue, environment, and task (add in lighting) – influence a person's effective (replace with functional) vision in a given situation.
· Environmental factors include:
Add in ‘visual clutter’
The text was updated successfully, but these errors were encountered: