The weekly EOWG meeting began with an update of the Quick Ref. Eric received public comment requesting a way to omit a tag from the filtering function. On Eric's recommendation, the group passed the following resolution:
<yatil> https://www.w3.org/WAI/WCAG20/quickref/?currentsidebar=%23col_customize
Eric: We had public comment on the Quick Ref, customizable How to Meet WCAG 2.0, tags, filters,
<yatil> https://github.com/w3c/wai-wcag-quickref/issues/150
Eric: comment was related to the tags, asked what if I want to show everything except what I choose to tag?
... I took a look at that and replied that I could see the use case but needed to think about the ramifications for the user. It seems as though this is not a quick change that we can easily implement but wanted EO to consider if this is something we will work on for the next iteration.
Shawn: We wanted to ask the group since this is a fairly complex public comment, is it OK to put this on a list for future work but not do the change at this time?
RESOLUTION: Will address the request for a function to de-select tags in a future version but will not make that change right now so we can address the UI considerations outlined in GitHub comment #316438001
<rjolly> +1
<j-pulido> +1
<yatil> +1
<Vivienne> +1
<Brent> +1
<Sharron> +1
<dboudreau> +1
<Sylvie> +1
Denis: I was playing with the QuickRef while we were talking, I noticed there was a misleading outcome, will put that in GitHub.
Brent: We are moving the eo-planning meeting to Wednedays rather than Thursday in order to get the agendas out earlier. Will give us more time to plan for meetings and since we will be working in samll teams, we will be able to announce earlier when we do not need to hold the Friday meeting.
Shawn: Mailing list links are updated where they are referenced. I will also update them on the home page at https://www.w3.org/WAI/EO/#email
Brent: This is a brief intro and then once we explain process we will return. In the survey we asked everyone to indicate interest in editing and reviewing the materials to get in shape for the new site. We spent time yesterday looking at the survey results
<shawn> Materials in development under current charter
Brent: This link is to the work roles for the resources we are developing under the current charter which is ending in August.
... people on these smaller review teams will work more closely getting comments to Judy and her editor in a timely way. The people named here will commit to responding, doing the survey or however response is requested. Anyone who wants to monitor the development of these resources is welcome to do that as well.
<shawn> EOWG Current Projects wiki page
Brent: we tried to make each person editor of only one of the high priority resources. Other editor assignments will be for secondary resources to be completed afterward. There are more people assigned to review teams and you may find your name on several resources as a reviewer. We are asking everyone to consider those. For resources in current development, please look at where you are assigned and consider how feasible it is.
<shawn> Edit and review assignments to update existing resources (New charter work)
Shadi: I signed up to too many things and so what is the process to become a monitor instead of an active reveiwer? Should I just change the wiki table?
Shawn: In most cases it is great to change the wiki directly but because this table is directly referenced in the charter, we would rather that you contact us and allow us to change the wiki. Thanks.
Sharron: Shadi, please just contact chairs and we will consider how to cover the material and respect your need to step back from a few of them.
Shawn: Briefly want to look at the assignments, then look at the process so you understand the timeline and then look again at the assignments to determine how realistic these are.
Brent: ...Next up let's consider the existing materials that are being reviewed and updated for publication on the new web site. As you recall, the instructions for these are to have at least two editors on each and then be assigned a small group of reviewers. If your name is editor on more than one, it is because we will do them sequentially.
... just look through find your assignments and please hold questions until we go through the process. Make sure you understand how to find your assignments.
Vivienne: Looking at Easy Checks, I am assigned both roles?
Sharron: It is due to the nature of EasyChecks, we may have more than two editors, it will be determined later on.
<shawn> Guide for Editing and Review Teams
Brent: We wanted to be sure that we were all working in the same way for consitency. Have made a brief guide and wanted everyone to take a look and have the chance for questions. Let's take a minute to read this...
<dboudreau> -------- done with reading
Sharron: me too, done
<Vivienne> done
<Brent> done
<j-pulido> done
<krisannekinney> done
<rjolly> done
<Norah> done
Brent: I wanted to touch on a couple of things that we wanted to be sure were very clear. In the first section, things to remember about deliverables - understand that the power of the whole of EO working together is that it includes a broad perspective, making the resource widely relevant. It is important to think beyond your own perspective and be sure we are addressing as wide a POV as possible. Make sure that when issues arise, that we bring those to a consensus supported resolution that inlcudes the widest possible input. Remember also that while we can iterate, we want the materials to be of the highest quality possible and hope the Style Guide will help. Smaller review teams will provide initial review and polishing but all resources will come to the full group for final approval to publish.
... we have tried to streamline the process and will give an example of how the approach will work. When I took on an RM in the last round of review, I listed the things I would change and gave that to the planning team (chairs and staff). In return, I received a reminder of links and other related materials that would be impacted by these edits. It was very useful.
... So then, once your approach is approved, do the re-write or re-formatting and iterate as needed with the reviewers. When you have a final, stable draft, bring for Thorough Review to all of EOWG.
... there is more in the Guide about what to bring when, how to resolve issues, how to work with the planning team and the EOWG as needed. Think about the time required for that and fold it into your planning.
... optionally giving you a choice to make a separate mailing list if it will be helpful. Alternatively asking for cc to archive list.
Sharron: Just wanted to add a quick note of reassurance. With the tables, assignments, Guide, instructions, timleines, it can all seem overwhelming. Since we coordinate with folks all over the globe, it is important that we have processes and decision making documented, so that is one part. It may help to keep in mind our goal to take advantage of the efficiency of working in small groups. When we say that all recources must be reviewed before going into the new site, we do not necessarily mean major changes. In many cases it will be just clean-up, additional headings, some wording, changing paragraphs to bullets and so forth. In those cases, the expectation is that an editor may spend no more than a few hours. It is a very agressive timeline at this point to try to publish the new website in a couple months
... another thing to remember is that the Style Guide is meant to be a living document. It addresses punctuation, spelling, editorial style, and more. If you encounter something that you are unsure of or have any questions that are not addressed there - or questions on what is there - please e-mail wai-eo-editors@w3.org with subject starting with [style guide] " -- Participation Info
Shadi: Want to emphasize the expected level of pre-review and to suggest adding a bullet in "when and how", that points to the review stages and to say maybe also a small note in "how to
Sharron: Good suggestion Shadi, how to bring things may need a bit more clarification. Use the perspectives video approach as a model - how you all brought only focused questions to the group
Shawn:Shadi and Brent, maybe you could to write up *brief* case study / tips from Perspectives work ?
Shadi: Suggest a sentence - we encourage editors, teams to bring questions issues to the full group but to shape the questions to get a good outcome.
Brent: In the final review, you are seeking approval to publish. In process review the more specific you are, the more efficiently you will get answers you need.
<shadi> +1 to Brent
Brent: process will be to look at the document, make a bulleted list of what changes we suggest and run that past the planning team. Then do the work as defined, work with your reviewers iteratively as needed and when you are all satisfied, bring for final approval to all of EOWG.
Shadi: Where is the project planning happening? Where are the milestones documented?
<shawn> example project planning https://www.w3.org/WAI/EO/wiki/EOWG_Current_Projects#Policies_Relating_to_Web_Accessibility_update
Brent: We are not creating new resources but only re-writing updating existing resources.
Shawn: Yes, I think Editors and Chairs need an overall schedule for current work for project management. We need to maintain a schedule so we can coordinate consideration of all these- an editorial calendar.
... will be doing a wild crazy push to see what we can get done for the site launch and then can change the pace, learn from what we have done, and do more big picture planning once we get the site launched.
Brent: The bulleted list that is intially developed should include a rough timeline, that could be a high level schedule. For now we will be fast and furious so the project "plan" timeline will be rough and high level.
Sharron: We are asking everyone for a lot right now and want you all to realize that we're not going to keep up this pace all the time. we've been working towards this through the Website Redesign Task Force for over a year and now are ready to push through and get this done.
..all the time you can contribute in the next 2 months will impact accessibility around the world. change image of WAI website and allow us to be proud of the support we provide to practitioners globally.
Shadi: Don't take up all the management on the chairs but ask the RMs to be accountable as well.
Shawn: If you want to join one of the groups, please email to public eo-plan group at this point because you missed the survey.
Brent: Invite you to look at assignments to both tables - the new resources in development, as well as the editing of existing resources.
<shawn> current work roles: New resources in development
Brent: you will see in the table existing resource require editing
... this is our perspective of what needs to be done (that may change as editors investigate) as well as a timeline. You may see your name as an editor in more than one location and our hope is that you only have one that is timed as pre-launch. The expectation would be to do them sequentially.
Shawn: I am not sure that what we have talked about in the Web Site TF and what the reality of the timing is, we have had different discussions about all this and we need to agree on the prioritizing.
... have we brought this to all of EO?
Denis: I am trying to make sense of priorities. Looking at both tables, all the content related to Tips for Getting Started, only my name and Robert's appear. That seems to be where we should focus, should we be working on those right now?
Shawn: In the top table, the intention is to get those done since they were part of the last charter. In addition, we are trying to get existing resources in shape for the new site and that is part of the new charter. We need to agree on the prioritization.
Denis: I will create an email group for the Tips
Shawn: Or I am happy to make a list for that work
Denis: Yes I would appreciate that.
Shawn: To clarify on the top table, we have editors already, just need reviewers. The bottom table is the one where editors are needed.
Brent: Everyone on review teams, need to wait for marching orders from your editors whether the top table of resources in development or the re-writing of existing resources.
Denis: So based on the timing, the Presentations should be my priority?
Norah: I was wondering if for any of the older resources, have reviews been done and changes suggested? Does that exist anywhere?
Shawn: It relates to coordinating with the EO planning group. We can point you to the requirments document or any GitHub issues that may have been documented.
Norah: Where can I find TF discussions?
Sharron: There are minutes and as well we made resolutions here in EO meetings to affirm that we want to be sure that any resource that goes into the new site is current and well structured.
<yatil> https://www.w3.org/WAI/EO/wiki/WAI_Website_Redesign
Norah: I had not heard that in these meetings. I was wanting background from the Task Force work.
Brent: We have left some resources behind to do after launch, a few are in really good shape, may just need some tweaking some gentle editing. It will be a challenge to get this done and so we are going to drive as hard as we can and give you all the support you need. After launch, we will polish a few others and add as possible.
Eric: I don't understand the timeline this seems to be only charter stuff what's up with all the other resources that need a touch-up?- on one hand it says ASAP and otherwise have Q3 etc that may not align. We said we would touch on all the resources, many are missing, have they been collapsed or what?
Shawn: We are combining two things here - the charter work we set extended timelines with the hope to beat them, building in flexibility.
... as well, we have the site launch. The table is trying to reflect both, we may need to change that if it is too confusing.
Eric: We may need a two step approach. For example, with the Easy Checks, we can polish what is existing without trying to build the interactive version until after launch.
<shawn> +1 to Eric that we might do some minor things for relaunch, and then major things later -- at least with Easy Checks
Brent: Yes, we are tersifying, checking links, replace long paragraphs with bullets, etc and make notes about future iterations, etc.
<shawn> +1 to Brent "some of these resources could take months if really want to change them. We just want to get polished for redesign"
Eric: Just want to make clear that it is the intent, just get them in good shape and then iterate later as needed for more extensive rewrites
<j-pulido> Outreach campaign [monitor]
<j-pulido> How PWDs Use Web [monitor]
<j-pulido> Tips for Getting Started [monitor]
Brent: So if you want to add to your assignements or change them in any way, now is the time to do that...anyone?
<j-pulido> How PWDs Use Web [monitor]
<j-pulido> Tips for Getting Started [monitor]
<j-pulido> Presentations [Editor]
<yatil> [ I should probably go into monitor mode for most of mine as I'm occupied with the HTML/CSS/JavaScript ]
KrisAnne: Timing for the launch - is it November? After launch I will be more available to edit due to work demands.
Shawn: Any additional changes can be sent to the planning team.
Brent: Any comments about the timing, does this seem do-able by the end of October?
... probably best to commit to drive this work as efficiently as possible until we run out of time.
... any questions, comments about this?
KrisAnne: I will commit to make myself available as a reviewer but cannot do editing until things clear up a bit at work.
Brent: Any other questions or concerns, please email the team.
<shawn> Sharron, KrisAnne, Vicki, James, Sylvie, Amanda
<krisannekinney> I am happy to review the Intro.
Shawn: Confirm my review team, and then will move on it and get a schedule to everyone.
<Norah> you can add me
<Norah> I would like to be added to review team for intro
<shawn> If you want to change your assignment, please e-mail Send e-mail to public-eo-plan@w3.org
Brent: Next week, all editors should be reviewing thier docs and getting plans in place.
... also remember that your AC rep should be active in support of the EO charter
... some AC reps read previous comments, if they see lots of support it can be helpful for us.
Denis: As members can we see who is supporting the charter?
<shawn> https://lists.w3.org/Archives/Public/w3c-wai-eo/2017JulSep/0009.html
Sharron: Will make concerted effort to have shorter and fewer meetings to give you time to work on your resources
Brent: Thanks so much for the lively discussion and getting so much done today.