See also: IRC log
<scribe> scribe: janina
jb: Any agenda additions?
... Noting several folks unavailable for meeting today
jb: Introducing discussion of W3C
reorganization aimed at being more responsive to web
development today
... Now to be organized by function
... e.g. project management for spec development
... architecture for how the pieces fit together
... strategy for where we need to go
... This takes away the old familiar domain structure
... Notes that WAI was an Initiative before it was a
Domain
... The hope is to get even better a11y integration
... However, details are still evolving
<Judy> https://www.w3.org/2016/08/2016-reorg.html
jb: Expected effective date is
late September -- post TPAC
... Available to discuss with anyone concerned about these
changes
<Judy> [jb: there was an omission, that will be addressed]
jb: Notes also an omission in the announcement doc, which will be corrected
<Judy> here is the missing bit that will be added to the reorg doc:
<Judy> The Web Accessibility Initiative is a long-time publicly visible brand of W3C, and will be kept as a brand and as an Initiative. However, whereas in the past the work was mostly managed by a single Domain, accessibility work is now distributed across the new functions (primarily Strategy, Project and Architecture & Technology) supported by the WAI specialists and Principal Investigators on external funding.
jb: Notes the above doc is
public
... Yes, message went to AC + Chairs, but the doc itself is
public and can be shared
... Any questions?
kathy: How does this affect existing work efforts?
jb: Work will continue as is.
Some background shifting, i.e. moved under different
management
... Management will be mostly focused on testing, publications,
meeting milestones, etc.
... i.e. very production oriented
... Michael would still be the staff contact for his current
groups.
<Zakim> Joshue, you wanted to ask if this management change will have any impact on charter creation processes
josh: Concerned about charter impact, esp the creation of new/updated charters
jb: Yes
... Noting there different types of charter provisions,
adding/deleting deliverables, redefining scope, or new work, or
simply extending an existing charter
... So above can cross production, strategy, as well as
a11y
... Wants to reassure that I have been cross-checking this on
existing charter work, even though I wasn't able to discuss
this up front
... So, now I can report there are others in the loop, but I'm
not out of the loop in any case
... Asking whether WCAG discussed in meeting?
josh: Yes, it will have some impact on charter development, and have some feedback
jb: Want to reassure that I'm still very involved, though my new title is not yet determined
josh: Might plh start to come on calls?
jb: Probably not, unless there's
a specific reason. Will moe likely interface with
Michael.
... Any other questions for now?
... Wants also to note this call continues, though changes are
possible, e.g. frequency of calls
brent: EOG will not have official
F2F at TPAC because only 4 of us will be there
... Rather, we want to focus on outreach and to meet with other
WAI groups to better understand how we can help with their
work
... We are trying to establish a schedule in advance for those
discussions
jb: Are you getting responses?
brent: We've reached out to WCAG, and also with ARIA
josh: Looking forward to our
joint conversation ...
... Hope that eog can help even with some of our doc
creation
jb: Suggest it's best to be
specific in cross meeting requests as many groups are tightly
scheduled
... Suggest specific agenda and several suggested times
jb: Notes that a11y testing now
in WCAG ...
... Anyone have date on this?
... OK, will determine and forward to list
... OK, it's Thursday 22 September
ts: Same day as dpub mtg, but should be able to share a few folks for part of the day
jb: Important to communicate with Wilco so he doesn't drop the room thinking no one is coming
<Ryladog> Yes, it did
<Joshue108> JS: Discussion was started in WAI-IG.
<Joshue108> JS: There are threads in WAI-IG and APA.
<Ryladog> am recording the inpu tuse cases
<Joshue108> JS: Trying to capture that so you can see them on archive.
<Joshue108> JS: We took the MAUR and stripped them back.
<Joshue108> JS: We were reviewing APIs that came out of IG. We are figuring out what we want to say.
<Ryladog> There are some use cases in the Web Payments Use Cases document and modify for userswithdisabilities
<Joshue108> JS: We should like an a11y impact statement etc.
<Joshue108> JS: Suggestions around UI and API implementation etc.
<Joshue108> JS: Still details to be worked out.
<Ryladog> yes
<Ryladog> Also, There are some use cases in the Web Payments Use Cases document and modify for users with disabilities
jb: Is there seeding discussion in WAI IG?
janina: Yes, Katie lead it and it's been helpful
<Joshue108> https://www.w3.org/2016/08/draft-wcag-charter
josh: Have had group feedback to
be addressed
... We will need to take that up and make appropriate
changes
... we want to make sure we do the background requirements work
for any future WCAG spec
... This now includes UAAG and ATAG maintanance
... Also have input coming from COGA, Mobile, and Low-Vision
work
jb: Encourage looking at this
from the perspective of keeping people engaged
... e.g. want to make sure our ongoing Mobile work has
sufficient visibility
ja: Wondering whether issues arising of folding in UAAG and ATAG needs to be specifically called out in the charter somehow
josh: Obviously this is important, but how to address is unclear now
jb: Believe the maintanance work
needs to be clear
... But also the evolving scope
josh: We still don't know the mechanics of maintaining UAAG and ATAG
jb: Please call that out, it needs to be stated
<Ryladog> Just to say that we should be looking for the impacts of ATAG and UAAG for the IoT/WoT tools and content
djosh: Concerned of the mechanics of doing the work
jb: Expect there will be staff support, but this is the stage to name the work
josh: OK, but don't understand how to articulate it
jb: It's in scope because of future WCAG reqs
josh: Hope we can keep this preliminary for the current charter, i.e. reqs
jb: Are you concerned that there's a lot to do?
josh: Unsure
jb: No, not a point release of UAAG or ATAG, just errata level things
<Ryladog> What about? Just to say that we should be looking for the impacts of ATAG and UAAG for the IoT/WoT tools and content?
josh: That's helpful!
<Ryladog> I can hear
<Ryladog> ok
jb: Perhaps we do need to revisit
this charter work ...
... It's important to get scope right, and to avoid surprises
in charters
jb: WCAG reviewed and approved
jb; Hope this helps draw more workers in
jb: Have heard there's some kind
of problem?
... Raising it now to ask whether there are specific issues of
concern?
... Is APA aware?
janina: Noting APA Payment sscheduled to meet Thursday morning, so will get clarifications there
<Judy> judy: Can APA just close it?
<Judy> janina: if there was a cfc on longdesc, apa should have been advised.
jb: Suggest we need to say more
on closing HTML-A11y TF, noting it's not yet closed
... Perhaps some dependencies being missed, and we need to
resolve gaps
jb: Want to know which discussions are most useful? And, want to know about meeting fequency, optimizing that.
<Brent> +1 to as is. This is a learning experience for me.
janina: I find current level good
<Ryladog> +1 I am for keeping it
tzviya: Also me
<Judy> [JS: particularly b/c of pace of activity, to stay on top of this, avoid dropping things]
tzviya: Our model might be helpful for I18N and other horizaontol review groups
<Brent> I will not be available
<Ryladog> I will be
jb: Who is available for 31 August?
<Judy> Availability for August 31?
janina: Probably
<Brent> -1
janina +0.75
<tzviya> +1
<Ryladog> +1
<Kim> .75
<Judy> +.75
This is scribe.perl Revision: 1.144 of Date: 2015/11/17 08:39:34 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Succeeded: s/ommission/omission/ Succeeded: s/Yes/Yes, it will have some impact on charter development/ Succeeded: s/Tuesday/Thursday/ No ScribeNick specified. Guessing ScribeNick: janina_ Found Scribe: janina Default Present: Tzviya, fesch, allanj, George_Kerscher, MichaelC, Kathy, Katie_Haritos-Shea, Kim, Judy, Jim, Jinina, Janina, Brent, Joshue108 Present: Tzviya fesch allanj George_Kerscher MichaelC Kathy Katie_Haritos-Shea Kim Judy Jim Jinina Janina Brent Joshue108 WARNING: No meeting title found! You should specify the meeting title like this: <dbooth> Meeting: Weekly Baking Club Meeting WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth Got date from IRC log name: 17 Aug 2016 Guessing minutes URL: http://www.w3.org/2016/08/17-waicc-minutes.html People with action items: WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]