Meeting minutes
introductions
<jeanne2> Introductions
<Marie_Bergeron> Hi
Intro to WCAG3 architecture and existing documents
Jeanne: I'll show what we have, & what architectural decisions we made so far.
<jeanne2> wiki page
<jeanne2> Architecture presentation
Jeanne: I wanted to start with the architecture presentation we looked at during TPAC
… We've looked at the architecture in terms of general guidelines, similar to guidelines in WCAG 2 today.
… For each guideline, we expect a how-to document
… It's a plain language how-to with information on how to get started.
… We have different tabs for what you need to know as a Project manager, developer, designer, tester
… We want to make it easier to understand the topics.
… The next level, we're still experimenting on it, it's basically the scoring level / precise statements.
… These may be outcomes, maybe user needs.
… We can assume they are outcomes for now. These are testable criteria, and how to score.
… Then there's the method level, which is specific per technology. How to do alt text in HTML is different from iOS
Marie: When you say levels, do you mean for each topic there will be these 3 different sections?
Jeanne: Yes, it's more of a tree. A guideline can have 3 outcomes, with 15 methods for example.
… The big thing that prompted this is people were looking at examples of the structure, and they couldn't tell the difference between how-to and methods.
… That's what prompted people to want to get some designers to look at this.
Michelle: The current structure is WCAG 2.0?
Marie: Have you already started designs for WCAG 3?
Jeanne: Not by anyone who's a designer.
… We have a lot of documents not in the official standard, but in the overal package.
… The navigation is not as good as we'd like it to be. Those are our first priority. The how-to and the methods
Michelle: So lets say if we have a wireframe, will that be used for all methods?
Jeanne: I think so, yes
… These documents are stored in a different part of the W3C site. I don't have access to it. I can change them in GitHub, but it needs to be broad over to the WAI part of the website. It's a two-step process
… Once we have the wireframes and the new flow, we'll mock it up in GitHub as part of the editors draft, and we'll need to talk about moving it over to the WAI website
… In the longer run we want this all to be database driven.
Marie: So we can have freedom with the design on the how-to.
… What freedom do we have to change WCAG 3.0?
Jeanne: We can change icons, we have to keep standard font and colors
Michelle: We can carry over the fonts? The other pages have a different font?
… We can keep it uniform
Jeanne: Some people liked the tabs, some didn't. We're not attached to that.
Marie: So people are getting confused between how-to's and the methods.
… Are you stuck on the term how-to?
… I wonder if that might clear something up.
Jeanne: I'd rather not touch any of the naming. It's a bikeshed issue, we could spend 6 months arguing about the name.
Wilco: If you have a really good change you can, it's just complicated to change.
Marie: So we're saying its a section describing the guideline. Did anyone not like the term "description"?
Jeanne: We wanted it to be an introductory place for different roles
Wilco: I would say it's not so much a how-to, since it doesn't tell you how to build or test it.
Jeanne: I'd rather have the how-to become more useful, instead of it becoming just a description.
… We have description as a part of the method.
Michelle: What about the timeframe? How did you want us to manage that? Should there be an agenda or list?
Marie: What's the project of the wires, the mocks, do we want, two weeks on a section?
Jeanne: We're starting to try to run the project in 8 week sprints. We do a presentation to the main group every 4 weeks so that the subgroup doesn't get too far away from the main group.
Marie: So like a monthly stakeholder check-in
Marie: So right now we'll work on the text alternative section. I could have wireframes in a week, 2 weeks?
Set goals and next steps
Michelle: If I do my wires, should I then check in here?
Wilco: I would suggest we check in weekly. Spend around 4 hours a week on it.
Jeanne: There was one more thing I wanted to look at today. We have design issues opened on GitHub
Github Issues
Jeanne: Different people had different reactions. Whenever we publish a document we invite for public comments.
… These are the ones we thought were related to design
<jeanne2> Githubn Issues on Usability
Marie: Michelle and I started reading these last week
Jeanne: 306 is something you can't do much about. The rest are important to look at
… Everything we do is public. If you can't get to something let me know.