Meeting minutes
Introductions (Jon ~10 mins)
JonA: Speaks to agenda items, introductions.
JonA: If you need accommodations, please let us know, happy to help.
JonA: The LVTF is part of Accessibility Guideline Working Group. I've been in space for about 20 years.
<shawn> ChrisL: Recentrly working in Silver on visual contrast of text. Work at Oracle.
ShawnH: I've been on staff for W3C for 18 years. I mostly work in Education and Outreach and have personal interest in Low Vision.
BruceB: I work at the Access Board, we develop the regulations around Accessibility. I've been in the area for 30 years. I've been following the work of the accessibility guidelines through 1.0 through to current WCAG. I helped develop contrast on WCAG 2.0.
AndrewS: I came across work within contrast and visual perception. Concentrate on readability. I came up with algorithms and a tool that is significantly different than current WCAG tools.
… Originally based on Silver , but working on next version as well. Open to comments and improvements.
JonA: WCAG 3.0 is code named Silver internally to W3C
KimB: I'm new to 508 space, I work at USDL , worked in disability rights space for many years. Low Vision , Colorblind . I've worked in cross disability spaces , housing etc.
<AndySomers> The SAPC technology demonstrator https://
<AndySomers> Click on "Research mode" for interactive experiments
BhoomikaB: I also am new to the group and tech space. Background is in research and social science. Received PhD in travel issues for visually impaired. Pivoting to UX field and Accessibility space.
AmeenahG: I am not new to 508, I'm with Dept of Defense , cybersecurity area. Implementing 508 in area creates fun challenges to resolve. I'm totally Blind. I am hoping to help the user experience for the war fighter and increase accessibility for those users.
… been around area for 20 years. Been program manager for 4 years.
ShawnH: We are working on that on Education Outreach and would love to help with that topic.
SamW: University of Cambridge, 13 years in design. Measure user's vision ability and how that relates to products . Takes into consideration how it would impact population. Interested in WCAG 3. and visual clear iconography , then move into text on spacing, type face, etc. I'm interested in the segments of vision, aging, normal range, low vision, etc.
… I'm interested slicing the low vision segments and categories.
AndyS: Talked to in Laws, etc.
KimB: It depends in context of use, per user too. I.e. legally Blind vs. what actually is.
AndyS: talks to 20 two hundred baseline for legally Blind.
ShawnH: We have a place for the level of vision category within EO (Education Outreach).
LauraC: I've been in accessibility space in 20 years. Started in W3C with HTML5 spec. I've been in WCAG working group.
LauraC: I'm a original member of LVTF.
Cammie: I am 508 at Health and Human Services. I wear many different hats, training, testing, etc. I've worked with Jon before. I am interested in the group and efforts and topics. I've been working with electronic baseline documents , document accessibility is my concentration.
Work modes (Jon ~15 mins)
JonA: Talks to work modes. We have a wiki, we have a GitHub issue tracker. We have ability to use surveys for group to respond to.
https://
The main wiki is https://
Expectation is around 4 hours of total work within a week commitment wise to the efforts of Low Vision Task Force (LVTF)
<laura> https://
JonA: Talks to scribe list. We'd like to have people sign up before the meeting, if at all possible.
JonA: We don't want people to have to scribe every week, so if we could alternate that would be great. Minutes would be documented by scribing.
<jon_avila> group-lvtf-plan@w3.org
JonA: to email us as facilitators, please use group-lvtf-plan@w3.org to reach Shawn and Jon and Chris
AmeenahG: Do you see me as a fit in the group?
JonA: It is not about a disability it is about your interest in to contribute to the group , in a variety of ways.
AmeenahG: I want to capture the DoD space's demographics and help impact the users within our group through these efforts.
JonA: We are going to go over previous work and current work and you can make the determination.
BruceB: To my colleagues , I wanted to introduce the 508 group as this task force was starting up again.
AndyS: On topic of what is low vision, can we talk to this now or later?
JonA: Later as an agenda item of a future meeting.
BruceB: For work modes, are we under AGWG or Silver.
JonA: Should be within AGWG and within LVTF moving forward.
AndyS: On work modes, LVTF , W3C working and liaisons, talks to CSS color and accessibility. Do we cross communicate ?
<bruce_bailey> is this the email address we will be using ???
<bruce_bailey> public-low-vision-a11y-tf@w3.org
ShawnL: APA working group is chartered to coordinate with those type issues.
JonA: AGWG , Accessibility Guideline Working Group tried to set up things where we are aware of cross communications.
APA: Accessible Platform Architecture
public-low-vision-a11y-tf@w3.org is for communication within the group that is not GitHub based
Past work overview (Chris ~10 mins)
<ChrisLoiselle> https://
Chris: Past work link posted - we have editors draft of Accessibility Requirements for people with low vision. Lok at past work and determine if there is anything additional in our new work. Look at this as an overview and where we are from the publication in July 2019 and potentially update the publication of this.
Chris: This is one of the documents we want to review in terms of past work and incorporate into WCAG 2.x. People call could review this. Good to review for baseline for next call. Progression of visual impairments and what those are. It covers functional vision and we could expand that section. It also goes into specific user needs which maps back to WCAG 3.0 work.
Chris: WCAG 3.0 guides are more user based.
<shawn> JonA: in WCAG 2.1 , got some new SCs that were from these user needs
<shawn> ... additional gaps that we couldn't address in WCAG 2 - which is where we are now
andy: made some comments on the doc on github and we need to upatte something like figure 10. It says it has high contrast but has low contrast letters. Some technical things to examin.
Andy: There is also some newer research.
<ChrisLoiselle> https://
<laura> https://
<shawn> What's New in WCAG 2.2 Working Draft https://
Bhoomika: Could we have access to what was proposed.
Current work options (Chris ~15 mins)
<jon_avila> Supplemental guidance list on the wiki https://
Jon: looking at some guidence topics that have been suggest
<jon_avila> COGA example: https://
Jon: cognitive work also overlaps
[see links]
… focus is on user needs, what helps
… one of the limitations with WCAG2 approach is need for requirements that work everywhere for all technologys
… supplementary guidence could have more flexibility
… provides valueable guidence and information but wouldn't be picked up by regulators
… things like sticky headers
… we need ability to provide authoritative but supplemental guidence
… linked resources are not necessariliy finished, more like topics that might be addressed
<AndySomers> Visual Contrast Notes and Resources on our Wiki https://
Shawn: WAI and EO working on some additional guidence
… will fit and match look-and-feel of other material posted on WAI site
… but draws from the recommendations from this group and others
Jon: Another goal is be considering if there is feedback from this group that might inform 3.0
… there is an onging effort to migrate requirments from 2.x format to 3 -- and this group can help with that.
<jon_avila> https://
Jon: Also there is older LVTF recommedations that this group should review and that we might want to update.
… and there are some long-standing questions that have not been addressed
… for example adding 200% mag to text that is already large is counter productive -- but WCAG 2x does not account for that
KimB: Best experience for me is text and a standard size -- yet so many well meaning sites do not do that
Jon: Yes, so we have a list of topics
… some may be lower priority
<shawn> Accessibility Requirements for People with Low Vision https://
<jon_avila> https://
<shawn> [ Shawn has to drop to take call from hosptial ]
Andy share doc
… question where to share some notes from email
[discussion if github or wiki]
Andy: my notes include fonts size and useability
… as you zoom text up, you get to a point where further magnification makes things worse
… the way browsers zoom is by percentage, but want a user want is magnify smalles text up to say 80 px -- while keeping larges text clamped to 120 px
… but this is a UA thing , so it makes we might not be able to address the user need in author-oriented content requirement
… but this group could at least document the need
Jon: I think this group can at least keep all of this issues on our plate
… might not fit for 2.3 but might be 3 or might revisit UAAG bue we can also work in cross discipline groups
[Jon and Shawn discuss wiki/github locations]
<jon_avila> Supplemental guidance page: https://
<shawn> https://
Chris: on GigHub we have issue tracker, which might work well for buckets
… triaging off the milestones might work better than the wiki
<ChrisLoiselle> For new or current issues We have 5 milestones, https://
Jon: We also heard topics and suggestions for possible future agenda topics
Shawn: wiki has planning page , so that might help
<Zakim> shawn, you wanted to say tangent for now. and UAAG -> WCAG 3 (and maybe supplemental guidance)
Shawn: Laura will remember the old organization , but Jon and I think we need to start pretty much fress for this group
… I will also remind folks that the old UAAG 2.0 never was finalized because the browsers providers were not comfortable with that activity.
Next steps (Chris ~5 mins)
Shawn: Our expectation is that there is some room for that in what 3.0 covers.
Jon: This group should have some conversations about what work we prioitize.
… next meeing in a couple weeks. I think supplemental guidence should be our first task and a high priority.
Andy: Agree with supplemental guidence as good first task.
Sam: It is a huge red flag for me that 2x has no minimum font size requiremet. Really do not want to wait ten years for that.
… Also I am concern for current contrast ratio. My near term priority would be min font size and better contrast requirement for 2.3.
Andy: My conversation with designer is that they are eager for better and more flexible guidence like the SAPC.
… have been working on a new version that might fit 2.3 approach
Jon: I am hearing some people advocate for a couple things in 2.3.
… I think HHS has min px size requirement they add to HHS.
Jon: When I started, I was advised that it was too big a paradigm shift for 2x, so focus on 3. I woud be glad to have something sooner.
Shawn: The supplemental guidence would be a way to get this sort of information out there now.
<Zakim> shawn, you wanted to say supplemental guidance can turn into WCAG 2.3 &/or WCAG 3
Jon: i think it has been a productive meeting, look for follow-up email and next steps
… new folks take a look at the current materials
<ChrisLoiselle> https://