Meeting minutes
scribe
WAI announcements process changes coming (easier for you!)
shawn: At one time, Shawn did all the announcements. Then other staff, chairs, and facilitators contributed more to initial drafts.. We are working on announcements templates.
… and the announcement process. At one time Shawn and EOWG reviewed abstacts and introductiosn for all WAI publications, then was not able to fit it in workload.. Tamsin is leading reviews of abstracts, introductions and SOTD of documents.
… unless anyone objects, Tamsin will take over drafting the announcements.
janina: Want to be able to carry forward the institutional knowledge we have on making announcements.
shawn: Agree, we've been having different people work in GitHub or in Google docs to draft announcements.
… one thing we learned for trying different options is that in GitHub, haiving each type of announcement in a separate file was not best. So will do that differently..
[sub-topic] question 1. Google docs and sheets vs. GitHub ?
shawn: Want input on this topic and screen reader accessibility
janina: Some will be happy with Google docs. Depends on the TF and how many screen reader users they have.
… Are we settling into 2 different tools and how we decide on what tool to use.
… most screen reader users export to Word and can then access it. But you lose the interactive aspect of editing.
shawn: Will continue to develop draft templates in Google docs for now and will eventually have them ready in GitHub and the group can choose which they wish to use.
janina: Sounds fine.
shawn: If we had the list of publications in a Google sheet that you would only need to access occasionally, would that work?
kevin: Would like to not have a Google spreadsheet, as it would be difficult to manage where things are in the process. Prefer GitHub
Daniel: Agrees with Kevin.
[sub-topic] question 1. Any input on format, tone, approach, etc. at this point ?
shawn: Will come back to the group with specific, but wanted input on the format, tone, etc. If you have input, great to get now.
janina: Don't have anything specific now.
Guidance for using Google Docs with screen reader
daniel: This depends on your operating system. On windows, google docs essentially works ok (with some difficulty). On Mac and Linux, it isn't working at all. Missing a lot of characters and content.
… can write guidance for people, but only on Windows are these useful.
… with the WCAG2ICT task force, if you use Google Drive and put the Word documents on there you can synch up with that drive and get access to the content.
Janina: We don't want to force everyone onto Windows.
daniel: That's the high level overview.
Janina: would agree with that, and some have come up with keystrokes to get things to work but it's a burden for everyone to do.
kevin: Wanted to raise this as there were concerns expressed. Plus there's other tools we use that we want to make sure are accessible.
<shawn> [ also Shawn has direct contacts with accessibility folks at GitHub ]
kevin: Leonie has inroads to GitHub and is getting issues fixed for screen reader users.
janina: Should get ahead of this in both environments so we can document issues and know what works. Others outside of WAI are using Google docs, so it would be good to get things documented so they can get fixed.
Any follow-up needed from last meeting? (Kevin sent email to Matthew) https://www.w3.org/WAI/cc/wiki/WAI-CC_agendas#Agenda_from_last_meeting_(27_Jan) shawn]
shawn: Last meeting there was a long agenda and not a lot of folks present.
… wondering if there's updates to share.
janina: Can follow-up via email.