Education and Outreach Working Group Teleconference -- 05 Jul 2017

<scribe> Scribe: Brent

James calls meeting to order.

James: Saw emails from Sharron and Shawn earlier today. Not everyone has read them. Can we recap?
... Going to to share screen and talk through IA documentation.
... Did not send out the SimpleMind Pro mind mapping document.
... This tool helped me get to the other PDF document with IA structure showing top level navigation and subpages.

James talked through the structure of the proposed new IA.

James: The idea behind the new IA is about findability.

<yatil> [ Eric really likes the IA. ]

James: Questions about the AI proposal?

Shawn: Thank you for sending in multiple format. They were all very helpful to get the feel for the different implementation.

<Zakim> shawn-hiding, you wanted to ask James to send to WSTF list, or OK someone else too and to note that Tips was explicitly designed for *tasks*, *not roles* and to note the first tool

Shawn: For the Tips for Getting Started... We set out to design these for "tasks" instead of "roles." Don't know that it matters much so far, but we just need to keep this in mind.

James: I see where you are going with that comment. May need to add some good copy on the landing page to address or clarify.

Shawn: As soon as you are comfortable with the IA documents, this information needs to be sent to the Task Force email so that it will be on record.
... Also would like us to think some more about "New to Accessibility" title. maybe basics, or introduction...

James: Agree this needs some thought.
... Also about Evaluation vs. Testing. May be better using both words to help catch those that are looking from different perspectives. Also helps with visual balance.

Sharron: Also, as Shawn suggested, another thing that could help with the visual balance would be to swap "Designing & Writing" with "Developing."

James: We put these in this specific order in which you would progress through accessibility.

Charlotte: Agree with the current order.

Shawn: Not too worried about findability, more concerned with peoples perspective of what content we have (or don't have).
... Would like us to test the different versions.

Eric: I don't think the swapping will matter too much. I think the order is logical progression as is.

Sharron: I didn't see the importance of the sequence immediately until it was pointed out. Now I understand the sequence and like it.

James: The "why" of the order was to try and make a statement about the order of putting this to work. Modeling the thinking process of accessibility work.

Shawn: I am okay with the current order.

James reading through the final IA email thread that came from Sharron to discuss and decide some issues/recommendations.

James: First issue, change WAI Guidelines to "Guidelines/Standards"

<shawn-hiding> thread: https://lists.w3.org/Archives/Public/public-wai-eo-site/2017Jul/0000.html, https://lists.w3.org/Archives/Public/public-wai-eo-site/2017Jul/0001.html

James: Okay, not hearing any issues with the change.
... Second, remove the word "accessibility" from some of the main nav titles. Seems redundant.

Charlotte: Would like to test that. I think that some users who come may have some issues with the titles not having accessibility.
... Lets test the following, 1) standard terms, 2) adding "ing" to the terms, 3) keeping Accessibiltiy.

James: We can do that.
... Third, instead of "I'm new to Accessibility," possibly use Accessibility Fundamentals, or Basics.

<yatil> [ Eric prefers “Testing and Evaluating” over “Testing/Evaluating” – sounds more human an less technical. ]

James: Fourth, Testing and Evaluation. What to name it. Think we need to do some more testing on this one as well.

Charlotte: I will be working out some schedules for testing in the near future on the latest IA version. Once schedules are set, then will send out calendar of testing so that people can come observe.
... Question, if we complete the IA and start editing content, will we be able to have a rough prototype of the site done by mid-september in time for some solid testing.
... How many people do we have that can start with the editing?

Sharron: We have touched on the subject in email and we will be communicating about this in upcoming meetings.

James: We have about 60 resources that need at least a minimal level of review. We will be on a tight timeline to get this complete.
... Charlotte will pull together an editorial calendar with top priority resources up at the top so that we can get through the most important first.

Shawn: I would like to make some comments on that. When should I do that?

Charlotte: Let me get the first editorial calendar draft complete and then let you comment on it.

Shawn: Want to back up the the Evaluating and Testing nav name.
... If they are the same then use the
... "/", if they are not the same then use the "and".
... Another topic is the "Teach." Do we want a second word added to that?

Shawn had suggesting "training" or "advocating" in a previous email.

James: Currently the content is about teaching. If we can get more content we can definately rename it.
... The word "train" isn't really clear. Once we get more content the meaning of that section may change.

Shawn: We do have people working on new content that would fall in that arrea. They are scheduled to be done with it in August.

James: Keep thinking about the names because they are not set in stone and can change as the site changes.

WAI Sitemap to New IA spreadsheet.

James: Columns C through F are the current site map of the current WAI site.
... Column A is to verify that we included the topic in the new IA.
... Comlumn B is the number code for tracability from the new org chart IA to the old IA.
... Column G is if there was a rename that was/is suggested.
... If there was a name change suggestion, it will also show up as a text bubble in the PDF visual map.
... Some of the name change recommendatoins will need to be talked through. (example of the How people with Disabilities Use the Web resource). Streamlining it may help us to remove or condense some of the landing pages in the new site. Clear names will help with targeting findability.
... Only renamed resources when I felt we really needed to. Willing to discuss. If we are aiming for the future and more posterity, we really need to use names that will truly describe the resource.
... If rows are colored RED, then there is a suggestion for archive or merging.

<shawn-hiding> [ note about "Easy Checks" -> intro to Eval : Most of the target audience for this resource will not go on to do more robust eval -- they will often just do this level. They don't want a thorough eval, just to get a general idea. ]

James: Charlotte is going to use this spreadsheet to inform the editorial calendar.

Eric: Thank you so much for doing all of this. A lot of work.
... See some fringe issues that may come up with some of the archiving, but we can deal with them as they come up. I am looking forward to working on this with the team.

<Zakim> shawn-hiding, you wanted to ask about Testing/Evaluating instead of Testing and Evaluating and to check w/ Charlotte

James: Anything else? Very happy that you are all pleased with the draft IA. Charlotte and I are both really excited that we got through this.

Shawn: Charlotte are you making the next pass on the spreadsheet?

Charlotte: I am going to make it a seperate spreadsheet or an additional sheet in the current document?

Shawn: Crossreferencing is very helpful.

Charlotte: I will tweak and send a new version for you to make comments on.

James: Thanks everyone. Happy about progress. Meeting adjourned.

<yatil> trackbot, end meeting

- DRAFT -

Education and Outreach Working Group Teleconference

05 Jul 2017

Attendees

Contents

WAI Sitemap to New IA spreadsheet.

Summary of Action Items

Summary of Resolutions

Scribe.perl diagnostic output