Meeting minutes
WAI Curricula
<dmontalvo> Curricula Designer Modules Starfish Review Survey
Daniel: This is the topic where we have put together first draft. Still needs polishing based on your feedback.
… Take time to go through the modules and add comments where you can. Starting polishing the draft
Daniel: Curricula is set of modules developing under assumption of targeting different roles. Started with foundation modules published in 2019. After that started to develop specific roles. Developers and now designers and content authors. Cross references responsibilities shared between team roles. Also one of the things to think about when reviewing is how much you agree with distinctions and cross referencing. Open until July 25th.
Daniel: Thanks to those who have already provided feedback. Will be asking for clarifications in coming weeks. Open to questions and comments.
Sharron: Last week we had discussion around changes to content. Does this draft reflect that?
Daniel: Yes, partly. We agreed on EO to reflect changes to designer roles. We decided to use that work already done in understanding involving users module in the foundation modules. This part is now removed for designers but not yet included in the foundation modules.
Sharron: But the intent is that the involving users content will be integrated into foundation module?
Daniel: Yes and we will need a separate EO review of the changes. Another editorial pass will be needed for clarification including the pieces already discussed in EO.
Sharron: Any comments or questions for Daniel?
How people with disabilities use the web - Videos
Shadi: We are supposed to be doing 3 sets of videos based on funding from European Commission. Perspective videos were so well received at time that chairs felt more video content would be good. Short videos of evaluation process.
...We were supposed to do a second set on WCAG SC. Concern however that this was a tall order. Lot of resources and very complex project. Became apparent that this was a long project and hard to ...First set evaluation, Second set was supposed to be WCAG 2.0 videos with all guidelines, third set supposed to be videos on How People with Disabilities Use the Web. Fourth set was meant to be before and after demo. ..Before and after set has not been updated as supposed to be. New plan is to include it all in How People With Disabilities Use the Web. Idea would be that story would be e.g. someone using a screen magnifier<shawn> [ these 3 resources linked from https://
Shadi: e.g. Uses screen magnification. In order to do her homework - e.g trying to do schoolwork, looking up train timetables etc. That would be the video.
Shadi: Second page - tools and techniques would be short video introducing assistive tech and adaptive strategies. e.g. refreshable braille display. Not about the person but about the AT.
...Last video would be about the disabilities. e.g. Not all people with visual disabilties are blind. Different degrees of disability. We had agreed that some people prefer either video or text content. Such a resource could be used very well in training to clarify what users and tools we are talking about. ...Be easier to manage because all shooting/filming would be done in one.Filming of all sets could be done together then scattered around different pages of multi-page resource.Shadi: Any questions? Jade and Shawn have already raised questions.
Shawn: This is going to be a big project but do-able.
Sharron: This resonates with me. A good place to use video. Good for people who have difficulty visualising AT use.
<kevin> +1 to Sharron's comment
Michele: As a consultant you have hardest time explaining AT to people. Can't be too narrow with broad topic like SC. So this is maybe for the best.
Sharron: Agree. If we get too short it could be unclear. This is an excellent move. Thanks Shadi for the very detailed rational. Any questions for Shadi before we continue?
Jade: Just really sad to be losing the ergonomic keyboard argument.
Shadi: This time we get to discuss what an ergonomic keyboard is. A whole video.
Sharron: Anything else on the videos?
Work for this week
<Sharron> Remeber to check https://
Shawn: Related to that is Kevin/Mark/Jayne updating stories of web users. Updated survey to look for next week. Kris-Anne, did you get email to take to COGA?
Kris Anne: Sent email to COGA to ask for feedback about how they wanted to respond to survey - individually or as a group COGA response?
Kris Anne: Waiting to hear back. Hopefully we can discuss once back from Vacation.
Shawn: To let you know, we decided to set a date but open to them saying they need longer. Just don't want it to go on and on.
Kris Anne: Which is why I'm giving options to get it done in a defined timeframe.
Sharron: Link to work for this week in IRC to remind everyone that it's good to check in on that once a week. Updated from time to time.
Sharron: Reminder that timely issues are at top of the page but there are other work marked as option. Reminder to look to see if W3C WAI has tweeted or made an announcement. Spread the word.
...So when you see things like that and can promote then it's useful part for our outreach mission. Over here making resources and sometimes forget to spread the word about them. So this is your freindly reminder to continue to do Outreach. ...and, we will coming up to open the survey on the designer modules and next week the WCAG-EM Reprot tool.Shawn: One survey with EO
Kris Anne: Plugged two resources yesterday at a meeting. Business Case resource and Media resource. Gave them URL.
Shawn: Another part of outreach is we are trying to do better at tracking what we do and the impact of our outreach. When you do things like that, can you list it?
Shawn: Just put reminder to do this in work for this week.
Shawn: List with date and your name so we know what EO is doing when and what the impact is.
Sharron: Related to that is that often people ask about metrics. Maybe we can get reports of not necessarily specific numbers but metrics on which pages are getting most attention. Is there any opportunity for that? Does anyone gather that info routinely? Say, once a quarter?
Shawn: I look at it when I have a reason to but no regular report. For example if we are looking to see what our priorities are re what is being hit. I am happy to share that when it's useful for EO. Not seen much that would be of interest in general.
Shawn: Saw a spike that I could not figure out at all. Maybe EO could look at that to help figure out.
Sharron: Would anyone else find this useful?
<Vicki> +1 I would
Sharron: I will put on the agenda for next planning meeting to decide how we would report that back to the group?
Sharron: Any news to share? Howard, how are your plans for access to Higher Ground this year?
Howard: In terms of interest and proposals, pretty good. Looking to open registrations in next week.
Howard: Format will depend on how many people can travel. Plan currently to be on site.
Howard: Will be interesting. Will be one of the first in person face to face conference.
Sharron: EO can potentially plan face to face meetings in the spring.
Sharron: May post survey about that. What do EO participants anticipate their travel possibilities to be like in the spring.
Daniel: We need to talk about that. Situation could be variable. Will need to make sure it's possible and would look forward to if possible.
Shadi: W3C still on no travel policy until otherwise decided.
Sharron: TPAC virtual again this year.
Kris Anne: TPAC will be on my birthday this year. I expect balloons and cake. I miss meeting this group face to face.
Sharron: Remember to check work for this week and that survey data can be saved and returned to.
Shawn: The other thing that is apparent from analytics. We get huge number of hits on logo pages. Updated WCAG2A Conformance page to be more usable for new people.
Shawn: Chances that some of that is robots.
Sharron: Any other business?Hearing none, we can adjourn. Thanks all and have a great weekend.