Meeting minutes
Scheduling update
Lisa: We'll do general issues today
Lisa: We'll do Interactive Components on April 23.
julierawe John and I will be ready to send the pre-read for Interactive Components by tomorrow or by Monday at the latest.
Lisa: On April 30, we'll discuss Text and Wording.
LenB: We'll send our pre-read on April 23.
It takes at least 3 weeks to do an initial review. Maybe we should try to recruit more people to do this work.
LenB: It's worth a try to recruit more people.
Lisa: I don't think it's realistic for someone to have less than 2 weeks.
Lisa: I could put off finishing error handling and start reviewing a new section.
Lisa: That would still give me only two weeks to review Process and Task Completion.
Lisa: If Jan and Len were each taking one separately, that would be two separate sections.
Lisa: We could ask Jennifer to review a section on her own.
ACTION: item: Julie to ask Jennifer to review a section.
Lisa: Is it significantly easier for you to work with Jan?
LenB: I think it's significantly easier and better to have a thought partner.
ACTION: item: Julie to ask Eric if he's ready to take on a new section.
Lisa: If we do ask people to do another section, we need to be kind in the scheduling, such as giving a full month to review.
Lisa: I'm not promising on when to do Process and Task Completion because we haven't finished doing Error Handling.
Lisa: John, you're going to partner with me on Process and Task Completion. I can do a first run-through and share it with you.
Review of general issues
1st general issue: What are some things core and some things supplemental? Is it equitable?
Link to 1st issue: https://
Lisa: 1st bullet in definition of core requirment is about assistant technology, such as screen readers.
Lisa is going through each of the bullets in the definition.
Lisa: Very little here has to do with COGA.
julierawe flagged that the fourth bullet about "necessary support" is vaguely worded but in a way that could be helpful to COGA.
Lisa: It could be interpreted that way. Something like "findability," that design is clear--is that a necessary support? Or is that good design? It's not clear that any of our stuff is here.
Lisa: The definition of supplemental requirement notes that some things don't apply all in all situtations or that are difficult to implement.
Lisa: I don't think we should use wiggle room. It would make it possible for them to downgrade to supplemental at the last minute.
Lisa: I don't want us to lose the vote. It's not what we should want.
Lisa: My proposal is that core requirements should be "items that are essential to the user."
Lisa: "Essential to the user" means they can't independently use the content without this requirement.
Lisa: It's good that we're clarifying what is meant by "essential to the user."
Lisa added more paragraphs to the draft issue.
<Lisa3> do we agee to send this to the coga list and if there are no substantive disagreement or objections, to send it to AG?
<Lisa3> +1
<julierawe> +1
<kirkwood> +1
<Lisa3> Len is also happy
Lisa moved on to general issue #2: https://
Issue #2: Why aren't assertions at the core level?
Lisa: Assertions seem the least important, like AAA.
Lisa: I think the term "assertion" makes it look less important.
<LenB> how does this issue help us with assertions that include core AND supplemental requirements?
<LenB> reco - make two different assertions to address provision type
<Lisa3> do we agee to send g2 to the coga list and if there are no substantive disagreement or objections, to send it to AG?
<Lisa3> +1
<kirkwood> +1
<julierawe> +1
<Lisa3> Len also agrees
Taking a 5 minute break, back at 10:31
Lisa is moving on to the 3rd general issue about how assertions are written: https://
<Lisa3> do we agee to send g3 to the coga list and if there are no substantive disagreement or objections, to send it to AG?
<Lisa3> +1
<kirkwood> +
<kirkwood> +1
<julierawe> +1
<LenB> +1
LenB: When we do the pre-reads, should we send draft github issues as part of the pre-read?
julierawe: Yes
LenB: What do we do if we're reviewing a provision and we don't have research that supports the user need?
LenB: Text style readable is an example. There are not COGA user needs about font face, character spacing, etc.
LenB: I don't see any COGA research on user needs about font face, etc.
LenB: We will mark it as a gap in user-needs research.
LenB: Jan and I want to raise with the task force how to address this gap in COGA research.
julierawe: Include the problem in the pre-read so people can think about it about beforehand.
Link to scheduling tab, which has many unclaimed sections: https://
<LenB> been kicked out of IRC a couple of times today - not a good scribe candidate today.
Jennifer volunteered to review Help and Feedback
Lisa3 asked to aim for discussing on May 14, so would need to send the pre-read by May 11.
Jennifer: I will aim for May 14 but may need more time.
We already discussed general issues—sorry I didn't do zakim correctly.
ACTION: item: Julie and Lisa to discuss at Monday's task force if more people can volunteer.
julierawe: Is the current voting system usable? Do people know where to vote?
Lisa3: I don't like spreadsheets. I prefer to look at the draft github issues in the google doc.
julierawe: Maybe people should vote right in the google doc?
Lisa3 added voting table to the general issues tab.
Group agreed this seems like a simpler system.
julierawe: What is my comment makes the draft not work for other people?
julierawe: I'm not going to +1 a draft issue that I don't understand.
Lisa3: Some people might put in a 0 if they don't understand but don't want to stop people from going ahead.
Lisa3: If a lot of people put in 0 saying they don't understand, then we may need to discuss it again.
Lisa3: If you use tracked changes, then I am no longer sure what I am voting on.
Lisa3: What happens to my vote if you put in track changes?
Jennifer Should we vote now?
The group is going through Eric's updated draft issues.
Jennifer: Are we suggesting that trigger warnings should be removeable?
Lisa3: The proposal is that settings should give more control to users about trigger warnings.
Lisa3: It also could allow time of day, I want to allow trigger warnings between 8pm and 9pm
Lisa3: I can control when I get trigger warnings, like choosing to get them when I am after home, winding down after work,
kirkwood: Maybe we should be clearer that our goal is to support personalization.
This is a separate issue about trigger warnings that is lower down in the tab: https://
Lisa3: If changes need to be made, we need to discuss as a group and get to consensus.
Lisa3: Here's a different approach we could try: People could put in their comments, Eric can incorporate, then he resubmits.
Lisa3: If you update the draft, then you have a new version that no one has voted on it.
Lisa3: For Eric's issues, everyone needs to put in their comments. Then Eric can try to resolve. If he's comfortable, then he'll send to the group for another vote and flag the group on which changes have been made.
julierawe: Do we need to align on the Thursday calls before we ask the task force to vote, like we did today with the general issues tab?
kirkwood: I agree with Julie
Lisa3: I've been asked to write a new issue for Error Handling. So probably if I send it to the list, you're not going to be happy.
Lisa3: Maybe I should schedule more time for it in the Thursday calls.
kirkwood: Is there a way we can time-bound the commenting in the google docs?
julierawe: Asynchrous comments are really important. We need synchronous time to align.
Lisa3: I think it's good Julie read my drafts ahead of time and put in comments so we could focus our discussion today.
Lisa3: I think we need to schedule another discussion of Eric's drafts.
ACTION: item: Schedule a discussion of the updated Animation issues.