W3C

- DRAFT -

Education and Outreach Working Group Teleconference

12 May 2016

See also: IRC log

Attendees

Present
Katie, Haritos-Shea, EricE, Howard, shawn, JeffKline, Susan, Sharron, James, Denis, Shadi(phone)
Regrets
Chair
Sharron
Scribe
Howard, shawn

Contents


<Ryladog> OK

<Howard> scribe:Howard

Website Redesign

Jeff: policy driven adoption...
... rather than having just technical rules, there should be governance procedures.
... 6 point framework. Focused into the vendor space. Questionnaire is part of the PDA.

Anna Belle: 6 basic steps of redesign.

Sharron: all our goals need to be measurable.

Anna Belle: want to get to one primary goal and then secondary ones.

Susan: goal to update the site to make it more clear and engaging to users.
... Plain language, tone.

Dennis: anyone can come to site and can identify the things that are relevant to them.
... Don't have to search through everything to find what is relevant.

Susan: want site to be number 1 place to go to for web accessibility.

James: increase traffic and reduce drop off.
... increase satisfaction.
... Improve credibility.

Jeff: Would like to see multiple entry modes to increase exposure to success criteria,
... intermediate and advanced. Structure so that they can get what they need.

Anna Belle: redesign should establish our leadership in modern web community...

scribe: Model accessibility. Seen as an authority for a11y.

Eric: WAI site should have comprehensive overview of web accessibility.
... right now it's very WCAG focused. Need to be broader - cover ATAG for example.

Dennis: should have comprehensive role-based information.

James: we should provide comprehensive role-based content for web a11y.

<shadi> +1

Anna Belle: site should inspire visitors to implement web accessibility...

Shawn: site should be referenced in other expert's presentations.

<shadi> [[hearing three aspects: presentation of content (eg. "engaging"), organization and findability of content (eg. "identify" and "role-based"), and more content (eg. "comprehensive")]]

<Ryladog> organization and findability of content

<Ryladog> my microphone is dead

<Ryladog> organization and findability of content

<Ryladog> yes I am

<shawn> s/

Jeff: have #1 go to place for web a11y as overall goal with
... bullet points for sub-goals.

Denis: should keep in mind that EO should do more outreach.

Anna Belle: how do you support folks who are already engaged & inspired?

Create w3.org/WAI/ as the first go-to place for web-a11y

Anna Belle: Who are our 3 main audiences?

Susan: Important to consider roles also besides level of expertise.

<Ryladog> Those who make the web..

<shadi> +1 to leaders

<Zakim> shadi, you wanted to ask about managers, policy makers, and advocates

James: may want to consider how they access the content. Developers don't look at content/resources ...
... the same as other users.

<Ryladog> governements and business should handle their own procurement requirements resources....it should be light for now on that topic

Shadi: distinction between developers and policy makers/administrators.

