Meeting minutes
Announcements
scribe Laura
Maryjom: not meeting the first week of january. We will begin the second week of January. (the 9th).
Maryjom: AGWG today published four things. Updated WCAG 3 draft.
<bruce_bailey> Announcement for W3CAG: https://
Update to the explainer doc. Updates to 2.1 to 2.2 to include the errata. How does that impact the WCAG2ICT text? We will have to check.
Maryjom: Check your email for updates from Rachael Bradley
Bruce_bailey: Is there any article besides the updates to the listserv?
Maryjom: checking the news for an announcement.
<maryjom> https://
Bruce_bailey: yes, an update is in the WAI News page
<bruce_bailey> Also WAI landing page: https://
Maryjom: zakim, next item
Explainer
maryjom: I was concerned that we were revisiting decisions we had already made.
Maryjom: first will cover the explainer
<maryjom> https://
Maryjom: This is a note on a note so it goes through a less formal publication process.
Maryjom: Briefly explain proper uses of ICT. To help developers to understand what criteria do and do not apply.
Maryjom: We need to improve the language through the addition of an explainer.
<Zakim> GreggVan, you wanted to say we need to tweak the appendix A and
GreggVan: we don't need to revisit all of our decisions but there are a few cases where we have decided we are wrong.
GreggVan: Appendix A problematic for closed functionality section, the title should be changed to include the other issues.
Maryjom: Had decided to send the explainer as-is. Then were rehashing the decision.
Do we have an explainer or not.
GreggVan: Legislative notes are not formal but document the notes of the group so that people know the background but it's too much to put into the law.
GreggVan: Would like to have it informally.
Meant to be extemporaneous notes.
ChrisLoiselle: Dialogue from last week was about what the explainer was, and how we were going about it. One of the main notes was embedding in the original vs having a separate doc.
ChrisLoiselle: I agreed that a plain text "this is what we mean by this" would be better served in the note vs in the explainer that directs people elsewhere.
ChrisLoiselle: explainer is duplicative of our work statement in some cases.
<dmontalvo> https://
Dmontalvo: Based on the sections that are outlined and the abstract, I said that there are things here we may not need (do we need them). What are we saying in separate places?
Dmontalvo: Let's do the exercise of knowing what is said in the pages to figure out what to include elsewhere. I was also worried about the format of the explainer. Whatever we decide it needs to be more informal.
Sam: I would agree with Maryjom that we agreed to this. It is not duplicative to the document itself. It is short. It allows us to talk about DOJ etc.
Sam: I thought that was decided. We just need to make sure there is no overlap (no redundancy?) against the document itself.
maryjom: We were asked by AGWG to have the explainer as part of the information we are sharing.
<bruce> +1 to dmontalvo that WAI intro page might serve as Explainer
Maryjom: AGWG was worried that we were getting into the realm beyond scope (telling policy makers what to do/not do).
<bruce> +1 to Sam that addressing DOJ cite is important -- and that is not a good fit to WAI intro page !
Maryjom: These are some good thoughts on the explainer as far as what we might put in there.
<ChrisLoiselle> Laura: Is explainer just a tldr or laymen's term document?
<ChrisLoiselle> too long didn't read = tldr
maryjom: yes. TLDR.
GreggVan: we need to make sure we aren't putting content into it that is only in the explainer.
GreggVan: It is for when people get into arguments
<ChrisLoiselle> I read https://
<bruce> +1 to ChrisLoiselle
Laura: which is it, an explainer of how we came to our decision or a TLDR
ChrisLoiselle: Endorse daniel and bruce's contribution
GreggVan: We can't put everything in WCAG2ICT because it's too long
GreggVan: Plain Language thing vs explanation for what we mean by . . . .
GreggVan: Need for both to capture our notes. That document could be a wiki (notes of what we were thinking) - wiki would need to be preserved.
GreggVan: Published doc about what the purpose is of the doc and a plain language version
Maryjom: agrees that there are two different purposes.
<ChrisLoiselle> ok. understood. just wanted to offer it up as a possible solution.
Dmontalvo: I would like to think of the intro pages as "the explainer" as Bruce said earlier in the IRC.
Maryjom: Would have to look at the web page and see if the outline matches the google doc.
<maryjom> POLL: Explainer: Should we 1) continue with the outline in the Google Doc. as-is, 2) update the outline in the google doc with outline from the web page? 3) Start with the outline in the web page and add in sections we think need adding? or 4) something else
Bruce: not sure of the difference between 2 and 3
<ChrisLoiselle> 3 would be taking content from 2 and putting it in the explainer doc we are working on
bruce: could also use the outline that is in the explainer explainer doc.
<bruce> https://
Maryjom: no.
ChrisLoiselle: We own the explainer google doc. We can take what the WAI doc has and add it to our google doc.
Because we own it.
<bruce> i agree that the template from the "explainer explainer" is not a good fit
<Laura> +1 chrisloiselle
maryjom: want to alleviate AGWG concerns that we are telling policy makers what to do.
GreggVan: if this is just an explainer doc (TLDR) in plain language then it shouldn't have more information than we have in our document.
<maryjom> POLL: Explainer: Should we 1) continue with the outline in the Google Doc. as-is, 2) Start with the outline in the google doc and update with pertinent sections from the web page 3) Start with the outline in the web page and add in sections we think need adding? or 4) something else
GreggVan: If we are saying how to apply it, we aren't explaining the doc, we are directing people how to use it.
GreggVan: If something is complicated, we should have a plain language version or simple form of what you are going to be reading.
<ChrisLoiselle> We can explicitly state in the wcag2ict not itself in https://
GreggVan: Simple form up front
<ChrisLoiselle> Laura : Plain language vs. tldr , we should choose one or the other or differentiate
ChrisLoiselle: On the WCAG2ICT note we have there is the guidance and then the note.
ChrisLoiselle: Could make sure the note/explainer includes "This is not for you" text to clarify based off the guidance
<Sam> q_
Maryjom: we aren't getting anywhere. We aren't excluding any particular audiences with this text so policy makers might look to this. For developers, policy makers, etc. Not solvable by removing the audience.
Maryjom: We need to agree. Do we need it? And then have to figure out the form it would take?
Maryjom: Alternate proposals for the outline should be presented.
Maryjom: Then we can analyze and vote on it.
Priority of Level AAA
Maryjom: Another conversation from last week. In the scope of work (PR on the work statement update) we had talked about priorities.
Maryjom: We had updated priorities in the scope of work (Bullets 5-8)
Maryjom: One of the bullets, the text got merged in (suggested changes that can be incorporated).
Maryjom: We removed AAA to the bottom (Not bullet 1).
Maryjom: Added in the two bullets based on AGWG leadership to go beyond our previous work statement.
Maryjom: So we can expand the scope.
Maryjom: Need to update work statement and explainer in order to run off and start working on them.
Maryjom: Decided AAA was lower priority. Was there new information that came up last week? Or same priority?
<maryjom> Poll: Do you agree with current draft work statement priorities in the bullets?
Yes
<Sam> y
<loicmn5> yes
<bruce> yes
<MikeP> y
<ChrisLoiselle> yes
<GreggVan> y but be sure the chairs are comforatable with it
ChrisLoiselle: Intent was a bulleted list that was being shared so it was unordered and not in the same place in the bulleted scheme. Should we change the unordered list?
ChrisLoiselle: It is something I would like to get through. Don't think we say it's the lowest priority. In terms of AG we can declare if needed.
Bruce: AAA can be asynchronous from the other work.
<Laura> +1 Chris and Bruce
Dmontalvo: Avoid saying it's a low priority, could add "as time permits"
<ChrisLoiselle> If it is a touchy subject those interested can join our group!
<maryjom> PR 942: https://
Sam: Question, is it my understanding that by the order of operation, first we will see if we need to apply fixes from the latest update
Sam: Then fixing up the explainer doc
Sam: maybe technology specific examples on a separate track.
MaryJoM: mobile accessiblity task force has a draft together and have potential changes for some of the SC's.
rragent, draft minutes