- From: Jim Allan <jimallan@tsbvi.edu>
- Date: Thu, 2 Jun 2016 11:47:21 -0500
- To: public-low-vision-a11y-tf <public-low-vision-a11y-tf@w3.org>
- Message-ID: <CA+=z1W=v1LuAqiZj+iQvh7ztsWtzUOvh+cib-jonXvKRqN_STA@mail.gmail.com>
source: https://www.w3.org/2016/06/02-lvtf-minutes.html
Low Vision Accessibility Task Force Teleconference 02 Jun 2016
See also: IRC log <http://www.w3.org/2016/06/02-lvtf-irc>
Attendees
Presentallanj, Shawn, andrew, laura, wayneRegretsJohnRChairJim and Andrew
Scribeallanj
Contents
- Topics <https://www.w3.org/2016/06/02-lvtf-minutes.html#agenda>
1. Password fields
<https://www.w3.org/2016/06/02-lvtf-minutes.html#item01>
2. italics, bold, underline #50
https://github.com/w3c/low-vision-a11y-tf/issues/50
<https://www.w3.org/2016/06/02-lvtf-minutes.html#item02>
3. italics, bold, underline #50
<https://www.w3.org/2016/06/02-lvtf-minutes.html#item03>
4. 3.3.4 capitalization - orthography #65
https://github.com/w3c/low-vision-a11y-tf/issues/65
<https://www.w3.org/2016/06/02-lvtf-minutes.html#item04>
5. Editorial: Electronic vs Digital content #66
https://github.com/w3c/low-vision-a11y-tf/issues/66
<https://www.w3.org/2016/06/02-lvtf-minutes.html#item05>
6. Editorial: Language, Jargon #60
https://github.com/w3c/low-vision-a11y-tf/issues/60
<https://www.w3.org/2016/06/02-lvtf-minutes.html#item06>
7. Section 2.4 https://github.com/w3c/low-vision-a11y-tf/issues/68
<https://www.w3.org/2016/06/02-lvtf-minutes.html#item07>
8. visual clutter
<https://www.w3.org/2016/06/02-lvtf-minutes.html#item08>
9. Section 2.4.1 https://github.com/w3c/low-vision-a11y-tf/issues/69
<https://www.w3.org/2016/06/02-lvtf-minutes.html#item09>
10. Section 2.4.3 https://github.com/w3c/low-vision-a11y-tf/issues/71
<https://www.w3.org/2016/06/02-lvtf-minutes.html#item10>
11. Section 2.4.4 https://github.com/w3c/low-vision-a11y-tf/issues/72
<https://www.w3.org/2016/06/02-lvtf-minutes.html#item11>
- Summary of Action Items
<https://www.w3.org/2016/06/02-lvtf-minutes.html#ActionSummary>
- Summary of Resolutions
<https://www.w3.org/2016/06/02-lvtf-minutes.html#ResolutionSummary>
------------------------------
close item 9
<scribe> scribe: allanj
sh: do proposed resolutions, then have folks vote on github
laura: CfC?
awk: no CfC in taskforce. too formal
close item 1
Password fields
<shawn> https://www.w3.org/2001/12/zakim-irc-bot
<shawn> here maybe https://www.w3.org/2001/12/zakim-irc-bot#agenda
<shawn> zakim-rage
Proposal
User Need - Password: Users need to be able to see the entire password as
text before it is submitted.
sh: don't want a new need, can't we put it somewhere else
verification of pw and number of characters is stressful, and time consuming
lc: there is a toolbar with a setting to show passwords
sh: can we squeeze it in somewhere?
<shawn> maybe
http://w3c.github.io/low-vision-a11y-tf/requirements.html#seeing-all-interface-elements
sh: edits pending to that section, to be broadened
wd: very stressful,
sh: propose putting in 3.7.1
lc: +1
awk: adding pw visibility to 3.7.1....seems weird
wd: tentative +1
ja: either 3.7.1 or create a new need
awk: 3.3?
wd: perhaps operation, high stakes. WCAG forms with legal consequences
sh: if in 3.3 then will be a new need
awk: will be lots of discussion about disproportionate impact on COGA or
LV. but lots of people have issues with pw
sh: agree, everybody has issues with pw. not quite threshold.
... dots (masking) is the issue
*RESOLUTION: Shawn to write password visibility addition to 3.7.1*
close item
italics, bold, underline #50
https://github.com/w3c/low-vision-a11y-tf/issues/50 italics, bold,
underline #50
this is a rewording of 3.3.3 and new intro for 3.5.1
*RESOLUTION: reword 3.3.3 and change intro for 3.5.1 per issue discussion*
3.3.4 capitalization - orthography #65
https://github.com/w3c/low-vision-a11y-tf/issues/65
<scribe> *ACTION:* jim to write COGA about orthgraphy [recorded in
http://www.w3.org/2016/06/02-lvtf-minutes.html#action01]
<trackbot> Created ACTION-59 - Write coga about orthgraphy [on Jim Allan -
due 2016-06-09].
wd: need vs success critera
sh: commenter - in German, all nouns are capitaized, authors should do it
right
awk: english evolved. chances of enforcing "standard english"
close item 4
Editorial: Electronic vs Digital content #66
https://github.com/w3c/low-vision-a11y-tf/issues/66
*RESOLUTION: current wording is fine, not changing*
close item 5
Editorial: Language, Jargon #60
https://github.com/w3c/low-vision-a11y-tf/issues/60
*RESOLUTION: use shawn's comment*
close item 6
open item 7
Section 2.4 https://github.com/w3c/low-vision-a11y-tf/issues/68
sh: are light sensitivity and glare sensitivity different?
... is there a condition where glare is an issue but not light
wd: cataracts, issues with ocular fluid
sh: do we change title of 2.4.2 Light sensitivity to include Glare also?
<shawn>
http://w3c.github.io/low-vision-a11y-tf/requirements.html#light-sensitivity
<scribe> *ACTION:* shawn to write up bit on glare sensitivity to 2.4.2 with
Jim (one or two sentences) [recorded in
http://www.w3.org/2016/06/02-lvtf-minutes.html#action02]
<trackbot> Created ACTION-60 - Write up bit on glare sensitivity to 2.4.2
with jim (one or two sentences) [on Shawn Henry - due 2016-06-09].
visual clutter
wd: background images
sh: in same category of changing font size, background color, etc.
wd: yes, same category, but need to specify background images
sh: comment - visual clutter is environmental factor. shawn - not so much
... but visual clutter may be a user need. do we have visual clutter
covered?
<scribe> *ACTION:* wayne to review document for adequacy of "visual
clutter" coverage and verbiage [recorded in
http://www.w3.org/2016/06/02-lvtf-minutes.html#action03]
<trackbot> Created ACTION-61 - Review document for adequacy of "visual
clutter" coverage and verbiage [on Wayne Dick - due 2016-06-09].
wd: may need something on tracking and scanning
sh: point 2 & 3 addressed.
... point 1, wording issue
... proposed wording "This section briefly introduces types of visual
impairment that impact web use, not including total blindness: Visual
acuity (clarity), Light sensitivity, Contrast sensitivity, Field of vision,
Color vision"
+1
changed "categories" in original to "types"
<laura> +1
*RESOLUTION: change wording for intro in section 2.4*
close item 7
Section 2.4.1 https://github.com/w3c/low-vision-a11y-tf/issues/69
wd: concerned about functional vision when operating the web
*RESOLUTION: update document to reflect shawn's wording in the issue*
close item 8
Section 2.4.3 https://github.com/w3c/low-vision-a11y-tf/issues/71
How about change the first sentence from:
Contrast sensitivity is the ability to distinguish bright and dim areas of
images, for example, to discern text on a background.
to:
Contrast sensitivity is the ability to detect differences in brightness
between targets and their backgrounds, for example, to discern text from
its background.
wd: targets - poor word
shawn: objects, better
*RESOLUTION: change to "Contrast sensitivity is the ability to detect
differences in brightness between objects and their backgrounds, for
example, to discern text from its background.*
close item 10
Section 2.4.4 https://github.com/w3c/low-vision-a11y-tf/issues/72
awk: in item 10, point is not detect difference but to get the information
sh: medical testing vs functioning
awk: contrast sensitivity is the ability to detect difference in brightness
in content
sh: are we talking about adjacent information. link in text (distinguished
by color), need to be able to tell the difference just by color/brightness
lc: similar to pie charts (adjacent colors)
<AWK> ...to detect differences in content and interfaces, for example,...
ja: pie charts - add texture or other feature for block of color
sh: contrast sensitivity difference in luminance that makes an object
distinguishable
... ability to detect difference in brightness.
<shawn> > Contrast sensitivity is the ability to detect differences in
brightness, for example, to discern text from its background.
<laura> bye
*RESOLUTION: 2.4.3 change wording "Contrast sensitivity is the ability to
detect differences in brightness, for example, to discern text from its
background."*
trackbot, end meeting
Summary of Action Items *[NEW]* *ACTION:* jim to write COGA about
orthgraphy [recorded in
http://www.w3.org/2016/06/02-lvtf-minutes.html#action01]
*[NEW]* *ACTION:* shawn to write up bit on glare sensitivity to 2.4.2 with
Jim (one or two sentences) [recorded in
http://www.w3.org/2016/06/02-lvtf-minutes.html#action02]
*[NEW]* *ACTION:* wayne to review document for adequacy of "visual clutter"
coverage and verbiage [recorded in
http://www.w3.org/2016/06/02-lvtf-minutes.html#action03]
Summary of Resolutions
1. Shawn to write password visibility addition to 3.7.1
<https://www.w3.org/2016/06/02-lvtf-minutes.html#resolution01>
2. reword 3.3.3 and change intro for 3.5.1 per issue discussion
<https://www.w3.org/2016/06/02-lvtf-minutes.html#resolution02>
3. current wording is fine, not changing
<https://www.w3.org/2016/06/02-lvtf-minutes.html#resolution03>
4. use shawn's comment
<https://www.w3.org/2016/06/02-lvtf-minutes.html#resolution04>
5. change wording for intro in section 2.4
<https://www.w3.org/2016/06/02-lvtf-minutes.html#resolution05>
6. update document to reflect shawn's wording in the issue
<https://www.w3.org/2016/06/02-lvtf-minutes.html#resolution06>
7. change to "Contrast sensitivity is the ability to detect differences
in brightness between objects and their backgrounds, for example, to
discern text from its background.
<https://www.w3.org/2016/06/02-lvtf-minutes.html#resolution07>
8. 2.4.3 change wording "Contrast sensitivity is the ability to detect
differences in brightness, for example, to discern text from its
background."
<https://www.w3.org/2016/06/02-lvtf-minutes.html#resolution08>
[End of minutes]
--
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 Thursday, 2 June 2016 16:47:50 UTC