Meeting minutes
Infoshare
MC: Some of us were at CSUN. I focused on deaf people. SOme interesting hallway conversations
George: We had 3 presentations. I have to make standards more interesting. The reading presentation got a lot of feedback
Jeanne: I highly recommend Jutta's talk. It is mostly about Artificial Intelligence, but it has an excellent section on standards and how we got where we are.
Matt: On April 13, we will be launching the AT support tables in the ARIA Authoring Practices guide. THese will be the first 5 of what will be 60+
… this will grow over time. APG example with 3 different screen readers
… it will need help for drafting announcements
… the timelines may slip which will help with announcements
James: ARIA moving to PR tomorrow
[jubilation]
<Zakim> Rachael, you wanted to give brief status on WCAG 2.2 if not covered elewhere
Rachael: There is a high probably that WCAG 2.2 is going to slip
Michael: Slips, means a 3rd CR. That will add at least 2 months to the schedule
Janina: and a charter extension?
Michael: They are generally being granted at this time due to the transition. That is making it difficult for groups. That will probably be taken up next year. According to the Process document, we are doing the right thing for going to re-CR.
Rachael: It is hard to get the right solution based on comments. We expect it to be the last WCAG 2, and we could push it through, but it would not be the best thing.
Janina: Is ISO still a possibility, we didn't lose it?
Michael: No, this slip will not be a risk to ISO at the moment.
Daniel: We need to keep an eye on EN-301-549, it could become an issue in the future
Tracker retired?
Kim: A couple weeks ago, the zakim command didn't work. Is that related to the retirement of tracker?
Michael: It needs to be zakim, start meeting instead of tracker, start meeting
… zakim has to be in the channel /invite zakim [#channel name]
W3C site beta https://beta.w3.org/
Michael: Reminder to look at the beta and please report issues in Github as soon as possible.
Shawn: There were more issues that expected, so rollout has been delayed.
… if you filed an issue, you can monitor the issue.
George: So I can expect a "this has been fixed" notification?
Shawn: Yes, that is how it is supposed to work.
Michael: We dtill need to identify accessibility issues as we notice them.
Matt: Does this re-design include the groups functions? Including the calendar? Is there a change to Calendar as part of this?
Shawn: My understanding is that they have already done the changes to the groups and calendar.
Michael: The groups have been redesigned, and the pages in the beta will be what you will see in the regular site
<kevin> Example calendar page
James: I can see problems with time zones
Matt: The thing I struggle most is the time zone change. There are 400+ items in the list. Why are there 400 items in the list.
James: I looked and it has accelerations now. It is better, you can press A to get to America. I'm finding it hard to use visually.
Matt: I don't understand why we don't have 26 entries, or however many time zones there are
Kevin: Please file an issue with suggestions of what will work better.
… they have been working on auto-complete feature based on the UK gov pattern.
<shawn> w3 beta GitHub for issues = w3c/
Kevin: they are working on the auto-complete feature. I didn't realize that there were 400 items on the list
Discussion of WAI strategic priorities
Michael: I encourage you to read the presentaiton
I want to start getting input from the broader community to turn it into a presenation to management
Meeting next Monday