Meeting minutes
Collaboration Tools Accessibility User Requirements.
jasonjgw: Notes inprocess comments from COGA and thanks the TF for them
jasonjgw: Notes Scott went through them and generated our questions and responses
jasonjgw: One challenge that came up relates to scope
jasonjgw: Collaborative editing scenarios, also revision control, change tracking, etc
jasonjgw: May not be an editor, and so far has been text editing, but could be more--just not yet addressed, e.g. media editing
jasonjgw: We're mindful of not expanding scope significantly, esp. to not range into other groups' remits
jasonjgw: We could take on tooling, for example, but we should discuss scope
jasonjgw:
We also have some process issues to touch on
jasonjgw: So, re scope, which in, which out, and which can we rework to bring into scope
scott_h: Thanks everyone for the time and the overview from Jason
janina: I want to suggest we can likely dispense with our process questions and focus on scope.
… Lisa may have questions after she gets a sense of where and how
scott_h: q?
lisa__: Wasn't aware there was now an issue from our doc; can we get a link?
lisa__: Notes Janina, Rachael, Roy, and I have weekly planning; we should use that to stay coordinated
https://
<lisa__> our google doc is at https://
jasonjgw: Notes link above to Scott's summary; clarifies that it will become a multiplicity of issues on github, but we haven't done that yet
Roger: asked about apps
Janina: Yes. Some tools like MS docs do a good job about that.
Roger: I'm not sure how many people know about that.
… If you don't. know, then the publication would have to be converted to MS word.
janina: That's right. The feature broke a few times a few months ago. Working now. It used to be called "download". It prompts you for what format you want to download into.
rajAsks scott_h Explains his experience using high contrast; had to get help knowing where comments ended
<Zakim> lisa__, you wanted to ask for the link to scotts work (i have the google doc) and to say we have probems with the comments, and can put in end of comment marks
lisa__: Would "End Comment" help?
lisa__: Fpound it hard to tell where comments were
lisa__: Comments take up relatively little space, it's hard to know what's in it, what's added
lisa__: We focussed on the process that helped us collect comments
janina: End comment would be helpful. I think you just raised the point that the comment feature is difficult for coga as well as screen readers. If using that feature is a problem, then that needs to be written up.
… that is extremely important because of the industry development.
… this document then becomes more important. IF scrolling to a box on the side is a challenge. We need to capture those.
scott_h: End comment is good, something consistent that jumps out could work
lisa: Think it's worth figuring out what's relevantly easy for each our groups
lisa__: Will do, and ask for your response?
scott_h: Yes, happy todo this
jasonjgw: Returning to the more substantive point, a more detailed comment on the user interface withcomment feature should be captured
janina: Might be helpful to talk scoping
janina: Suggests scoping example for COGA benefits
jasonjgw: e.g. summary of doc
jasonjgw: Providing summary would be out of scope
jasonjgw: Change tracking summary would be within scope
jasonjgw: point is general editing is not what we're working on; rather the collaborative aspects
lisa__: We did see that
lisa__: We did get summary, and easy lang reqs, but also change log
lisa__: Recalls we had collab env could be more supportavie to authors to achieve this
lisa__: would be helpful to have a tag that enables help on demand
lisa__: Concerned to support author contributors to get these things done properly
lisa__: analogy of alt text; one searches for image and checks for the alt and its quality
jasonjgw: suggests a11y info; any update of what it applies to triggers prompting that a11y info is still correct
jasonjgw: could be one way to integrate
janina: I'm a little hesitatant. I'd like to hear from Lisa. This is still in process.
jasonjgw: Will the existing comments change?
jasonjgw: Asks whether existing received comments are ready for github
lisa__: Have at least 3 more to add; should do that and resend with "end comment"
lisa__: What we sent is approved by COGA, though; should be ready for github
lisa__: But would that be confusing?
jasonjgw: Email would be easier for us
lisa__: Think I should but the "close comment" in the existing; then send the additionals via email
jasonjgw: Any concerns on the strategy
raja: Not here
jasonjgw: Notes there are quite a few, and we'll need to make decisions on each once we have them in github
jasonjgw: We'll communicate per comment once we're ready with a disposition proposal
janina: This has been a very helpful conversation
janina: Early days. COGA will want to weigh in eventually.
… accessibility user requirements started as how can we handle html? How do we make sure everything we need for accessibility in html5? Has several sections.
… kinds of issues, general neeeds. ..We have been asked for a 2.0 of MAUR (sp?) because the document was so successful.
… lots of problems with htmls but one area that had no issues was media.
… time to update.
… we have a laundry list. I know COGA has issues like keywords. The ability to support that in educational environments would get used.
… I think you'll want to get involved at some point. It will be a TPAC conversation w/ media and entertainment interest group.
[discussion about getting link]
… I will share link.
… APA is now looking at charters and those conversations led to wanting to update the MAUR.
… APA in blue sky mode. A lot of groups have come to conclusion so APA is thinking about how to change the web world in 5-10 years.
… ADAPT and AAC will be part of that.
… A lot of things lined up for creative thinking.
Media accessibility: update and planning.
https://
jasonjgw: We're already in discussions with MEIG and APA that will influence MAUR 2.0
jasonjgw: We have a list from MEIG--some of which are very challenging
jasonjgw: We've started collecting our list of items to address
jasonjgw: We've moved MEIG's issues into github, but haven't worked on them yet
jasonjgw: Next step is to get ours into github; then start working on the text
Janina: Some preference for Canvas because they can create livelier animations. Finally got CSS ways to control it and now preferences are changing
jasonjgw: Notes multiple a11y issues crop up when you change the platform
jasonjgw: It came up for TV based environments
janina: Underlying principle is if you create a new platform you also have to reinvent the accessibility support
… regulators care
janina: I am hesitant but believe I should be the one to do it
… TPAC timing is difficult
[Janina and Scott volunteer to work on media post TPAC]
jasonjgw: notes we have wiki; phps we can come back to it post TPAC
janina: Try to get Raja involved around the hard of hearing and Deaf
lisa__: wants to note comorbidity; when there are multiple issues; cause of one issue lends to other issues
lisa__: Notes several COGA members who's first issue is COGA, but now also vision or hearing
jasonjgw: So we'll focus on media for TPAC planning, then working on issues and the doc post TPAC
<lisa__> thanks everyone