W3C

- DRAFT -

Low Vision Accessibility Task Force Teleconference

09 Aug 2018

Attendees

Present
jon_avila, Laura, Jim, Jason, Shawn, Wayne
Regrets
Laura, Jason
Chair
SV_MEETING_CHAIR
Scribe
Jim

Contents


<JohnRochford> Hi Wayne. I'm joining this meeting to learn more about your generated-content work.

<JohnRochford> I can't get in by phone yet.

<JohnRochford> ok

<WayneD> * Morning All

<JohnRochford> I joined, but I can't hear anyone.

<scribe> scribe: Jim

Please review Reflow Understanding Doc - wording changes https://www.w3.org/WAI/WCAG21/Understanding/reflow.html

close item 1

F87, Issue 433 Generated Content - Wayne response - https://drive.google.com/file/d/1TfmTC3U1zFd9Hz8Oankfm-uV30xUjsmw/view?ts=5b6b3bbe

wd: tested all of Jon's issues and found them all true

test page http://nosetothepage.org/pseudoImgLnk.html

wd: can't inject aria into dom thru css
... can't change role or class. you can add css parameters. but can't add css parameters to css
... for icon-fonts - if author fails to add role=image nothing user can do to fix it

<JohnRochford> This is the link Wayne provided today.: http://nosetothepage.org/fullPseudoTest.html

wd: User can replace generated content [ ] with other content using Stylus
... Example 2, if you use browser find, to look for the word "Fact", the browser won't find it.
... Example 3, work with a screen reader, used visually hidden generated content.

jim: disappearing icons when changing fonts?

jon: replace fonts with arial, try to skip changing <i>

http://nosetothepage.org/fullPseudoTest.html

<jon_avila> * { font-family:arial !important; }

jon: need more specificity in the technique, to tease out which styles work and which don't.
... see icon fonts * for required fields etc

jr: icon fonts for cognitive issues to make content easier to understand.

wd: I use icon fonts for my own purposes as assistive technology.

jon: I too use icon fonts in a favelet to help with testing etc.

<JohnRochford> Example of using icon fonts to help people understand content: https://disabilityinfo.org/records/index/?search=61789

jon: important to note that <img> and <input> don't support generated content, there may be others

wd: Generated content. How to use generated content accessibly. with caveats/constraints from WCAG
... generated content has no semantics and you can't find it.

test page https://rawgit.com/allanj-uaag/wcag21/example-reflow-url/example-reflow-url.html

jim: looks ok in FF, not so good in chrome, and worst in Edge

jr: in IE the long url pushed the aside to the bottom of the page

wd: safari looks like chrome

jon: different resolutions and browser width also compound the view

jim: please review the technique for content.

jr: perhaps an advisory at the top of the example about different browsers and resolutions.

open item 4

jon: concerned about HCM or ignore colors in IE, don't have a total handle on what works and where.
... need a test page to use across browser. Need a list of what changes and what doesn't in HCM.

wd: when I get to a page with lots of controls I turn off my color style sheet to make sure I can see everything.

jon: SC not text contrast. concern about outline and using other more complex methods. would be good to write a technique so if you turn off or make outline transparent.

jim: there are many issues around color, may come up in silver
... HCM issues different instances per browser.

jon: no setting in chrome extension. it is just a filter. user has little control.
... mac has increase contrast mode. changes control borders and other fine controls, but not replacing colors. doesn't solve all of the issues.
... doesn't provide all of the control that Windows HCM
... HCM can control text colors and other things.

open item 1

2nd para - For people with low vision, enlarged text with reflow enables reading. It is critical. Enlargement enables perception of characters. Reflow enables tracking. Tracking is following along lines of text, including getting from the end of one line to the beginning of the next line.

jon: it makes sense. think this is ok

<JohnRochford> I bow to Jim's lexical prowess. He, not I, pronounces "illustrative" correctly.

jr: on the cognitive side. large text improves comprehension.

trackbot, end meeting

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.152 (CVS log)
$Date: 2018/08/09 16:04:22 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.152  of Date: 2017/02/06 11:04:15  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Default Present: jon_avila, Laura, Jim, Jason, Shawn, Wayne
Present: jon_avila Laura Jim Jason Shawn Wayne
Regrets: Laura Jason
No ScribeNick specified.  Guessing ScribeNick: AllanJ
Found Scribe: Jim

WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Found Date: 09 Aug 2018
People with action items: 

WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)


[End of scribe.perl diagnostic output]