Meeting minutes
WCAG EM Report Tool
Hidde: You are familiar with this tool, we have been redesigning to bring it up to date with current site design. Recently has created ATAG Report tool so used that as a model. Wanted to share with EO let you know what has changed. We will get your feedback later this week on a survey. It is a tool to record your manual test results.
… the first page allows you to open an exisiting or create a new report, the buttons have moved. You complete the scope information, define your report, indicate the technologies you will use. The third step allows you to choose and then the fourth stpe is the one most changed. Brought it into line with WAI website styles and defined outcomes. Can set results for pages to include in smaple outcome.
Can now use markdown to inlcude images, code smaples, etc
Hidde: Can see progress bars now and have the option to hide those. Can add Executive summary and preview the report. The page has changed to reduce clutter, review outcomes and allow for editing before saving. Looking for first impressions today.
Shadi: No new features in this tool but the code has been reworked. There are still a few bugs. The scope of this review is the UI redesign.
Mark: As someone who has both loved and struggled with the exisiting iteration I think this is a great improvement. The use of markdown is a great addiiton. Might ask for a bit wider space for the markdown display.
Hidde: For each of the samples, we nest them all and it tends to look a bit cramped. Are thinking to summarize.
Mark: Design wise it is overall a huge improvement
Hidde: I looked at not putting results into a table, but there are pros and cons.
Mark: May not be needed to show markdown at this level of review
<shawn> Shawn: we will be announcing that an update is coming - so people can test it and get used to it before we replace the old version
<Zakim> kevin, you wanted to comment on sample input, links in 'Add results for pages'
Shadi: We did send our a quite broad message to the community as we said we wanted input for the redesign.
<hdv> related GitHub issue: https://
Kevin: First, starting to look really good. I was an early user and appreciate the update. One thing that is a bit of a pain, the select sample is a long, thin, clutterred page and does not work well in Edge. It is difficult to visually parse. Wasn't there more of a tabular view - is there an option for that kind of view?
… also is there an option to bulk export?
<shadi> For new issues: https://
Kevin: in the audit sample, when you put add results for pages, why is the URL included there? I know why the name is included, it is the label,why the URL?
… is that the right place and the right way to include it?
<shadi> https://
Kevin: The user need is I need to be able to go to the page to check the results, but this is visually a bit hard to parse.
Hidde: I will take this away and think about how to address
Kevin: Maybe compare to previous version?
Shawn: We could use an icon to link to a new page
<Zakim> shawn, you wanted to ask about options for communicating markdown now available and to add to Kevin's point: spacing and proximity
Hidde: There is an open issue to add design to the long and skinny page.
Shawn: Yes it needs more space between unrelated things and less space between realted thisng that will go a long way to address.
Carlos: Is it supposed to be working or not yet?
Shadi: It is not a new function but it is meant to be more visible
Carlos: It needs more information, I can have an output for just one page, will ti split the sample into correct sections when outputting more than one page?
Shadi: We would definitely welcome your inut on error messages, the format of output and such.
WCAG video update
Shadi: Laura gets the proze for being the first for completing the survey. The first set of 10 scripts are ready for your thorough review. Not much more to say.
… at the top is an indicator of what we DO want you to review and what NOT to review. We want to try not to scope creep and keep the focus only on the requirement.
Shawn: The survey will be public so that more that just EO can respond.
Shadi: Next steps on the survey will be announced soon so hold off.
Shawn: Can begin review but keep your notes offline until we get the right staus for entering comments within the survey until we work out the access.
Using GitHub videos
Shawn: I have produced short videos on how to use GitHub. Quick informal things to help people use the GitHub let me know if they are useful, if there are others you might want to have.
Work for this Week
Shawn: Update avaialbility survey and review other items in the WFTW - please review and comment on open issues.
… our plan for today was to introduce these topics and ask you to use the reamining time to review changes to the WCAG Reprt tool and/or the surveys.
List of Courses
Carlos: We received comments from 3 reviewers, would like to understand if our ways to address were acceptable.
Sharron: Will do
Howard: Will do
<JasonMcKee> have a great weekend everyone