Brent: MaryJo is the lead, Andrew and Robert are supporting her. Eric added MaryJo's text to the prototype and Andrew put the issues in GitHub.
... let's look at the prototype and Andrew will walk us through the GitHub issues.
<Andrew> prototype - Policy Prototype
<Andrew> issues - Policy Issues
Eric: I changed the left navigation to reflect new content from MJ's Word doc. Added intro text from that so that we can look at it and discuss.
... the Overview table now has headings and can be expanded and collapsed.
Andrew: Thanks for putting that up it will be helpful. I have added the issues, my comments and encourage EO to add comments and other issues as needed.
Brent: If you will just introduce each issue so we can get familiar, we won't try to come to resolution.
Andrew: The first issue was the fact that a strong disclaimer is at the top, seems distracting could it be on the bottom instead or collapsed.
<yatil> ?? https://github.com/w3c/wai-policies-prototype/issues/2
Andrew:It depends on how people will use this, how they will interpret a disclaimer. Don't want it to be a discouragement.
<yatil> ?? https://github.com/w3c/wai-policies-prototype/issues/3
Andrew: second one was a question about law vs legislation, is there a distinction? It is something we need to consider and reach consensus about. Definitions of 'public' 'private' - do we need 'nonprofit' etc.
<yatil> ?? https://github.com/w3c/wai-policies-prototype/issues/4
Andrew: Then there is an issue around scope, what goes in that column?
<yatil> ?? https://github.com/w3c/wai-policies-prototype/issues/5
Andrew: the summary table does not now list regulations that may be in development or pending, should we list them? Discuss the status column please.
<yatil> ?? https://github.com/w3c/wai-policies-prototype/issues/6
Andrew: currency indicator had some comments from MaryJo and wondered if we want to indicate somewhere what is new as a flag or something...and then how long is something 'new?' and/or a need for a pointer to what is new and if so, how to do that. What to put into an update statement.
<yatil> ?? https://github.com/w3c/wai-policies-prototype/issues/7
Andrew: in terms of categorization how to handle things that are recoemmendations without legal requirements, she gave an example. So the questions would be how to refer to strategies that are beyond just law, legislation. So how to approach that?
<yatil> ?? https://github.com/w3c/wai-policies-prototype/issues/8
Andrew: next is a terminology question. We could have a way to refer to the agency or other responsible body but since they differ from one country to another and may have translations issues, we should define it clearly.
<yatil> ?? https://github.com/w3c/wai-policies-prototype/issues/9
Andrew: finally we need to know how much detail to include. MJ suggests only links to rules, laws, and how to meet docs. She prefers no additional supporting docs and I had another point of view. Those two POVs are both captured in the GitHub comments.
<yatil> ?? https://github.com/w3c/wai-policies-prototype/issues/10
Andrew: I have a request for you Eric, at the top of the prototype, could we link to the current page for comparison's sake? so this week the goal would be to review comment as needed and add any additional issues that occur to you.
... Another question was about the level or quantity of information and if we want explanatory notes since they are often written in much clearer language that the law itself.
... that is probably all that needs to be said about it for now. I invite people to look, compare, think about how much information we want and how to classify it.
Denis: My first comment I have turned into an issue related to the level of detail. The table itself seems to be easy to skim, so I think the data in that should be sparse. Details can go elsewhere in the resource.
<Andrew> +1 to Denis
Denis: we are currently using bullets and arrows and it took me a while to realize the information structure. People will miss what it signifies, not realizing the functionality.
Andrew: Yes I agree the toggle is not clear.
<rjolly> +1 to Andrew's clarification that we should link to the current, live version of Policies on the prototype page.
Andrew: I would request that there be a link within the prototype to the existing document.
<dboudreau> Change the right-pointing arrows to a more obvious call to action
<dboudreau> https://github.com/w3c/wai-policies-prototype/issues/11
Eric: PLease understand this is a prototype it has not been styled do not need to comment on that. In fact, please do not comment on styles or the arrows,etc since we will apply a different look. This is a prototype, we use the standard HTML5 details element for prototyping reasons. We don't know how disclosures look in the new design, so we didn't implement that. Please don't comment on UI yet.
Brent: Currency indicator seems to refer to money, can you change the title of that issue
... and remember that not all information has been put into the GitHub issues, you may need to refer to the Word doc for detail.
... any additional questions or comments for now? OK hearing none, remember that this is a high priority plan to spend review time. Want to get it quickly into shape so we can begin adding data.
<yatil> [Eric: Added link to current version: https://github.com/w3c/wai-policies-prototype/commit/6a9fe9e4d8b443eb15b69ebda68f7f855c4303e2]
Eric: Two quick things: First issue 408 we had the discussion about 'Key Points' the suggestion is to retitle that section.
...Suggested options are:
<Brent> Carousel Concepts Page: https://w3c.github.io/wai-tutorials/carousels/
Eric: Can we have a show of hands for #1
<Laura> +1
<krisannekinney> +1
<rjolly> +1
<Howard> +1
<Andrew> +0.5
For +#2
<Brent> +1
<Andrew> +0.5
<yatil> +.85
Sharron:I would support the singular - "What makes a carousel accessible?"
<Howard> +1 for #2
<Brent> +1 to Sharron
<dboudreau> +1 to what makes a carousel accessible
<Andrew> +0.9
<Brent> +1
<Laura> +1
<yatil> +.89
<krisannekinney> changing my vote to #2 +1
<Howard> +1
Sharron: +1
For #3?
<yatil> +.11
<dboudreau> +0.1
<dboudreau> (for solidarity)
Eric: Seems like the modified version of #2 "What makes a carousel accessible" is the winner here.
<rjolly> I have no huge problems with #2.
<krisannekinney> i changed my vote too
Brent: Any objections? Hearing none, we have resolution.
RESOLUTION: The section will have the heading "What makes a carousel accessible"
<yatil> https://github.com/w3c/wai-tutorials/pull/412#pullrequestreview-19757986
Eric: The second issue was on the styling page. Shadi made some editorial changes and I will put this into the survey.
<Brent> Styling Page: https://w3c.github.io/wai-tutorials/carousels/styling/
<yatil> "Indicate Button Status"
Eric: changed to "use redundant status indicators" as a heading. I found that to be very abstract. Agreed to live with "indicate button status"
... wanted to ask if anyone objects to that compromise we made?
Sharron: Sounds good to me
<Andrew> clearer heading now :)
<Brent> +1
Brent: Thanks for all the work on this and all the Tutorials. Any other questions or comments?
Brent: This is one of the resources we are updating. Howard has been working on it as RM and brought it to the planning meeting. We asked him to walk the group through those today.
<Brent> Template Page: https://w3c.github.io/wai-eval-report-templates/
Howard: I will share my screen if you wish to follow along
... the yellow highlights are the things I changed. I also changed but did not highlight the update to WCAG2 from WCAG1. Added the Report Generator and Methodology links. Asked to mention Easy Checks and did that and added a link.
... I refered to the browser/tool configuration as the testing environment although that is not quite how it was mentioned in the existing doc where it is called "accessibility support baseline" which seemd too jargony for this. Will add, at Shadi's suggestion, to download blank template.
<Andrew> interesting how 'accessibility support baseline' has largely disappeared from a11y discussion
Brent: Shadi's email response is posted as an issue
Sharron: What is the intent for the highlighting? Will it remain?
Howard: No the intention is only to let EOWG know what has been changed
Howard: I will let Eric decide what of the changes reamins in a callout box
Brent: any other questions or comments?
Sharron: Susan has been working on the resource and has made suggestions. Her work load has increased in her job and so she will be stepping away from EO for some months.
... She is commited to completing the work she started on Mobile and has been communicating with the Mobile Accessibility TF. So she is compiling work to date, will post issues to GitHub.
... Susan's viosn is to ensure that our references to mobile accessibility are more clearly integrated to all of WCAG and focus on more actual implemention rather than theory.
... She will work on this resource to finish it up and then step back from EO temporarily.
<yatil> [Sounds like a good plan over all.]
<yatil> [Especially integration.]
<Andrew> +1 to integration, especially with many orgs taking a mobile first approach now
Brent: No discussion of this today, just a quick update.Looked at visual design, thank you all for your feedback on Alicia's design. The issues that emerged were addressed at the last TF meeting. We closed many of them, a few remain open and some of those are significant.
... next week we will have a walk through the IA and I invite James to wrap up this quick review.
James: Good meeting on Wednesday. Design by committee always has inherant challenges. but I think everyone was heard, we closed several issues, as we agreed on them during the meeting. Alicia is taking the open issues back for consideration and we are hoping that the next iteration will be it or close to it. The information architecture is coming up next and Charlotte and Alicia are working together on that. Anything to add?
Sharron: James is an *awesome* PM
<Laura> +1
<krisannekinney> +1
<dboudreau> +1 :)
Caleb: I think the work we are doing together is so inspiring, and am feeling really strongly that it will be a game changer
Eric: +1
Andrew: Any intent to let people comment at CSUN?
Sharron: Yes but there are dependencies/contingencies
Eric: Having a good prototype would be awesome but even with what we have now we can gather impressions.
Brent: James please convey our support and appreciation to your team of volunteers. The TF is phenomenal!
Brent: It was on the survey but wanted to encourage everyone to think about this and contribute. The f2f is always productive and the charter defines our work for the next couple of years, so it is useful to have your input.
<krisannekinney> Found out today that I will be able to come to the F2F meeting!!!!! very happy!
Sharron: Cheerleading about importance of participant input into both the charter - what is it that *you* want to do to move accessibility forward across the globe? - and the F2F where we get so very much accomplished.
Brent: And be sure to let us know if you want to attend by phone so we can set that up if needed.
Sharron: At TPAC we did internal promotion of EOWG and the work we do, as well as wanting to help other working groups with outreach. Recently I was asked about contributing to the new Techniques that the WCAG (now AGWG) have posted and can be commented on. Techniques are a sort of roadmap for designers and developer for meeting Success Criteria.
... Eric and I have added some links in the agenda to current GitHub issues and a link to the Techniques wiki page for instructions and background.Individuals can make comment on these as they choose. we are not likely to have group bandwidth to process comments in the near future but anyone insterested is strongly encouraged to take a look.
Eric: The link is to the new Techniques for WCAG2.1 we may be in a position to give guidance when publication is near. It would be good for us to get some perspective on it. No public working draft yet but now is a time to get on the ground and/or comment on older ones that may be outdated.
Brent: Any comments or questions about commenting on the Techniques?
... Any other new business? items of general interest? announcements?
Brent: Look for Policies questions on the survey as well as Tutorials and Template report approvals. Any addiitonal time can be spent on commenting on Charter and the Face to Face and of course, your RM duties.
... thanks everyone, see you next week.