<shadi> [[distinction between managers *in* accessibility and broader managers/policy makers/execs

Sharron: categories should be wide enough to encompass various groups:
... technical/hands-on
... leadership
... advocates/users
... decision makers

<yatil> q

James: need to make personas for our audiences.
... Limit to 5 or 6 and need to be modern.

Eric: Doers, planners, advocates
... policy makers not a primary audience. Can get info from our site ...

<Zakim> yatil, you wanted to support policy as a sec audience

Eric: but are secondary audience...

Shadi: which audience do we most want to address ...
... because they make the web accessible.

Jeff: policy makers would be far down on the list. Not a primary place ...
... a policy maker would go to.

Denis: remember that always come up that developers and designers come to the site ...
... and immediately turn away because of it's design...

subtopic: Data / Measurement

Caleb: have to start off with capturing traffic...
... and where do you fall with SERP rating.
... Traffic: where it's coming from ...
... define specific funnels depending on types of information ...

users are looking for/visiting.

<dboudreau> (SERP = Search engine results page)

scribe: Organic search traffic vs. via links/referrals.

Caleb: Referrals are more important, more valuable for building traffic/reputation.

User testing/ Usability testing

Susan: much more interested where they come from and how ...
... long they stay on the site.

Jeff: specific analytics on how many/who goes to different areas, resources.

James: What are the drop-off pages and why.

Eric: another way to measure is to see how well we are integrating ...
... ATAG and other standards.

Caleb: should we be measuring the community by looking at ...
... the top 50 sites in the world?

James: Is our job to influence, to make the web more accessible?

Shawn: Should we measure our mentions in other places: blogs, twitter, etc.?

Analytics should be a top priority for data/measurement.

Caleb: Should we specify what analytics we will try to capture - what areas of data.

Susan: Put specific tool to the side for now?

<shawn> tool: PIWIK

Shawn: need to specify what data we want from the tool.

<dboudreau> http://piwik.org/

<dboudreau> http://piwik.org/

<dboudreau> PIWIK DEMO: http://demo.piwik.org/index.php?module=CoreHome&action=index&idSite=7&period=day&date=yesterday#?module=Dashboard&action=embeddedIndex&idSite=7&period=day&date=yesterday&idDashboard=1

<Caleb> http://demo.piwik.org

subtopic: Information Architecture

Anna Belle: What is information architecture?

scribe: broader than just navigation.

Denis: what about Interaction Design? The needs of different users.

<yatil> s|s/my microphone is dead||

Jeff: Do we need an information architect specialist?

James: he and Caleb have those skills and they have tools to ...
... facilitate card sorting and other IA tools?

q

<yatil> + Howard

Anna Belle: do we want to make having a search box a goal?

<Caleb> +1 for search

<dboudreau> +1 for search

<Susan> +1 for search

<yatil> https://duckduckgo.com/?q=Tutorials+site%3Ahttps%3A%2F%2Fwww.w3.org%2FWAI%2F

<Susan> -q

<yatil> +1 for search

+1 to search

Jeff: do we need an Information Architect?

Shawn: we do have skills on the EOWG for IA.

Eric: might want to look into the possibility to add goal of adding a IA to the team.

<Susan> https://www.w3.org/developers/

Anna Belle: navigation, site map, ...

Denis: might want non-traditional navigation.

<Susan> +1 yatil re: getting into too much detail

Anna Belle: suggests having search, breadcrumbs ...

<shawn> Shawn: really good search might be our highest priority

Shawn: Search may be our highest priority.

<dboudreau> discovr - https://itunes.apple.com/us/app/discovr-discover-new-music/id412768094?mt=8

<shawn> Shawn: "really good search" means doing things like tagging so Tutorials comes up first, etc.

Caleb: user testing and talking to users needs to drive IA.

subtopic: Visual Design

Anna Belle: step 1: getting clear on style of site.

scribe: distill down the style to 2 or 3 adjectives.
... Simplify - central goal. Focus on essential elements.
... get rid of non-essentials. Mobile first.
... probably don't get too many casual readers at this point.

<Susan> -q

Anna Belle: What adjectives do we want to describe our style & tone?

Shawn: authoritative, credible, inspiring.

Caleb: Clear.

Eric: Fun.

Shawn: welcoming.

Jeff: supportive.

Susan: knowledgeable, encouraging, modern.

Katie: engaging.

James: reliable.

Eric: trustworthy.

Susan: universal.

Eric: global.

James: efficient.

immersive

leading

<yatil> http://i.imgur.com/zgWYG5B.jpg

<yatil> Here are the possibilities for Shadi and Katie!

current

authoritative

engaging 7, reliable 6, clear 5

engaging, reliable/credible, clear

engaging/empowering, reliable/credible, clear

engaging/empowering, reliable/credible, clear/practical

<Zakim> dboudreau, you wanted to support logo effort

<Caleb> Ocupop created the HTML5 logo

<dboudreau> Denis: supporting the idea of going through a logo design effort again, maybe contacting the same designer who created the HTML 5 and CSS 3 logos

<Caleb> http://ocupop.com

<Caleb> Background on the HTML5 logo creation: underconsideration.com/brandnew/archives/html5_validates_with_new_logo.php

Shawn: Suggest we work on the organization of the "Getting Started with Web Accessibility" page

<James> Re: logo: http://www.w3.org/blog/2011/01/an-html5-logo/

<scribe> scribe: Howard

Web Redesign Continued

subtopic: methodology

create personas fro our audiences

Anna Belle: baseline analytics

scribe: define deliverables

Eric: suggested methodologies/deliverables - Urgent technologies

- github base framework, issue management

Eric: longterm technology goals -

consolidation under PHP or some other standardized scripting/database language

Jeff: Might be helpful to right down a set of assumptions.
... as part of the methodology about the technologies we'll be using.

Sharron: we know we will use github, the wiki.

Eric: WAI site is completely separate from W3C as far as he knows.

Sharron: other assumptions - low budget,
... volunteer labor.
... usability testing? Where will funding come from?

Howard: could do user testing at AHG, AccessU, other conferences.

Jeff: What about remote testing?

Brent: Likes the goals the group came up with.

Anna Belle: most concerned about analytics. Crucial to do this before we start the redesign.

James: tasks for the redesign - Personas, architecture, analytics/ user testing, IA, Visual

subtopic: task - Personas

- looking at the existing personas & our audience. Updating them as needed.

- (something someone can take on)

scribe: (see photo of time chart created by James)

Deadlines - Personas (May),

scribe: Analytics (June)
... User Testing (July)

Shawn: need to note that policy content is a priority - it's already overdue

James, etc.: we'll dedicate 2 months to catching up on content that is behind then start the tasks for the redesign.

Shawn: can reuse URLs. Just can't have 404s.

can do redirects.

Caleb: should do an inventory/map of all URLs used on the site.

Shawn: her or Eric will put the script required for Analytics for each of the 75 eo pages.

<Caleb> piwik.org/docs/installation

<Caleb> Simple JS snippet to include on every page

James: can do a second round of analytics in July for customized data collection.

Shawn: overdue resource docs: policies (Wayne), Easy Checks, Tutorials.
... Easy Checks, Tutorials, simply need to be completed.
... if the working group decides to change the priorities of docs required for charter, we can come to consensus and record a decision on that
... in order to focus first on redesign.

Caleb: can get volunteer designers to work on logo, on mood boards/colors/ideation.
... deadline of July - preliminary exploration of visual redesign.

Shawn: should check on data from recent WCAG survey to see if any useful info

James: task analysis for IA, mapping, testing - ~ July - November.
... Technical Architecture -

Caleb: Linux server currently
... have Eric provide his vision of what technical resources we need.

Denis - will task analysis, mapping, testing for IA (timeline: July - Oct/Nov,)

<Susan> https://mail.google.com/mail/u/0/?ui=2&ik=f344b921d7&view=att&th=154a68451c79ab2c&attid=0.1&disp=safe&zw

subtopic: Personas

Meta description for EOWG pages

Proposal: ....
...

<shadi> +1 to proposal

<shawn> Proposal: OK to add meta data (such as description) to the perspectives pages to provide text & images for social media, etc?

<Susan> it's not muted

Group voted to create new personas.

<Susan> +1

<shawn> +1

<Susan> +1 for meta data

<shadi> +1

<dboudreau> +1

<shawn> +1 from Eric

+1 to metadata

<Caleb> +1

<Sharron> +1 metadata

+1 from Eric for metadata

RESOLUTION: OK to add meta data (such as description) to the perspectives pages to provide text & images for social media, etc?

Creating New Personas

Sharron: our 3 audience categories - Doers, Planners, Advocates
... How many personas do we need for Doers?

Jeff: Doers will probably be 75% of site users and Planners & Advocates the remaining 25%.

Sharron: So 3 Doer personas, 1 Planner, 1 Advocate.

<yatil> Evaluators, Designers, Developers?

<yatil> Content creators?

<dboudreau> Some questions to ask while running the personas’ research (http://www.usability.gov/how-to-and-tools/methods/personas.html)

Sharron: 2 Doers - developers/designers, testers?

Shawn: social media outlets - have vimeo channel. How important to have on YouTube?

Consensus is that YouTube is crucial - has the larger audience.

Shawn: we should also put on Vimeo.

Eric: We can put on both but YouTube is much wider audience.

<yatil> You also have to see that you don't get stuff freebooted.

<shawn> Thank you for Knowbility hosting!

<Sharron> trackbot, end meeting

Summary of Action Items

Summary of Resolutions

  1. OK to add meta data (such as description) to the perspectives pages to provide text & images for social media, etc?
[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.144 (CVS log)
$Date: 2016/05/12 21:01:58 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.144  of Date: 2015/11/17 08:39:34  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/.me missed that//
Succeeded: s/Can do it if you give me the meeting number and link//
WARNING: Bad s/// command: s/my microphone is dead
Succeeded: s/rganization/o rganization/
Succeeded: s/are you there Katie?//
Succeeded: s/o rganization/organization/
Succeeded: s/sub-goal/sub-goals/
Succeeded: s|WAI.org|w3.org/WAI/|
Succeeded: s/Dennis/Denis/
Succeeded: s/New motto: W3C WAI – We are the truth!//
Succeeded: s/rssagent, draft minutes//
Succeeded: s/preesent+ JeffKline//
Succeeded: s/Jeff Klein:/Jeff:/
Succeeded: s/my microphone is dead//
FAILED: s|s/my microphone is dead||
Succeeded: s/q//
Succeeded: s/on the team for IA./on the EOWG for IA./
Succeeded: s/should add/might want to look into the possibility to add/
Succeeded: s/need to note that policy content is a priority - risk of being overdue./need to note that policy content is a priority - it's already overdue/
Succeeded: s/'re/'ll/
Succeeded: s/can/can do redirects./
Succeeded: s/we can take a vote,/we can come to consensus and record a decision on that/
Succeeded: s/should check on data from recent WCAG survey on how to use WAI tools/should check on data from recent WCAG survey to see if any useful info/
Succeeded: s/is it okay for Caleb & Eric to put code into just the Perspectives pages so that it can be//
Succeeded: s/tracked within social media.//
Found Scribe: Howard
Inferring ScribeNick: Howard
Found Scribe: Howard
Inferring ScribeNick: Howard
Found Scribe: shawn
Inferring ScribeNick: shawn
Found Scribe: Howard
Inferring ScribeNick: Howard
Scribes: Howard, shawn
ScribeNicks: Howard, shawn
Default Present: Katie, Haritos-Shea, EricE, Howard, shawn, JeffKline, Susan, Sharron, James, Denis, Shadi(phone)
Present: Katie Haritos-Shea EricE Howard shawn JeffKline Susan Sharron James Denis Shadi(phone)

WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Found Date: 12 May 2016
Guessing minutes URL: http://www.w3.org/2016/05/12-eo-minutes.html
People with action items: 

[End of scribe.perl diagnostic output]