Minutes: Low Vision Taskforce 1 Sept 2016

source: https://www.w3.org/2016/09/01-lvtf-minutes.html

Low Vision Accessibility Task Force Teleconference 01 Sep 2016

See also: IRC log <http://www.w3.org/2016/09/01-lvtf-irc>
Attendees
PresentShawn, Laura, JohnRochford, JimAllan, ScottM, Andrew(second_part)
RegretswayneChairSV_MEETING_CHAIRScribeallanj, shawn, JohnR
Contents

   - Topics <https://www.w3.org/2016/09/01-lvtf-minutes.html#agenda>
      1. general <https://www.w3.org/2016/09/01-lvtf-minutes.html#item01>
      2. Action-70 Write Font SC
      <https://www.w3.org/2016/09/01-lvtf-minutes.html#item02>
      3. Action-71 Text Style Wording
      <https://www.w3.org/2016/09/01-lvtf-minutes.html#item03>
      4. Action-72 Capitalization SC
      <https://www.w3.org/2016/09/01-lvtf-minutes.html#item04>
      5. Action-73 Size of all elements SC
      https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Size_of_all_elements
      <https://www.w3.org/2016/09/01-lvtf-minutes.html#item05>
      6. Action-74 Element level customization SC
      <https://www.w3.org/2016/09/01-lvtf-minutes.html#item06>
      7. Action-75 update gap analysis - DONE
      <https://www.w3.org/2016/09/01-lvtf-minutes.html#item07>
      8. Action-76 use case for changing font size
      <https://www.w3.org/2016/09/01-lvtf-minutes.html#item08>
      9. Action-77 Printing Customized Text SC
      <https://www.w3.org/2016/09/01-lvtf-minutes.html#item09>
      10. Action-78 research on user settings
      <https://www.w3.org/2016/09/01-lvtf-minutes.html#item10>
      11. Action-79 write Mobile contrast on Large text research
      <https://www.w3.org/2016/09/01-lvtf-minutes.html#item11>
   - Summary of Action Items
   <https://www.w3.org/2016/09/01-lvtf-minutes.html#ActionSummary>
   - Summary of Resolutions
   <https://www.w3.org/2016/09/01-lvtf-minutes.html#ResolutionSummary>

------------------------------

<allanj> need a scribe

<allanj> scribe: allanj
general

<shawn> JohnR: Want to help more, but not sure now...

<shawn> shawn: would be good to make it clear to all what work is needed.

<shawn> *ACTION:* Jim inform TF of planned schedule and tasks that they can
do to fill in the wiki pages for proposed SCs :-) [recorded in
http://www.w3.org/2016/09/01-lvtf-minutes.html#action01]

<trackbot> Created ACTION-80 - Inform tf of planned schedule and tasks that
they can do to fill in the wiki pages for proposed scs :-) [on Jim Allan -
due 2016-09-08].

https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Main_Page

<shawn> scribe: shawn
Action-70 Write Font SC

<laura> Open actions:
https://www.w3.org/WAI/GL/low-vision-a11y-tf/track/actions/open

on Wayne

https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Font

<ScottM> I currently can't get into my w3c account
Action-71 Text Style Wording

wayne. nothing yet

agena?
Action-72 Capitalization SC

https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Capitalization

draft "For the visual presentation of blocks of text, a mechanism is
available such that capitalization is user adjustable."

Shawn: ... available for users to change capitalization.

<scribe> *ACTION:* Jim to make it easier to tell what is template text vs.
content. :-) [recorded in
http://www.w3.org/2016/09/01-lvtf-minutes.html#action02]

<trackbot> Created ACTION-81 - Make it easier to tell what is template text
vs. content. :-) [on Jim Allan - due 2016-09-08].
Action-73 Size of all elements SC
https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Size_of_all_elements

<JohnRochford> Jim: Will move the @@ statement in the Size of All Elements
to Element Level Customization.

Need to define elements?

Shawn: change elements to content?

