Education and Outreach Working Group Teleconference -- 27 Sep 2018

<Sharron> trackbot, start meeting

<trackbot> Meeting: Education and Outreach Working Group Teleconference

<trackbot> Date: 27 September 2018

<Sharron> Chair: Brent

<Sharron> Scribe: Sharron

Accessibility Statements

<shawn> Sharron: Went though with development team last week. Because it's so rough, didn't want to put it outwithout background.

<Brent> Prototype tool: https://www.accessibility.nl/statement/#home

Brent: Next version of the prototype and update in general to the resource. Wanted to let you guys have a chance kick the tires
... would love to hear what your reactions are to look at the resource. How does it strike you, what are your first impressions?
... focus on structure, presentation.
... anything missing or unnecessary?

<Vivienne> sorry, issues with connection

<Sarah> I'm done.

Brent: The dev team also asked if the heading structure, the expand/collpse section headers - did those make sense to everyone?

Amanda: I actually like the headers otehr thna the Why provide... Since that is the purpose of the page, it should be expanded by default.

Brent: Should it be able to be collpsed at all?

Amanda: It is not that much information, does not need to be collapsed at all.

Sarah: Not looking at content yet, but the How To Write a statement crosses over into what needs to be in it and who are you writing it for. That was the only section that did not gel for me with the setion title.
... other thing tht jumped out. This is a call to create the statement, am looking for where to create it. I had a bit of trouble matching up.

Bri: Agree there is a disconnect with what to do next.

<shawn> I think the issue is that the overall title is not clear.

Brent: It is not clear then that the home page was only informaitonal and it was confusing that to use the tool you ahd to use the button at the bottom.

Sarah: I gravitated to the headings and expanded and collpased sections and by the time I finished doing all that, the button and the purpose had escaped me.

<shawn> The overall title needs to be something along the lines of Web Accessibility Statement Generator Tool

Brent: Yes, the same experience for me, the headings are so big and appeakling it is hard to avoid jumping right into them and skipping over the purpose.
... So then on the next page Create Your statement, any thoguhts about that?
... not fully functional but overall what is your impression?

Sarah: Are we intending all sections to be expanded when we first visit the page?

Brent: My understanding is that it will nto be expanded.

Sarah: I liked the collapsed view becasue it works as a summary. If it will be expanded, it is quite a long form, summarize what will be asked for.

Brent: What about titles of the sections?
... is it what you expected?

Amanda: I almost think the one liner is not enough. For a long form like this maybe you should summarize what maight be useful such as the date of the last audit, exceptions, things like that.

<shawn> +1 to Amanda -- knowing ahead of time what infomration you need to fill out the form

Brent: ON the top of this page? or on the Home page? Where should it be included?

Amanda: Maybe right before the button on the first page to "Create Your statement" Or on this one?

Sarah: ON the start of the Generator page. Putting it on the home page might make it even more confusing about getting to the button.

Brent: How do you feel about how the information section titles, pre-content, etc compares to what is in the info boxes. Is it presented usefully? should that be differently presented?

Sarah: Starting with Basic Information wonder if it would benefit from a bit more chunking into smaller groups? Maybe even a group label to help with the distinctions?

Brent" Sub sections within Basic info?

Sarah: Consider reversing the URL/website name order

Brent: As you work your way down to complaints procedure, there is a box withpre-populated content. It is meant to be a kind of an example. Could copy and paste it you want to use it. How do you feel about the way there are some open comments, some pre-populated fields?

Sarah: I am allergic to placeholder text generally. As a personal view, I find it cluttered. Wonder if people will click less on the information box?

Brent: They are experimenting with different ways to provide suggestions, examples, support. Are there other ideas about that?

Sarah: I wonder if some of the information in the information boxes could be put directly on the page rather than hidden in boxes. And the helper text could be underneath as a "sample" without putting it within the placeholder. And the approval text might be better on the page rather than behind the info box toggle.

Brent: Other thoughts?

Robert: I like the idea of not hiding some of that helpful text behind the info icon. Maybe just allow the text to appear when that field gets focus. or could float along the right hand side a syou get to each section - it appears only when you get to the specific field. And what if the "sample statement" was avaialbe from a button to let the user have a generic statement to edit for thier own

environemnts.

