<Judy> scribe: George
<Judy> meeting: WAI Coordination Call
<Judy> JB: Checking availability Oct 23? Regrets?
JB: Next meeting October 23.
<Judy> NEXT MEETING OCT 23
<Kim_patch> Kim_patch+
GK: PWG haaving spec go to CR in the near future. Will get APA review soon.
<Judy> GK: the name of the spec is Web Publications.
GK: Web Publications
JS: CFC are now out.
James: ARIA 1. coming out in about two weeks.
No opportunity to get an early draft out.
<Judy> JB: Can we get early eyes on draft messaging?
Sean: The wording in the abstract and the status of the document are used in the announcements. JB and Shawn should review in advance.
JB: great to get the abstract to us sooner rather than later.
Stevve: COGA we have a note out with information on policy. We are also design guides to makeinformation more accessible to the COGA community.
WCAT 2.2 success critera is also getting attention.
Good ideas coming out of the group.
JB: question 1, are you getting feedback from the reviews that started recently?
What is the best way to integrate that work?
Steve: The content usable note was published, but there were quality issues. It needs to be better before we can expect to get comments.
We can springle COGA content around; we don't want it to be in a silo.
JB: we need to have people looking at it.
What are the integratation challanges you are facing?
JIM: COGA has been leading the way and we are following, and the overlap between issues between COGA or low vision.
<shawn> +1 to Jim that there is a lot of overlap between COGA & low vision (& mobile)
We are working on issues and we find people are loosing their place and then they are wondering what they were working on. So COGA issues are present in many arenas.
Usability studies show that screen readers finish faster than low vision. The low vision people have higher cognative load.
Shawn: with my many hats, all are agreeing with the COGA issues.
What is needed is integration. We do not want separate resources; they all need to be integrated into a single item.
Kim: I agree with Jim and Shawn.
I also want to mention that it is a moving target. What is in practice today.
Show and tell may be useful to help the groups.
Real world examples where COGA issues are helpful in many arenas.
Here is the problem and here is thee solution.
JB: This makes sense. we need to make sure we have the rights paths to move forward.
Is there a layer where EO can build this in to their materials?
<shawn> some thoughts "Beyond WCAG – Guidance for Web/Digital Content Accessibility #132" https://github.com/w3c/wai-website/issues/132
Are there implications for what you are doing also in APA or ARIA?.
Steve: Perhaps the WG should provide a semi-formal mechanism to make sure it happens. Show and tell may be a good way forward.
You cannot be in silos. now with personalization, this may be easier to accomplish.
<Judy> scribe: Judy
George: When we design the
publishing things we focus on making it easy and
straightforward for how to consume publications
... we pay attention to that in reading applications -- if it
is too complicated, they won't get it
<JimA> +100 to george on cognitive load for screen reader users
George: also want to comment that even while screen reader users may comprehend faster than low vision users, the cognitive load for screen reader users is also huge
Steve: yes cognitive load is major consideration
<George> You cannot be in silos. now with personalization, this may be easier to accomplish.
George: cognitive semantics really help on undersatnding what you're looking at
<scribe> scribe: George
Shawn: We would love to take on more work.
JB: there may be a relevant filter that we could add that would help.
Steve: The implicit understanding i think it can be in WCAG. JB: not sure we can add this to that now. there are open questions. Your question will not be lost.
<JimA> task force integration takes a lot of time - knowledge sharing is relatively easy, concept building and (deep) understanding is the time consumer. then there is the merging of concepts/understanding -- (thinking out loud in text)
JB: Looking for what we should be capturing on how the meetings went.
Are there follow up topics we need to address.
James: We tried to get remote working and could not.
JB: Had I known, I would have
tried to get it resolved. Feel free to esclate quickly to me
and others.
... we want good remote support.
... Get the message to us asap.
Steve: The equipment should be there and tested in advance.
JB: I want to know when ther is something going wrong, even if one assumes that it's a hardware problem. I hear the message that the equipment and connections should have been pre-checked..
CL: GK: Zoom was wonderful at
TPAC.
... back, I dialed in, more problems with Webx.
... Break outs on Wednesday were well done.
suggestions from previous years were implemented.
We had some audio problems. One day it is failing and the next day it worked.
When we were able to demo, the folks were able to implement in a few days.
That example of a demo and people getting it was great.
JB: please provide feedback on the TPAC feedback form. It is better if it comes in directly from you. I can talk, but when it comes from you, it is better.
Other TPAC comments?
JS: many topics to consider. The one is that we are not asking for enough from technology.
We should be asking for supprt that we are putting in to best practices.
<JimA> +1 two color focus ring (css)
One example is the spacking between words, lines, etc. You need an advanced degree in CSS to do that, but it must be in reach of the common person.
<Zakim> Judy, you wanted to ask anyone with remote connectivity problems during TPAC to please comment on the feedback form in detail
Example is how devices change with different light. We need this same thing for accessibility.
<Judy_> agenda order: 6, 4
<Judy_> agenda order is 6, 4
JB: fighting with the automatic agenda thingie.
<JimA> on the other side, browsers could make it easier for users. Spacing - authors can make a responsive site. Browser allow setting size of text - why cant they add settings for spacing metrics that apply to all sites. all rendering of native (default browser styling) html elements should meet WCAG by default.
Charter update.
36 were received.
Several were formal objections, but it did not come accross that way. THe publishing issue should be easy to address.
Particularly Silver may need to go somewhat beyond the traditional web. Getting push back about scope being too broad.
<CharlesL> +1 to George's comment on addition to Publishing to that charter!
<JimA> regrets for next meeting
This is scribe.perl Revision: 1.154 of Date: 2018/09/25 16:35:56 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/Jamie/James/ Succeeded: s/Sean/Shawn/ Succeeded: s/what you are doing/what you are doing also in APA or ARIA?/ Succeeded: s/q+Shawn/Shawn/ Succeeded: s/going wrong/going wrong, even if one assumes that it's a hardware problem. I hear the message that the equipment and connections should have been pre-checked./ Succeeded: s/WCAG 2.2 and Sliver goes beyonnd/Particularly Silver may need to go somewhat beyond/ Succeeded: s/mext/next/ Succeeded: s/Push back/Getting push back/ WARNING: Replacing previous Present list. (Old list: Joanmarie_Diggs, janina, Sharron, CharlesL, George, Katie_Haritos-Shea, Rachael, stevelee, Judy, Shawn, James, Brent, jamesn, Kim_patch) Use 'Present+ ... ' if you meant to add people without replacing the list, such as: <dbooth> Present+ Shawn, Judy, Brent, Joanmarie_Diggs, janina, James, Kim, Steve, Kim_patch WARNING: Replacing previous Present list. (Old list: Shawn, Judy, Brent, Joanmarie_Diggs, janina, James, Kim, Steve, Kim_patch) Use 'Present+ ... ' if you meant to add people without replacing the list, such as: <dbooth> Present+ Shawn, Judy, Brent, Joanmarie_Diggs, janina, James, George, Steve, Kim_patch Present: Shawn Judy Brent Joanmarie_Diggs janina James George Steve Kim_patch Jim CharlesL Found Scribe: George Inferring ScribeNick: George Found Scribe: Judy Inferring ScribeNick: Judy Found Scribe: George Inferring ScribeNick: George Scribes: George, Judy ScribeNicks: George, Judy Found Date: 09 Oct 2019 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]