Resolution to Accept Icon font techniques

<jim> https://www.w3.org/WAI/GL/wiki/Icon_Font_with_an_On-Screen_Text_Alternative

<jim> https://www.w3.org/WAI/GL/wiki/Using_aria-hidden%3Dtrue_on_an_icon_font_that_AT_should_ignore

<jim> scribe: allanj

<shawn> Wayne: support

<shawn> [Shawn didn't get to study it in detail & has to abstain, no objection]

RESOLUTION: LVTF approves the 2 Icon Font Techniques

<ScottM> the motion carries!

<laura> Providing an On-Screen Text Alternative for an Icon Font

<laura> https://www.w3.org/WAI/GL/wiki/Icon_Font_with_an_On-Screen_Text_Alternative

<laura> Using aria-hidden="true" on an icon font that AT should ignore

<laura> https://www.w3.org/WAI/GL/wiki/Using_aria-hidden%3Dtrue_on_an_icon_font_that_AT_should_ignore

Issue 3 Minimum contrast of images and icons https://github.com/w3c/low-vision-SC/issues/3

<laura> WCAG Issue 96

<laura> https://github.com/w3c/wcag/issues/96#issuecomment-240109904

<laura> LVTF SC Issue 3

<laura> https://github.com/w3c/low-vision-SC/issues/3

<jim> originated as WCAG issue in 1996.

<jim> also, bug filed in 2015

<laura> jim: we need to add to our requirements doc.

<shawn> ACTION: Shawn, in User Needs doc, include coverage of contrast of info in graphics [recorded in http://www.w3.org/2016/08/18-lvtf-minutes.html#action01]

<trackbot> Error finding 'Shawn,'. You can review and register nicknames at <http://www.w3.org/WAI/GL/low-vision-a11y-tf/track/users>.

<laura> shawn: will add it.

<shawn> ACTION: Shawn in User Needs doc, include coverage of contrast of info in graphics [recorded in http://www.w3.org/2016/08/18-lvtf-minutes.html#action02]

<trackbot> Created ACTION-69 - in user needs doc, include coverage of contrast of info in graphics [on Shawn Henry - due 2016-08-25].

<jim> created a wiki page for new SC for icon contrast. https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Contrast_(Minimum)

<laura> Using sufficient contrast for images that convey information: https://www.w3.org/WAI/GL/wiki/Using_sufficient_contrast_for_images_that_convey_information

<laura> Scribe: Laura

Gap analysis updated - existing SCs http://w3c.github.io/low-vision-SC/GapAnalysis-SC.html

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

jim: created Wiki pages

Issue 3 Minimum contrast of images and icons https://github.com/w3c/low-vision-SC/issues/3

<jim> proposed SC for Graphic Contrast https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Contrast_(Minimum)

shawn: hadn’t read thread. Will read.
... can we modify existing SC?

<shawn> currrent: Contrast (Minimum): The visual presentation of text and images of text has a contrast ratio of at least

<shawn> maybe: Contrast (Minimum): The visual presentation of information (including text, graphical info) has a contrast ratio of at least

<shawn> maybe: Contrast (Minimum): The visual presentation of information (including text, graphical info, icons) has a contrast ratio of at least

Laura: need to define information

John: could create the criteria and let WCAG decide.

Scott: how we convey what we what to say is important so people understand it.
... mulit colors, pie chart, text.

<AWK> The current view of the WG is that we will add criteria rather than edit the existing ones.

AWK: On question of edit or new SC. Probably new SCs so existing techniques can stay in place.
... advice TF write as new SCs.

<jim> current proposed: Contrast (Minimum) - The visual presentation of images and icons that convey information have a contrast ratio of at least 4.5:1

wayne: 2 cases: contast within icons and contrast within images.

<shawn> [ within icons *and* between the icon and the backgroudn it's on]

wayne: first case is easiest. More hesitant on images.
... foreground and background is easiest.

<AWK> Also, SC 1.4.1 requires that people don't rely on color alone to convey information

AWK: complex with images.

jim: shopping cart icon pale that are not discernible

AWK: can’t be too broad.

<shawn> current draft wroding in <https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Contrast_(Minimum)> "The visual presentation of images and icons that convey information have a contrast ratio of at least 4.5:1"

wayne: can get pixelated with magnifiers.

<jim> need to include borders on buttons and form controls etc. as well as images on buttons.

wayne: icons as part of form controls.

shawn: is there some working for “important information”
... will do the user needs.

wayne: we can come up with definitions.

jim: we can get rid of charts and graphs, pictures.

<shawn> The visual presentation of [relevant|important] information (including text, images of text, icons, and graphics) has a contrast ratio of at least...

<JohnRochford> yes

<AWK> from COGA doc:

<AWK> important information information the user may need to complete any action or task including an offline task. information the user may need to know related to safety, risks, privacy, health or opportunities.

<AWK> from https://rawgit.com/w3c/coga/master/extension/index.html

<jim> awk: actionable items only?

<jim> laura: no, things that convey information

<jim> awk: what images that are not actionable are included?

AWK: gets complicated.

<jim> wayne: image of printer, undo icon, etc

<jim> jim: what about borders on form controls and buttons...or is it a different issue?

jim: borders a different issue?

wayne: I think so.

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

AWK: might fit into another category.

<Zakim> shawn, you wanted to say think things like field borders fit here...

shawn: seems like borders are the same thing. Needed to use the interface.

<jim> shawn: border contrast is important to using a page

shawn: default contrast.

<jim> shawn: default contrast needed for all things on page - text, images of text, borders, buttons, actionable things...not pictures, non-informative images

AWK: leave out stuff that we cannot achieve.

<jim> awk: are people with disabilities disporportionally affected or is it everybody.

AWK: are PWD disproportionately affected?

Shawn: Yes. If no field border, then usability for all. If light gray borders, then see-able by some, but not by some with low vision.

<jim> laura: information in pictures?

<jim> like charts? or something different. need examples

<jim> information in image - need an onscreen caption?

Scott: everything that is not decorative.

<AWK> This feels like one to verify if COGA is working on it. We should avoid redundant work

jim: how about requiring on screen text?

<AWK> (the "have a caption if the graphic has information in it" item)

<ScottM> captioning is a different issue I think

<JohnRochford> Info graphics would need longdescs, not alt text.

Jim: will ask coga.
... will add notes to Wiki page.

SC wiki pages

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

jim: new wiki page in WCAG format.

<JohnRochford> Ciao everyone. On to next meeting.

Sections include: SC Shortname, SC Text, Related Glossary additions or changes, What Principle and Guideline the SC falls within, Description, Benefits, Testability, Techniques

testability

AWK: testability is a problem. Avoid saying something is clear.
... needs to be evauated or measured.
... how it is tested may vary from technology to technology. But it needs to be testable

reflow to single column

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

<Wayne> 3.2.2 Reflow to Single Column Content must be flexible enough to reflow visually in a one column format using standard features or extensions of the user agent. Tabular data may appear as tables, so long as lines of text within table cells fit within a viewport. If no user agents for a given content type has a mechanism for reconfiguring the content into one column, then an alternative...

<Wayne> ...format must be provided that does support this requirement.

jim: tables can be too large. Images can be an exception too.

wayne: has a definition of tabular data.

<Wayne> Definition: A set of tabular data is two-dimensional array of data points for which inclusion of a data point within a row and column conveys meaning about the data point that cannot be derived from the data within the point itself. Data points may be complex objects like list, paragraphs or even nested sets of tabular data.

<ScottM> I like it

wayne: we can think about it for a week.

<Wayne> If no user agents for a given content type has a mechanism for the users to …xxx…, then an alternative format must be provided that does support this requirement.

wayne: created a general mechanism.

jim: relates to accessbility support
... doesn’t know if it is an SC.

<jim> could be a definition in WCAG similar to "accessibility supported"

jim: gets back to “until user agents” in WCAG 1

wayne: not the same.
... would like to streamline the language.

Gap analysis updated - existing SCs http://w3c.github.io/low-vision-SC/GapAnalysis-SC.html

Line Length https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Line_Length

<Wayne> 3.2.1 Line Length Content must be flexible enough to enable the user to choose the length of lines in the visual presentation. If no user agents for a given content type has a mechanism for users to choose the length of lines, then an alternative format must be provided that does support this requirement.

<jim> Current wording: Line Length - For the visual presentation of blocks of text, a mechanism is available such that width is user adjustable between no less than 5 characters and no more than 80 characters or glyphs (40 if CJK).

<Wayne> Failure: If a user must use bi-directional scrolling (horizontal and vertical) to perceive the text within a document object, then the content fails Line Length.

jim: do we need change of definition for 148?
... intent is just informative.

<jim> https://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-visual-presentation.html

jim: thoughts?
... think we will get push back on 5 characters.

<jim> blocks of text?

<jim> is this page or individual paragraphs, or elements

<Wayne> Content must be flexible enough to enable the user to choose the length of lines of text in the visual presentation.

wayne: we are talking about the visual presentation.
... users needs ability to have a specialized visual presentation.
... that we can see.
... magnifiers aren’t that good.

<Wayne> Definition: A line text within a presentation is a sequence printable symbols from a natural language, that display physically as a line segment that may be horizontal or vertical.

jim: 2 different tasks.

<jim> reading vs interacting with web page/application

jim: what are the requirements?

wayne: can not be longer than x.

shawn: if resize window & it automatically reflows that passes right?

wayne: yes.

<jim> what about long words - need auto hypenation

wayne: yes, long words - need auto hypenation.
... user can choose line length.

jim: user adjustable?

wayne: yes.
... bidirectional scrolling is not acceptable.
... will push to wiki.

<jim> wayne: SC unidirectional scrolling is the only way to go.

trackbot, end meeting

This is scribe.perl Revision: 1.144  of Date: 2015/11/17 08:39:34  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/close: tem 3//
Succeeded: s/close: item 3//
Succeeded: s/ The visual presentation of [important] information/ The visual presentation of [relevant|important] information/
Succeeded: s/Shawn: yes./Shawn: Yes. If no field border, then usability for all. If light gray borders, then see-able by some, but not by some with low vision./
Succeeded: s/ if it automatically/ if resize window & it automatically/
Found Scribe: allanj
Found Scribe: Laura
Inferring ScribeNick: laura
Scribes: allanj, Laura
Default Present: jim, shawn, Laura, Scott_M, John_R, Wayne, JohnRochford
Present: jim shawn Laura Scott_M John_R Wayne JohnRochford
Found Date: 18 Aug 2016
Guessing minutes URL: http://www.w3.org/2016/08/18-lvtf-minutes.html
People with action items: shawn

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.