Laura: content defined in WCAG?

Jim: Yes

<JohnRochford> Laura & Jim: Because elements are defined in WCAG, we should
not need to define it.

Laura: then we wouldn't have to define anyting

<scribe> scribe:JohnR

<JohnRochford> Shawn: elements will be changed to content

<JohnRochford> This discussion is about
https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Size_of_all_elements

+1 to Laura's thoroughness with providing background info!

<JohnRochford> + 1 million and 1

<scribe> *ACTION:* Shawn update User Needs/Requirements with change size of
all elements->content [recorded in
http://www.w3.org/2016/09/01-lvtf-minutes.html#action03]

<trackbot> Created ACTION-82 - Update user needs/requirements with change
size of all elements->content [on Shawn Henry - due 2016-09-08].

<JohnRochford> Laura: Just updated "Size Of All Elements" doc to use
"content" rather than "elements".

<laura>
https://w3c.github.io/html/semantics-embedded-content.html#the-picture-element

<JohnRochford> Laura: The simpler the better (for SC text).

<laura> 1.4.8:
https://www.w3.org/TR/WCAG20/#visual-audio-contrast-visual-presentation

<JohnRochford> Jim: Any objections to marking this as finalized?

<allanj> *ACTION:* jim to update gap analysis - size of all elements final
[recorded in http://www.w3.org/2016/09/01-lvtf-minutes.html#action04]

<trackbot> Created ACTION-83 - Update gap analysis - size of all elements
final [on Jim Allan - due 2016-09-08].
Action-74 Element level customization SC

<AWK_> +AWK

wayne not gotten to
Action-75 update gap analysis - DONE Action-76 use case for changing font
size

<JohnRochford> ScottM: May have modified the wrong SC by mistake.

<laura> https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Text_Size

<ScottM> https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Text_Size#SC_Text

<JohnRochford> text = Except for images of text, text can be resized
without assistive technology up to 400 percent without loss of content,
functionality, @@and readability.@@

<JohnRochford> Jim: 400% should instead be "up to the browser maximum"

<JohnRochford> ScottM: Browsers today prefer to increase the size of the
entire page/UI rather than just the text/font size.

<JohnRochford> Jim: We are going to leave this issue for now.
Action-77 Printing Customized Text SC

https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Printing_Customized_Text

latest draft wording: "A mechanism is available to allow users to print
page content that matches page presentation changes made by the user."

Shawn: for example, user style sheet changes in browser reflected in
printed content

<scribe> scribe: Shawn
Action-78 research on user settings

wayne
Action-79 write Mobile contrast on Large text research

Jim: not done yet
... Andrew, know what mobile said about text size? Know where the reseach
is that support OK for diff contrast for larger text.
... from original WCAG

awk: Not know, I'll poke around.

<AWK_>
http://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-contrast.html

<AWK_> Note: Calculations in [ISO-9241-3] and [ANSI-HFES-100-1988] are for
body text. A relaxed contrast ratio is provided for text that is much
larger.

<allanj> trackbot, end meeting

<laura> bye.
Summary of Action Items *[NEW]* *ACTION:* Jim inform TF of planned schedule
and tasks that they can do to fill in the wiki pages for proposed SCs :-)
[recorded in http://www.w3.org/2016/09/01-lvtf-minutes.html#action01]
*[NEW]* *ACTION:* Jim to make it easier to tell what is template text vs.
content. :-) [recorded in
http://www.w3.org/2016/09/01-lvtf-minutes.html#action02]
*[NEW]* *ACTION:* jim to update gap analysis - size of all elements final
[recorded in http://www.w3.org/2016/09/01-lvtf-minutes.html#action04]
*[NEW]* *ACTION:* Shawn update User Needs/Requirements with change size of
all elements->content [recorded in
http://www.w3.org/2016/09/01-lvtf-minutes.html#action03]

Summary of Resolutions [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, 1 September 2016 18:53:40 UTC