Meeting minutes
<garcialo> Zoom is telling me that the Host has another meeting in progress
<shadi> hmmm
<garcialo> I suspect it's because we're reusing the Silver Zoom meeting?
<mgifford> It always takes me so much longer to find where I should be with W3C things.
<mgifford> What is the zoom link?
shadi: w3c systems inclusive but there are some costs with that, today's slow start is an example
shadi: we have 7 people, so that is plenty for quorum...
… action item last week was to add comments to Google doc, as we did not have meeting, thx to mike and jason...
… first two case well commented at this point, but would like to add more to scratch pad
… from next week on we might consolodate and figure how to put into useful documentation
bruce: Next monday is U.S. holiday, then we hit july 4 th week...
… but we only have the eight weeks, so we will proceed with what have. Chairs have not extended deadline. Please contribute off line as much as you can.
Cybele: I would recommend asking AG chairs for more time.
Cybele: also is scratch pad document our main work product for now?
shadi: Yes, Google doc is main doc for now. Please see notes at top of document for background....
… Each of the use cases are linked from document, and with each of the use cases we are trying to tease out implications for standard and policy.
<Cyborg> q still outstanding
shadi: The notes on May 3rd are good example. So reviewing one document and putting our comments into a second document.
shadi: Starting next week, I would to start with a draft of what that guidence document might look like...
… But I will be reporting back our progress to AGWG and I can ask for more time given all the interuptions, but no guarantee of that at all...
… on Tuesday 6/20 is mid point of our cycle, so my presentation to AG will be longer....
… Chair are really asking for all the subgroups to work on 8 week sprints....
… decision will be from AGWG if we extend or conclude.
Cyborg: Thanks for clarification, but I want to stress that we not limit ourselves just because they are already published....
… i understand direction to comment on Use Case document in the google doc scratch pad. It still seems like a constrained to work...
… We have had maybe 3 holidays so that is almost half of our allotted time, so that seems very limiting.
shadi: Okay, I bring this into my reporting to AG. So I will ask for AG to grant more time prior to final report...
… I will also raise issue of having a second sub group for some of the concerns which are out of scope for the task asked from AGWG for now.
<Cyborg> how do we bring all those comments together, including ones sent by email?
shadi: Please see some thought from Bruce and Laura and others at bottom of doc. I left those in, but they may be out of scope...
<Cyborg> such as Gregg's comments...
shadi: There are some GitHub issues (for WCAG3) which might be of interest to this group...
<Jaunita_George> +1
shadi: if you notices those, please link to GitHub issues in our working scratch doc.
Cyborg: Yes, please raise the holiday issued. But previous document written and feedback raised -- but those are not in this work assignment...
… so I worried about the process. I don't agree with framing of the issue, and would liked those worked in.
<Cyborg> just want to be mindful that the critique of the last work on this is included in this work, and not to frame this discussion as coming from the last one in a way that excludes those concerns
Shadi: Other comments? I have brought in Greggs V comments...
… I am not clear where the previous issues / recommendations are that you refrerence.
… Please help me understand, but I do not want to spend much more time today.
Cyborg: I would ask for clearer intent in our scratch pad document...
… Clear intention portion at top would be very helpful.
shadi: I will try to do my best, and address concern.
shadi: Back to agenda, thank you Jason, Laura, and Mike for contributions last week..
… please do work even if we do not have meeting...
I would like to start with situation 7 for today in scratch pad.
<shadi> https://
shadi: No comments so far. There are technology which keep evolving and changing and AT frequently does not keep up...
… What does it mean to provide text alterntive to VR and AR and XR?
<Cyborg> just added a comment early in the scratch pad to reflect my thoughts on intent
shadi: This was discussed by accessible archetecture group.
Bruce asks for some clarificant which changed from this Use Cases document and the previous conformance document in TR space.
shadi: That doc highlighted for me that problems highlighted in that doc were not suited to WCAG....
… the Use Case approach is to think beyond WCAG and what can be done elsewhere.
Mike: I added a couple points and Jason did another. Are those the kind of feedback you are looking for?
mgifford: Okay, good. These need word smithing but I was hoping I was on point.
[Mike reads comment from google doc.]
mgifford: If gov't are going to contribute to adoption, they need to contribute resources.
shadi: Why not ony govt and not industry?
mgifford: It comes to available resources. Govt has money and legal persuation, so neither of those migh be true for individuals.
<Laura_carlson> +1
Cyborg: My plus-one in doc was to govt involement in XR...
… technology even at its best can be problematic.
[Jason reads his comment in doc]
Jason_K: There can be alternatives but that is not equal access necessisarily....
… for example we had a nursing student who had an adapted stethescope...
<Cyborg> +1 to Jason's comment, it actually matches well with what I added to Mike's addition (re alternatives)
Jason_K: but it did not work well on dummy use for training. There were arguements that book made up for it.
… We did not think that correct, and came up with a workable alternative.
shadi: Any thougths on when fundamental alternative or execption is used?
Cyborg: I think it just that the content does not conform. That can be enough.
<Laura_carlson> +1 to Cyborg.
Cyborg: I have some concern to WCAG3 ability to address accesibility at the start...
… Much accessibility is done after the fact. So can 3 help fix that?
shadi: WCAG2x has concept of Conforming Alternative -- could we do better?
shadi: The other point about Early and Often -- is that something WCAG can prescribe -- or is that a process question?
shadi: Here we are thinking more broadly.
shadi: Also please add initial to your comments in doc to facility followup.
mgifford: Missing is personal preference, for example with reality, a person might be using a wheelchair....
<Cyborg> want to point out 8.2 in this document - which appears to be new? https://
mgifford: so is that WC option included in VR experience. This is very different than just a web page.
<Cyborg> will add it to the proactive piece....
mgifford: To focus, it is the importance of authoring. The user experience is getting melded, so our doc can note that.
Cyborg: I just added to early and often, but I believe Ontairo civil rights act has included some universal design,
… recommend that people take a look. Is that a good model for where this doc is going?
shadi: Situation 8, outdated content which is obsolete or hardly used. Are those different?
… Do we want to have things removed? Are there other approaches?
mgifford: This when moving content to archive. Too expensive to remediate. Goverment approach can be just to take down because of administravie burden.
… civilian needs to depend on Archive.org or something.
Laura_carlson: Why have old content online? List titles, but not inaccessilbe content.
<Cyborg> oh wow - so interesting Laura. if we take it all off and make people request it, then they need to make what they put on accessible
<Cyborg> +1 to Laura
<Cyborg> great idea
Louis: So just the index? I like it.
<mgifford> +1 to Laura
<Cyborg> this is so good on so many levels, better for storage energy too, effort distribution etc.
garcialo: Having request bumps the notice that people are interested. Rather than dump, have a way to prioritize.
shadi: I have heard the opposite from disabilty groups, removing it for everyone might not be the best approach.
mgower: ideally would be available and accessible, but if the alternative is not to have it at all, that seems bad choice.
… if posted, violates WCAG. But just having a list seems like a compromise,
… but one which can be exploited.
Cyborg: I love the idea of everything not accessible being taking down but well indexed....
… Once requested, old doc gets remediated before posting.
… As for exploit that wastes time, but is alternative not to try it? Seems like risk can be mitigated.
rssagent, make minutes
Shadi: Mindful of the time, but lets take quick look at situation 9
… Mike has a comment, but others?
garcialo: We want experimental non-conforming content posted so we can start working on a11y....
… seems like situation 7 to me. We need to find resources to fix.
mgifford: The elements that related to getting information for accessilbilty, need the feedback...
… so the feedback mechanism needs to be conforming or at least as ccessible as possible
shadi: Wrapping up, we only have short calls...
… Next Monday we will be prepping for presentation the next day.
Please add time into scratchpad document this week.
… we will be using that to consolidate ideas...
… i am seeing some patterns. For example that organization need to establish processs...
… theme repeated a few places. Also see GreggV comments which echo that.
shadi: Please continue review. We will be meeting 6/19 for the people who are available.
Also, please attend AG meeting Tuesday.
Tuesday 9/20 that is