<scribe> scribe: Rachael
Judy: We will keep the same
rotation as we cross the New Year. We have a bunch of holiday's
coming up. Two weeks out from January 1st is January 15th. Is
there a critical mass of regrets for that?
... if not, then we will assume January 15th is our next
meeting. Any regrets?
... That will be the next one.
<Matt_King> hi, I can't find the meeting id for dial in
Judy: Michael has one that will be happening. Shawn, you will be getting text after the fact.
Michael: I'm publishing WAI-ARIA
1.2 and WAI-ARIA Practices 1.2
... I will send a draft to the list. I am not going to spend a
lot of time on it. It is a wide review draft so will be
automatically sent to a number of channels.
Judy: It will include some plain language content.
Shawn: When?
Michael: If I'm lucky within 20 minutes.
Shawn: When are you trying to get the announcements out?
Michael: Before end of they day Friday.
<shawn> Shawn adds to https://www.w3.org/wiki/WAI/announcements#Upcoming_Announcements_.3C-_add_yours and reminds Michael of ...
Judy: Can you two coordinate with each other.
<shawn> https://www.w3.org/WAI/cc/wiki/WAI_Announcement_Drafts
Judy: the meeting id is there. Can someone share the password but comment it out?
Shawn: To clarify it shows the substitutions but not the comments.
Judy: If it does, we'll change the password.
Tzviya: I owe Shawn an announcement.
Shawn: I put the information about where to put draft announcements up.
Judy: Any other document
publications coming up?
... I want to bring awareness to the new web accessibility
course. If anyone can, publicize that. Maybe in your
orgnization or that you know. Aligns with curriculum.
Highlights different presenters.
<shawn> W3Cx course email <https://lists.w3.org/Archives/Public/public-wai-announce/2019OctDec/0003.html> BLOG <https://www.w3.org/blog/2019/12/free-online-course-introduction-to-web-accessibility/> (both link to description)
Judy: may be a useful resource for anyone in your field. Anything else on announcements or publications?
Judy: A few months ago, the W3C
announced a workshop on inclusive design for inclusive well.
Went well. Lot of accessibility focus. New workshop just
approved to go forward by management of W3C
... its not circulatable yet. Its on the web and machine
learning. That will be held in late March in Berlin.
... 24/25 March. It will have some accessibility focus. A bunch
of us have been waiting for this. If you or people are
interested, get it on the calendars. It would be great to have
people who know the accessibility field going, putting in
statements, or papers
... Is it useful for me to put in the link?
... I'll hold it till its a bit more cleaned up.
Judy: I'd like to welcome Matt to the call. Did you make it in?
Matt: Yes.
Judy: You wanted to talk about converting a note format to a resource section. Can you talk us through some background on that?
Matt_King: The ARIA authoring
practices has been a note for a few years now and has become a
widely used resource. But we've received a lot of feedback
regarding its usability
... we also have a problem with people finding our older
versions through search.
... the note itself is a single document but the most prominent
feature is Section 3 Design Patterns. Every one of those design
patterns has a set of examples. There are 63 of them on a
subdirectory on webpages. They are working functioning code
that illustrate design patterns.
... every time we publish the note, there is a new version of
the examples. These three problems (usability, information
architecture, and republishing content) are drivers for
surveying content and audience.
... I am also chairing the community group with the goal of
publishing Can I Use tables for all 63 examples. The initial
pilot (aim to be done by June) will be desktop screenreaders
only
<Judy> meeting: WAI Coordination Call, 20191218
Matt_King: 6 different
screenreader and browser combinations. Currently you go the
example itself; the documentation; a table for roles; states
properties, etc; the source code for the example.
... what we will be a adding is a table that will include
support information. Not sure exactly what that will look like
but it will get aggregated into a single number or 2-3
numbers.
... The main question is could we solve high level problems and
support upcoming integrations by hosting the authoring
practices within the website as a section of the website with
its own navigation and architecture? I don't want to make
content changes.
<jamesn> +1 to all of this
I think this will open the door to serve multiple audiences and needs. Start consolidating some of the accessibility resources. Just being able to authoring practices that is user friendly and solves versioning problems.
Judy: Thank you for bringing a great question to the group
<Zakim> shawn, you wanted to say yes (and relates to broader work on WCAG support materials and potentially "supplemental guidance")
<tzviya> +1 - this sounds amazing
Shawn: The short answer is yes. We have been thinking about doing a better job of presenting other support materials through the site such as understanding WCAG and the work COGA is doing. If you can clone two of me, I can start in January.
Matt_King: We have some issues to
address relating to aria versions. This will help with
that.
... We are working on a vendor on a related project and they
may be a vendor we could work with on this.
... My hope is to tackle the problem of making this happen
efficiently by bringing people on full time to do it.
Judy: Thank you for the work effort you are doing on that.
Shawn: That is excellent that you
have those people. Please keep me in the loop on the design,
architecture, interface, etc so we can address consistency. I
can share what we've done and where we are moving. We need to
be looking more broadly at how we are doing all this.
... I will make time to help coordinate the effort so what we
are doing works throughout.
Judy: I want to check in for a moment. Jeanne is expressing interest for Silver. James was +1. Any comments to coordinate discussions as follow on to this meeting?
Jeanne: I would like to talk to you, Matt, about Silver plans and make sure we are going in the same direction.
Matt: One of the things I would
like to tackle longer term but may involve charter adjustment.
I think we should have more coordination if not consolidation
amongst resources.
... I think one of the things I'd like to talk about in the
near term, planning in 2020 for 2021, is scope. Working on ARIA
coverage. We still have a backlog. Hoping to close backlog next
year. Its more like 2021 before we can consider merging scopes
between ENO and ARIA
... I think Silver cross referencing would be valuable. Its how
we go about it. Does that make sense?
<Zakim> shawn, you wanted to mention EOWG rechartering in 2020 - drafting in Q1 and to say have done coordinated work in past, e.g., WCAG quickref
Jeanne: Yes, that is why I'd like to talk to you mor eabout it.
Shawn: EOWG (Education Outreach
Working Group) will be rechartering next year. So lets make
sure we have what we need in the charter.
... We've successfully coordinated with the AG working group on
the quick ref. I think we can do formal coordination like a
task force or just the two groups working together. We'll make
sure its in the next charter.
Matt_King: How would you like to do that?
Shawn: We will probably ask you to join the planning call with the chairs. We can discuss.
Judy: This is great to be thinking forward and exchanging info.
<CharlesL> Love all this Matt, the DIAGRAM Center's code repository does link to a lot of these ARIA Authoring best practice examples. https://benetech.github.io/Accessible-Interactives/
CharlesL: The diagram center has an accessible code repository that was linking to some of Jon Gunderson's examples but now we link to the code repository. We will point to wherever this goes. Great work.
Judy: Any comments from anyone else? Any concerns?
Matt_King: My only outstanding question is for the aria and at project, we will need some hosting capabilities to serve that. Figuring out how that will work is something we should get on. How do we plan this?
Judy: I think that's Michael.
Michael: I was waiting for the outcome of this meeting. We are joining forces with EO and then moving forward. If we are not going to merge with EO then we would move forward looking elsewhere. Maybe W3C.
Judy: You will talk about this further?
Matt_King: Is this an Aria editors agendum?
Michael: yes
Judy: Anything else?
... Maybe makes sense to do individuals coordination and then
come back for update.
<janina> https://www.w3.org/community/dic/
Judy: The W3C CG needs a
community group liason
... this is a tour of community groups that have accessibilty
relevance.
Janina: We thought digital identity is of interest and concern and very relevant.
Judy: Did this start recently? Active? What expertise mix?
Janina: Its recent. I don't know how active and I don't know how they are defining what they are planning to achieve.
Judy: MIssion: Identify and
resolve real world identity issues, build a more trusted
identity ecosystem for IoT. Security, privacy, mobility,
etc.
... They didn't include accessibility in their mission
statement and when you are looking across all those systems
accessibility is important.
... started June 2019.
... looks like its run out of China.
... 21 participants.
tzviya: This looks like it
overlaps with an existing working group. The digital identity
working group is already ongoing.
... they may not know.
<tzviya> https://www.w3.org/2019/did-wg/-> Decentralized Identifier WG
<tzviya> Credentials CG https://www.w3.org/community/credentials/
Rachael: Do we have somewhere to point folks to when we want to ensure coverage? We may not find someone in 2 weeks. How do we know its filled?
Judy: We just updated process to a group a week. We could , after we discuss on this call, post it somewhere. Maybe APA?
Janina: We already have a tracking matrix. That helps us coordinate. It may take a minute to find that URI. Beyond that, we should talk about it. Maybe another column in the table. It is sortable.
Judy: I think something that is
persistant. Discoverability is a concern. You aren't alone. Is
there a way to surface this? Maybe an easy link? We can follow
up on this.
... discoverability is the main thing.
<janina> https://www.w3.org/WAI/APA/wiki/Community_Groups
Judy: always good to have more than 1 person covering. Its when we don't have any coverage we have concern. Any ideas on links Rachael?
Rachael: I think the table is good (reduces work) but am not sure the best way to do so.
Judy: Jemma, I want to circle
back with Matt's proposal after we finish this agenda
item.
... for filling this, please keep it in mind and bring it up in
places where people may be interested. Any ideas?
Janina: If I could respond to decentralized identifiers. We met with them at TPAC and are looking at sending them additional accessibility use cases as requested.
Judy: I think we're set.
... Jemma, did you join for the webex(online meeting) because
you want it to go forward or have concerns?
Jemma: I don't have any objections but am still finishing reading the minutes. I have no objections nor anything to add at this point.
Judy: Sounds like that will go
forward. We'll check back in a few months.
... AGWG charter status discussion.
... not yet officially announced. Proposed, revised charter
moving forward. Announcement will be out in the next day or so.
Several edits to clarify scope. Several items to bring to the
working group for discussion. Important to follow up on but not
in charter.
Judy: Thank you to Michael,
Alastair, Andrew, Shawn and Jeanne for getting that done. I
want to note that this process took most of the year.
... Typically we hope charter development is not that extended
but I do want to alert folks who have charters upcoming to
start earlier than you think you need to.
Tzviya: As a member of the AD, several of the members of the AB are concerned about this. The process being much harder than expected. I am reviewing the incubation process and if you have anything you'd like to discuss about that, please let me know.
<jeanne> +1 to the high work burden
Judy: I would like to and I imagine Michael will as well. I think W3C has pressure to increase agility but the charter process is the opposite. There is an expectation that charters will be shorter duration. High work burden for chairs. In this case we were able to get 3 years but if it were 2 years, we would spend 50% of time on charter even though work is continued.
+1
Judy: lets catch up on
that.
... anything else on the AGWG charter?
Michael: I'm just waiting on announcements.
Judy: Quick question. Were there any other WF and Taskforce plans that were settled.
Rachael: For whoever is there, COGA will piggyback for an hour or two on Silver's CSUN meeting for whoever is there.
Judy: The inclusive design for
immersive web workshop in seattle there were quite a few people
interested in follow up but scattered across many different WG,
Community Groups and task forces. I have concerns about
coordination so am thinking about some of those topics into
this call.
... just to make sure the right work is getting positioned in
the right place. I think some people in this call are
interested in this topic anyway. Is there anyone who wants to
push back on us rolling some coordination work into this call
until something is in place?
... I'll bring something more specific into a follow up
call.
<jeanne> good idea
Judy: any updates before we close for the year?
Thank you.
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/couse email/course email/ Succeeded: s/ENO/EOWG/ Succeeded: s/finishing the minutes/finishing reading the minutes/ Succeeded: s/web design/webex(online meeting)/ Succeeded: s/AD/AB/ Present: MichaelC George Judy Rachael_ shawn tzviya janina CharlesL Matt_King jeanne jamesn JemmaJaeunKu Regrets: Katie Brent Sharron No ScribeNick specified. Guessing ScribeNick: Rachael_ Found Scribe: Rachael Found Date: 18 Dec 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]