<jon_avila_> trackbot, start meeting
<trackbot> Meeting: Low Vision Accessibility Task Force Teleconference
<trackbot> Date: 03 March 2022
<laura> Scribe: Laura
Jon: Exploring a Low Vision
Accessibility Community Group.
... we would still meet and use GitHub.
... AG would need to review work same as now.
... hopefully would have more involvement.
Laura: we need more people.
Shawn: CGs don't get a staff
member
... have the same time. Would need another wiki.
... keep the current wiki.
... could use GitHub.
Jon: there is a wiki on GH
shawn: GH wiki doesn't have an auto toc.
Jon: have discussed with AG chairs.
shawn: no one has to approve CGs
<Sam> yes CG to get more contributions
Laura: +1 to CG
shawn: 5 people need to support a CG
<jon_avila_> I am good with moving bulk of work into community group
(Discussing name for cg)
<shawn> Low Vision Accessibility Community Group or Low Vision Community Group
Shawn: Low Vision Accessibility Community Group or Low Vision Community Group
jon: I sent around 5 GH related
issues
... questions on how to interpret SCs.
... need to button up some issues.
... 1st one related to skeleton.
Sam: don't have a preference.
shawn: need some indication.
jon: it is a current style right
now.
... need to be an activity indicator.
... do we want to show support as a group?
Shawn: it is what we think now.
RESOLUTION: Task force agrees that some indication of page/content loading needs to have sufficient contrast but the skeleton itself does not need to
shawn: can put a link to resolution into GH.
<shawn> scan put text and a link to resolution/can put text and a link to resolution
Jon: what if you have a label
inside input field?
... if label is inside or outside it doesn't make a
difference.
... google decided borders aren't needed.
... fatigue or time was not considered.
Sam: hard to tell without a visual example.
(Jon shares screen)
Jon: common technique.
... font size is small on the labels.
Shawn: user hat on.
... poses great difficulty for me.
... this is an issue.
Sam: would reject it on the text size.
shawn: several examples of how inaccessible it is,
Jon: min text size could be a supplemental guidance topic.
Sam: is there a live example?
jon: looking around for example.
Sam: need some real life
examples.
... can look at it offline.
Jon: we can create an example too.
jon: this one is also related to
1.4.11.
... How to compare adjacent colors.
... doesn't say adjacent to the component.
... walking though the examples.
Sam: is there a thickness requirement?
jon: based on area.
... (explains criteria for 2.1)
Sam: reject the entire lot if no
thickness requirement.
... for large features it's the contrast that matters.
... for small details size matters.
... Andy has looked into this.
Jon: this is important for 3.0.
Sam: test with gaussian
blur.
... it is not fit for purpose as is.
Jon: trying to do the best we can
for what we have.
... could do supplemental guidance.
sam: border thickness is the key
Jon: user agent exception for 2.2.
shawn: supplemental guidance is
in our control.
... is a fairly straightforward blur test for supplemental
guidance?
<Zakim> shawn, you wanted to ask Sam if blur test is a fairly straightforward supplemental guidance?
Sam: possibility.
... I'll think about it.
... are we talking about hover and focus?
Jon: for supplemental guidance could cover both.
Sam: 4 possible states.
jon: many states.
... colors against colors is difficult.
Sam: 4 possible states needs to
be determined and distinguishable.
... interested in the topic.
<shawn> scribe: Shawn
Jon: Please look at other items, and if you are interested , pleae comment on GitHUb
[ Jon desribes issue ]
Sam: Makse sense to me.
Jon: reflow size ... similiar to
older mobile devices
... is it OK to have horizontally scrolling content, as long as
doesn't require scroilling in 2 dimensions
Sam: Not sure. I've seen this, e.g., for menus and shopping. On touch screen, it kinda works OK. NOt sure about accessibility perspective.
Jon: Could introduce an indicator that more content is availble yet you need to scroll. NOt sure if fits into crteria.
Sam: A signfifier
... what is reasonable? how set boundaries?
Jon: if you have to use the two
things at once is a challenge
... limitations of small screen
Sam: e.g., a table that just didn't fit
Jon: OK for tables if cell not re1quire scrolling both ways
Sam: option to turn it off
<Sam> Proposed topics are Sam hover versus non-hover active versus inactive selected versus not selected for buttons and controls and radio buttons
Sam: add to the supplmentasl guidance list new topic of distinguishing hover focus active selected etc. for controls - add Sam's name
This is scribe.perl Revision VERSION of 2020-12-31 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00) Succeeded: s/LVTF community group/Low Vision Accessibility Community Group/ Succeeded: s/an auto tic/an auto toc/ Succeeded: s/can put a link to resolution/can put text and a link to resolution/ Succeeded: s/able/label/ Succeeded: s/ fo supplemental/ for supplemental/ Present: Shawn, jon_avila, Sam, Laura Found Scribe: Laura Inferring ScribeNick: laura Found Scribe: Shawn Inferring ScribeNick: shawn Scribes: Laura, Shawn ScribeNicks: laura, shawn Found Date: 03 Mar 2022 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]