Brent: Yes they were going to have two versions of sample a simple and more complex version.
... they are putting in placeholder text relevant to CityLights and maybe the preview is one that comes from the example text.
... The placeholder text is at a 4.6 contrast ratio to the black text.
... they use the word Example in front as well

Lewis: Some places it says example and some say "write here."
... should be consistant. I am concerned with how long some of the helper text is. If not behind the icon it will be very long indeed. May then really need smaller chunks.
... the preview moves some of the items so I had to look for it, not in the same sequence as when I put it in. Had to look 4 times to be sure it was included. Need to let people know that will happen.

Sarah: It seems like it is in some cases redundant and adds cognitive load for the sake of consistenacy - like email address, add email address here.

Amanda: I uderstand why they did this and is useful when it is a statement, complaint procedure, etc - for how it is generated but seems unecessary in some places, like email and others.

Sarah: No other social platforms than Twitter is included, seems limiting.

<shawn> scribe:Lewis

<scribe> scribe: Lewis

<shawn> scribe:Sarah

<Lewis> thanks Sarah

Brent: Question - There are companies that provide tools like this and have done research on the best way to design a form. Can we look at examples that provide best practice examples for forms like this (e.g. TurboTax)?

<rjolly> I'm all for exploring ways other folks have tackled similar interfaces.

<rjolly> And borrowing those ideas.

Amanda: Yes, lets look at this. Why reinvent the wheel?

Robert: It would be good for the form to be easy and self-explanatory. We can borrow what others have done successfully.
... Let's release a first version then improve on it as we go.

Bri: Amanda and Sarah provided good feedback.

Business Case update

<Brent> Latest Version of the Business Case: https://w3c.github.io/wai-bcase/teach-advocate/business-case/

Sharron: Nearing the final review of the business case. Thanking Amanda, Shawn and Eric for their help.
... Use github to lodge any remaining feedback that you may have.

<Vivienne> It is looking really good!

Shawn: Now is the time for feedback - ASAP! It is ready for thorough review before approval to publish.

Brent: Use links at the bottom of the resource to raise new issues in github. be specific in your issue title. For Editor's discreteness, but ED. It if is critical, add !! to the issue title.

Shawn: If you are not comfortable with github, please email your feedback using the email link at also at the bottom of the page.

Meeting time

Brent: We decided to stagger meetings for more flexibility based on timezones.

<Vivienne> It is never going to be a good time for everyone, but it is usually very difficult for Western Australia.

Brent: There was a decline in participation in the current time-slot (Fridays).
... Should we keep meeting at this time or should we change the time to suit more people?

<Vivienne> This time slot isn't too bad for me, but it is very early (sigh)

Amanda: WA does not have daylight saving so during winter meetings are at 5am. During spring and summer meetings are at 6am which is more reasonable.
... Happy to meet late afternoon or evening but makes it difficult for everyone else.
... If we pushed it later by an hour, I would be happy with that but I wont speak for Vivienne.

Brent: To sum up, it would be a bit more palatable if we pushed it one hour later.

Sarah: Conveyed Vivienne's message that 1 hour later is fine.

<shawn> [ We would need to see if an hour later would work for other timezones ]

<Brent> me/ says bye robert

Sarah: EST (Australia) will be going into daylight saving which will push things back by an hour (we think!).
... Intopia will try make sure either myself or Andrew are online.
... Will mean that it is harder to manage client work since we will be out for a half-day.

Brent: Thank you for the feedback. Andrew and Vivienne, if you have additional information please email the planning team.

Work for this week and weekly survey.

Brent: Weekly survey will be reviewing resolution to changing references from WCAG 2.0 to WCAG.
... In content where it is important to reference the version number, we would do so.

https://www.w3.org/2018/09/21-eo-minutes.html#item02

<shawn> WCAG 1.0 is being superseded this year.

Brent: If you do not have an issue with this resolution, please +1.

<AMace> +1 no issue with that

<Lewis> +1

<shawn> Bri +1

Brent: We will pull together a quick survey with minutes and perhaps a few questions about the business case. Brent will check with Sharron.
... Other business?
... Nope!
... Thank you you for the good discussion, and good feedback on the accessibility statement generator.

<shawn> trackbot, end meeting

- DRAFT -

Education and Outreach Working Group Teleconference

27 Sep 2018

Attendees

Contents

Accessibility Statements

Business Case update

Meeting time

Work for this week and weekly survey.

Summary of Action Items

Summary of Resolutions

Scribe.perl diagnostic output