Meeting minutes
<ChrisLoiselle> GeorgeK: CIO with Daisy Consortium.
<ChrisLoiselle> JamesN: Adobe , know Chris from a prior life at Oracle.
<ChrisLoiselle> Tzvija: I'm with Wiley and involved in W3C chairing committee
<ChrisLoiselle> Brent, I apologize I missed your introduction, could you add here?
<ChrisLoiselle> KatieH: I work with Clover, have worked with AG for over 20 years.
<ChrisLoiselle> Steve, I missed your introduction, apologize could you list here?
<ChrisLoiselle> Janina: I contribute to the APA here, I know Chris from the Silver work.
Scribe, rrsagent, agenda check, confirming next meeting April 21, add your present+
<ChrisLoiselle> KimP: I am heavily involved in the speech input area.
[Updates] Upcoming work and publications https://www.w3.org/WAI/cc/wiki/WAI_Announcement_Drafts
<ChrisLoiselle> Judy: Please look at publication grid and update if needed.
<Rachael> Making Content Usable hopefully net week
<ChrisLoiselle> Janina: Pronunciations first public working draft is ready to go. We want wider audience to review.
<ChrisLoiselle> Judy: This is in announcements section?
<ChrisLoiselle> Janina: Yes.
[Review follow up] Invitation to review EOWG WCAG Videos Project: which groups have reviewed these?
<ChrisLoiselle> Judy: Checking in on review of videos project.
<ChrisLoiselle> Brent: Last time was introduction as to what we were doing. We are looking to create WCAG videos around users and use cases
<ChrisLoiselle> ... These are short videos. We want to have 70 to 100 videos through Education Outreach and want other groups comments as part of this effort.
<ChrisLoiselle> ...Subgroups are working on scripts. These will be put these into batches , 10 at a time. We'd ask for review of scripts .
<ChrisLoiselle> Ask will go out to EO and other groups. There are more details and I'll follow up offline if needed.
<ChrisLoiselle> Judy: Brent, any feedback on this since last meeting two weeks ago?
<ChrisLoiselle> Brent: Shadi had been working on that. Lisa S. and COGA were interested. Key is to send announcement to right place and groups could take up work as they see fit.
<ChrisLoiselle> Judy: Who has reviewed ?
<ChrisLoiselle> KimP: I will look.
<brent> Video Project
Requirements: https://
<ChrisLoiselle> Judy: George or Jeanne?
<ChrisLoiselle> George: I sent links to some videos on wg .
<ChrisLoiselle> Judy: Digital publishing not being tracked entirely may be an issue and opportunity to be picked up by EO there.
<ChrisLoiselle> George: Reviewing scripts on videos, correct?
<ChrisLoiselle> Judy: Yes.
<ChrisLoiselle> MichaelC: Shadi and I talked to this today. The AG chairs need to be alerted that EO is reviewing. AG and EO needs to be done in parallel.
<Rachael> +1 to Michael
<ChrisLoiselle> ... in parallel rather than in sequence. There is a stage in the process. Thorough review is the term. AG needs to be involved in that process.
<ChrisLoiselle> Brent: We have a project page in Github , subgroup review of scripting. Questions are raised on scripts on Friday meetings. Then we raise to thorough review.
<ChrisLoiselle> We don't want to raise to EO then have to backtrack.
<ChrisLoiselle> Jeanne: I had not taken an action item as I thought it was WCAG 2 only.
<ChrisLoiselle> Jeanne: If not branding as WCAG 2 only, WCAG 3 will be interested in generic templates for use cases and user needs for guidelines.
<ChrisLoiselle> ... interested in early stages for sure.
<ChrisLoiselle> Judy: It is important to receive feedback groups and follow up on this topic.
<ChrisLoiselle> Brent: Talking to the AG group , either I or Shadi, could be worthwhile on the subject. I'm happy to do that.
<ChrisLoiselle> Judy: Cross communication is important.
<ChrisLoiselle> KimP: Where should we be sending the feedback on scripts?
<ChrisLoiselle> Brent: We will put everything into surveys and provide feedback on Github.
<ChrisLoiselle> MichaelC: AG needs an introduction , 30 minutes or so.
<Zakim> MichaelC, you wanted to say orientation to AG important
[Discussion] Intra-WAI Coordination procedures
<ChrisLoiselle> Judy: This relates to agenda 8 .
<ChrisLoiselle> MichaelC: AG and task forces coordination needs to be reviewed. A group could send comments to another group. Doing so late in process holds up publications or other efforts.
<ChrisLoiselle> ... We all need to concentrate on reviews being done earlier in process.
<ChrisLoiselle> ... It is an issue in WAI . We need to work it out to AG and task forces but apply it across WAI in general.
<ChrisLoiselle> Judy: A gap in coverage within Deaf community has been expressed. I'm hoping all issues have been resolved.
<ChrisLoiselle> Judy: Issues were both internal and external. Cross group coordination needs to be improved to help with these type of issues.
<ChrisLoiselle> Janina: I like the idea of a dashboard. I think socializing as a public resource would be helpful.
<MichaelC> AG facilitator discussion of review coordination
<ChrisLoiselle> Judy: Some of the comments came from immersive captions community group. Some community groups work on pre rec track documents.
<ChrisLoiselle> ... It may be important for them to attend this meeting in the future to get the connections at the right time.
<ChrisLoiselle> MichaelC: Speaks to dashboard aspect of tracking.
<ChrisLoiselle> ... We identified issue of timing and horizontal review processes. We wanted to speak to AG as a start for this process.
<ChrisLoiselle> ... Reviews are requested and carve out time for these reviews will be discussed.
<brent> +1 to dashboard idea
<Ryladog> +1 to dashboard
<ChrisLoiselle> Judy: Please feel free to send individual updates to this list on this process.
<brent> WG leads staying up-to-date on dashboard and what is needed from other groups.
<jeanne> Could we have a link to the APA Dashboard? Perhaps the next meeting could give us an overview of how to use the APA Dashboard.
<MichaelC> APA open a11y issues across W3C
<MichaelC> Repo for requesting spec review from APA
<ChrisLoiselle> Judy: If there were groups that were active in the WAI space but in the community space perspective, would people find that useful or distracting?
<ChrisLoiselle> George: I like the idea of a dashboard with dates and what we want to review. I had questions on community groups that have an accessibility connection.
<jeanne> +1 to a closer integration of the accessibility-related Community Groups and task forces.
<ChrisLoiselle> ... publishing group has an accessibility task force that will be publishing an user experience guide.
<ChrisLoiselle> George: Inputs from Zoom and IRC are troublesome being read off.
<ChrisLoiselle> Brent: Would the dashboards be public or invite them to the commenting process?
<ChrisLoiselle> Judy: On immersive captions, they meet on Wednesday at noon ET. I think those comments could be impactful to our conversation. I don't think a general broadening WAI CC would be necessary but per agenda perhaps.
<ChrisLoiselle> Judy: I could bring in Phillipe who tracks process changes into the next call. A statement would be something we could explore on W3C statements.
<ChrisLoiselle> Janina: On process document writing , I'm not sure how that works on community groups.
<jeanne> ACT and ACT community group
<ChrisLoiselle> Judy: It is going on in multiple parts of WAI and W3C.
<ChrisLoiselle> Janina: In regard to process things should reach a finished state vs. a draft.
<jeanne> +1 changes to Process document to better integrate Community Groups
<ChrisLoiselle> Judy: Regarding process W3C statements , is there interest in this topic?
<ChrisLoiselle> Judy: Would Philippe talking to this point on 20 minutes or so, would that be sufficient?
<jeanne> +1 to PLH and will read it.
<ChrisLoiselle> Judy: The agenda today has the statement resource.
<Judy> [JB: Send W3C Statement topic with its own subject line!]
[People] Workshop in the planning stage on Production of Media
<ChrisLoiselle> Judy: Francois is putting together a workshop geared toward production of media. His is looking for feedback on draft.
<Judy> https://
<ChrisLoiselle> ... He is also looking for feedback on accessible media experts as well.
<ChrisLoiselle> Janina: I'm sure we are interested.
<ChrisLoiselle> Judy: I invite all groups to take a look at this. We want representation in workshops where we can frame accessibility.
[Discussion] Exploratory Process "W3C Statements": https://www.w3.org/Consortium/Process/Drafts/#note-track
<ChrisLoiselle>Potential new process mode requiring additional vetting but enabling publication of more authoritative "W3C Statements" instead of simply "WG Notes." (Discussion) OK I'll invite PLH to explain more context, and send an additional mail with clear subject line.
[Aware of? Review?] Terminology questions, WAI Style Guide, review commitment?
<ChrisLoiselle> Janina: We could frame this discussion around HTML5 and the backstory of HTML5.
<ChrisLoiselle> Judy: WAI groups have been talking to differences of terminology . Conversation around aria attribute naming conventions, as well as persona pronouns.
<ChrisLoiselle> ... Work had been done on style guide for WAI and WAI groups.
<MichaelC> *EO* style guide
<ChrisLoiselle> Judy: With regard to WAI style guide, that topic could be looked at during another meeting.
<ChrisLoiselle> MichaelC: The WAI style guide is the EO style guide and Shawn, Shadi and I have discussed. We need to review that further.
<ChrisLoiselle> ...COGA developed personas , that needs to then be incorporated to EO style guide, then WAI.
<ChrisLoiselle> ... Groups are struggling to what to do , what not to do for style guide uptake and overall guidance.
<Zakim> tzviya, you wanted
to point to https://
<Judy> [JB: Notes an agenda for a future meeting: To what extent are WAI groups all doing user scenarios, personnas, etc., in completely different ways, or in ways that will dovetail smoothly, to the extent possible?
<ChrisLoiselle> Tyzviya: We
can't make a decision for all of W3C , but https://
<Judy> [JB: Notes an agenda for a future meeting: To what extent are WAI groups all doing user scenarios, personnas, etc., in completely different ways, or in ways that will dovetail smoothly, to the extent possible?]
<ChrisLoiselle> ... Self defined is the name of the dictionary and would be geared to technical audience.
<ChrisLoiselle> ... I can reach to self defined to make an informed decision. I think is greater than EO. I can reach out to help make an informed decision.
<ChrisLoiselle> ... Around pronouns , whether using zero or using one is up for discussion. Informed decision needs to be reviewed further.
<Zakim> MichaelC, you wanted to talk about universal representation in technical documents and to talk about translation red herring
<ChrisLoiselle> Judy: Regarding pronouns, can you clarify whether they were being removed entirely?
<Zakim> Judy, you wanted to react to tzviya
<ChrisLoiselle> Tzviya: There was discussion and I object to the that.
<tzviya> s/to that/ to removing all pronouns
<ChrisLoiselle> MichaelC: Discussion was around are the personas and making them human. Pronouns and using them without calling them out specifically would be inclusive.
<ChrisLoiselle> MichaelC: Use cases with persona types is beneficial. Internationalization is an important topic as well, but shouldn't impede us on gender , pronoun use.
<ChrisLoiselle> JamesN: On Silver groups and aria , there was a state and property attribute use question. Any effort would be around all technology stacks , broad impact , i.e. disabled element in user interface.
<ChrisLoiselle> Judy: That is noted and appreciate the feedback James.
<ChrisLoiselle> KimP: The personas need to be included. On style guides, there are structure, grammar, special terms. All of these need there separate space but included on base is important.
<MichaelC> 3 different types of style guide: writing, video, web design
<MichaelC> KP identified more
<Kim_patch_> 3 types, structure, grammer, special terms