Low Vision Accessibility Task Force Teleconference -- 06 Apr 2016

<allanj> agneda?

<AWK> +AWK

<allanj> scribe: wayne

Availability for Upcoming LVTF Teleconferences <https://www.w3.org/2002/09/wbs/81151/LVTF-telecons/>

<laura> + Laura

<allanj> close item 1

Legibility

<allanj> scribe: allanj

wayne: legibility and navigation. Half of user requirements are legibility.
... 4 points
... 1 recognize something - eye test
... 2 acuity limit - can read - lots of errors
... 3 font - line spacing - read at max speed with few errors
... 4 duration (fatigue) - read at speed, with few errors, for long time to get work done.

<scribe> scribe: wayne

<shawn> draft https://rawgit.com/w3c/low-vision-a11y-tf/user_need-legibility/requirements.html#user-needs

<shawn> the Notes and the paragrpah under it

scott: folks have different triggers for fatigue. how do we provide technical guidance

<scribe> scribe: allanj

<shawn> long version: https://github.com/w3c/low-vision-a11y-tf/issues/37

shawn: see first paragraph

wayne: legibility based on vision issue and how individuals deal with it

shawn: refine long version as a separate piece.
... is the note and paragraph sufficient in the requirements?

wayne: note and para are ok

<laura> https://rawgit.com/w3c/low-vision-a11y-tf/user_need-legibility/requirements.html#h-note1

scott: is distinguishing between similarly colored items covered

<JohnRochford_> +1 to info in section "3. User Needs" being sufficient

wayne: that is covered under element level styling, so user can configure colors

<Wayne> +1

<laura> +1

<shawn> Scott: looks good to me

<shawn> +1

<AWK> +1

<shawn> +1 (possibly with minor copy editing)

<shawn> Alan: looks good to me

RESOLUTION: Note and para. after covering legibility approved https://rawgit.com/w3c/low-vision-a11y-tf/user_need-legibility/requirements.html#h-note1

<scribe> scribe: wayne

<shawn> https://github.com/w3c/low-vision-a11y-tf/issues/34

Issue 34: Scope question

Scope Issue 34

allenj: There are many definitions of electronic content. Do we make one.

AWK: every thing will be in the context of WCAG. We should take the WCAG definition.

<Zakim> shawn, you wanted to say web content, elec content, WCAg2ICT

Shawn: There is web content, electronic content (broader than web). We talked about broader than web content.

<laura> WCAG: content (Web content) defintion: https://www.w3.org/TR/WCAG20/#contentdef

<ScottM> +1 AWK

<allanj> -1 to defining 'electronic content'

Shawn: Do we need to define it. There are lots of reasons not too. Should we not define it.

<shawn> WCAG2ICT "WCAG... can be applied to non-web Information and Communications Technologies (ICT)"

<shawn> -1 to defining 'electronic content'

JohnR: Does it relate to the web of things. Can we define it in that way. it it is connected to the web. Yes/No

allenj: Do we not define electronic content and move on.

RESOLUTION: The group deciided not to define electronic content.

<shawn> https://github.com/w3c/low-vision-a11y-tf/issues/38

Issue 38 re-word 3.1.1 brightness vs. contrast

Shawn: Is being able to increase brightness over all a special low vision need.

Scott: We need to say both issues are possible within the spectrum.

AllenJ: Even when contrast is high, and then they set brightness up. There is a combination of the two.

<jon_avila> +1

Scott: For me the brighter the better.

<shawn> no objection to adding it

<laura> +1

Wayne: For me the dimmer the better.

<ScottM> We want to drive home that there is a wide spectrum and flexibility is key'

RESOLUTION: Edit 3.1.1 to include brightness.

<shawn> https://github.com/w3c/low-vision-a11y-tf/issues/39

AllanJ: The color wheel may be duplicated.

Issue 39: color wheel images

AllanJ: Leave it as is.

RESOLUTION: Leave the color whels images as is.

<shawn> https://github.com/w3c/low-vision-a11y-tf/issues/40

AllenJ: Use of serif fonts and different font families.

<ScottM> +1 Shawn

<allanj> s/Allenj/Allanj

<Zakim> shawn, you wanted to say best practice & comic sans and that's the point

<allanj> http://w3c.github.io/low-vision-a11y-tf/requirements.html#font

Discussion: Use clean fonts. This is similar contrast minimum.

<ScottM> +1 Shawn

Shawn: The User Need is that people can pick a font that works for them. Making the default font a clean one is a best practice or technique

<JohnRochford_> +1 to Shawn's last commentary

Alan: This seems latin letter specific.

allanJ: I can ping about different alphabets.

<ScottM> +1 for putting in best practice

allanJ: do we need to change our user needs?

<allanj> +1 putting this issue in best practice document

<JohnRochford_> +1 for putting in best practice

Alan: WCAG 2.0 many things are tchniques etc.

<ScottM> Entering Microsoft license keys

<ScottM> :)

<laura> +1 for putting in best practice

<JohnRochford_> Gotta go, folks. Ciao.

RESOLUTION: Leave section 3.3.2 as it and cover specific fonts in best practice.

<shawn> [Wayne presentation for CCLV used APH font - and a lot of people didn't like it. switch to verdana and was better.]

<shawn> https://github.com/w3c/low-vision-a11y-tf/issues/41

3.3.3 Avoid italics Issue 41

JonA: This should be two items: You should avoid italic and you need to be able to change font style semantically.

<ScottM> +1 JonA

JonA: Style should convey meaning instead of for semantic reasons.

<Zakim> shawn, you wanted to say 1. comment resolution, 2. style (3.3.3) & element-level points need attention

There are semantic meaning that are assigned to meeaning. italic emphasizes it and bold emphasizes it more. Using something for look alone is confusing and difficult.

Shawn: ... 3.3.3 needs work.

<shawn> s/Avoind the use of italics when possible./ /

RESOLUTION: Leave 3.3.3. Cover italics in best practices.

<allanj> wayne: italic for citation or book title. italic usage semantics

<shawn> open issue for for LVTF comment https://github.com/w3c/low-vision-a11y-tf/labels/question

Shawn: List of open issues see above.

trackbot, end meeting

- DRAFT -

Low Vision Accessibility Task Force Teleconference

06 Apr 2016

Attendees

Contents