12:19:13 RRSAgent has joined #eo 12:19:13 logging to https://www.w3.org/2021/04/16-eo-irc 12:19:15 RRSAgent, make logs public 12:19:15 Zakim has joined #eo 12:19:17 Meeting: Accessibility Education and Outreach Working Group (EOWG) Teleconference 12:19:17 Date: 16 April 2021 12:19:22 present+ 12:19:51 W3C has left #eo 12:21:44 Sharron has joined #eo 12:21:57 present+ 12:22:20 Chair: Brent 12:22:26 Scribe: Sharron 12:24:23 Regrets: Estella, Sylvie 12:30:22 Jade has joined #eo 12:31:18 Vicki has joined #eo 12:31:22 Present + Vicki 12:32:28 MarkPalmer has joined #eo 12:34:42 zakim, who is on the phone? 12:34:42 Present: W3C, Sharron 12:34:56 present: Sharron, Vicki, Shawn 12:36:17 present+ 12:36:23 present+ 12:36:24 present+ 12:36:30 present+ 12:36:40 regrets+ Brent 12:36:41 kevin has joined #eo 12:36:43 present+ Karl 12:36:45 Howard has joined #eo 12:36:49 present+ 12:36:50 present+ Howard 12:36:54 LeticiaSeixas has joined #eo 12:37:04 Topic: WCAG EM Report Tool 12:37:22 JasonMcKee has joined #eo 12:37:39 present+ 12:37:48 CarlosD has joined #eo 12:37:50 present+ 12:38:48 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. 12:39:04 present+ 12:39:31 zakim, who is on the phone? 12:39:31 Present: Sharron, Vicki, Shawn, shadi, hdv, MarkPalmer, Jade, Karl, kevin, Howard, Daniel, JasonMcKee, CarlosD 12:40:27 present+ Leticia 12:41:43 ...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. 12:41:43 Can now use markdown to inlcude images, code smaples, etc 12:43:10 q+ 12:43:21 q? 12:43:32 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. 12:44:19 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. 12:45:10 q+ 12:45:15 ack mark 12:46:45 q+ to ask about options for communicating markdown now available 12:46:53 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. 12:47:44 Hidde: For each of the samples, we nest them all and it tends to look a bit cramped. Are thinking to summarize. 12:48:09 Mark: Desing wise it is overall a huge improvement 12:48:24 s/Desing/Design 12:49:36 Hidde: I looked at not putting results into a table, but there are pros and cons. 12:49:51 Mark: May not be needed to show markdown at this level of review 12:49:57 ack Sharron 12:50:07 Sharron: stats 12:51:07 q+ to comment on sample input, links in 'Add results for pages' 12:51:07 s/Sharron: stats/ 12:51:14 q- later 12:53:25 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 12:53:27 ack k 12:53:27 kevin, you wanted to comment on sample input, links in 'Add results for pages' 12:53:27 Shadi: We did send our a quite broad message to the community as we said we wanted input for the redesign. 12:54:40 related GitHub issue: https://github.com/w3c/wcag-em-report-tool/issues/370 12:55:12 q+ 12:55:19 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? 12:55:35 q+ to add to Kevin's point: spacing and proximity 12:55:47 ...also is there an option to bulk export? 12:56:02 For new issues: https://github.com/w3c/wcag-em-report-tool 12:56:35 ...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? 12:58:18 ...is that the right place and the right way to include it? 12:58:23 https://github.com/w3c/wcag-em-report-tool/issues/201 12:59:49 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. 13:00:04 Hidde: I will take this away and think about how to address 13:00:15 Kevin: Maybe compare to previous version? 13:00:20 krisannekinney has joined #eo 13:00:48 present+ 13:01:58 Shawn: We could use an icon to link to a new page 13:02:29 ack me 13:02:29 shawn, you wanted to ask about options for communicating markdown now available and to add to Kevin's point: spacing and proximity 13:03:16 Hidde: There is an open issue to add design to the long and skinny page. 13:03:41 ack Carlos 13:03:52 Shawn: Yes it needs more space between unrelated things and less space between realted thisng that will go a long way to address. 13:04:30 Carlos: Is it supposed to be working or not yet? 13:04:57 Shadi: It is not a new function but it is meant to be more visible 13:05:55 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? 13:06:06 q? 13:06:41 Shadi: We would degintely welcome your inut on error messages, the format of output and such. 13:07:10 s/degintely/definitely 13:08:14 Topic: WCAG video update 13:09:15 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. 13:10:45 ...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. 13:11:18 Shawn: The survey will be public so that more that just EO can respond. 13:11:50 Shadi: Next steps on the survey will be announced soon so hold off. 13:12:41 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. 13:12:57 Topic: Using GitHub videos 13:13:47 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. 13:14:16 Topic: Work for this Week 13:15:06 Shawn: Update avaialbility survey and review other items in the WFTW - please review and comment on open issues. 13:15:57 ...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. 13:16:16 Topic: List of Courses 13:18:35 Carlos: We received comments from 3 reviewers, would like to understand if our ways to address were acceptable. 13:18:51 Sharron: Will do 13:18:56 Howard: Will do 13:19:51 have a great weekend everyone 13:19:58 trackbot, end meeting 13:19:58 Zakim, list attendees 13:19:58 As of this point the attendees have been Sharron, Vicki, Shawn, shadi, hdv, MarkPalmer, Jade, Karl, kevin, Howard, Daniel, JasonMcKee, CarlosD, Leticia, krisannekinney 13:20:06 RRSAgent, please draft minutes 13:20:06 I have made the request to generate https://www.w3.org/2021/04/16-eo-minutes.html trackbot 13:20:07 RRSAgent, bye 13:20:07 I see no action items