Important note: This Wiki page is edited by participants of the EOWG. It does not necessarily represent consensus and it may have incorrect information or information that is not supported by other Working Group participants, WAI, or W3C. It may also have some very useful information.


WAI Site Redesign Notes

From Education & Outreach
Jump to: navigation, search
The information on this page was preliminary, not agreed on by the Task Force or EOWG.

Outcomes from May 2016 Face to Face

23 May survey results with open issues.

Goals

There is one central goal to the WAI site redesign. It is:
Create the WAI site as the #1 Go-To place for web accessibility.

Secondary goals include:

  • Inspire people to care about web accessibility
  • Engage them in accessibility solutions
  • Empower web professionals with tools they need to be effective in creating and improving accessible web products.
  • Provide multiple entry points and pathways for people across varied roles
...other suggestions in planning wiki.

Audience

Primary audiences:

  • Doers (includes developers, designers,content creators, web administrators, etc)
  • Planners
  • Advocates
...distilled from planning brainstorm

Secondary audience:

  • Policy makers

Visual design

The new site will have the following characteristics:

  • Engaging/empowering
  • Reliable/credible
  • Practical/clear

Methodology

  • Personas consistent with our identified audiences
  • Baseline analytics
  • Map deliverables to EO participants
  • Assumptions
    • EOWG oversight
    • checkpoints with Judy
    • minimal funding
    • reliance on volunteers, donated resources
  • Urgent Technologies
    • wiki
    • GitHub issue management
    •  ??more??
  • Longer term tech issues
    • CMS
    • Standardized scripting

Draft Plan for 2016

See also Task Gant chart on GoogleSheets

Task Lead Support Start date End date
Create Personas for
Primary Audiences
Sharron Elisa Miller 12 May 30 May
Example Example Example Example Example
Example Example Example Example Example
Example Example Example Example Example
Example Example Example Example Example
Example Example Example Example Example
Example Example Example Example Example
Example Example Example Example Example
Example Example Example Example Example
Example Example Example Example Example
Example Example Example Example Example
Example Example Example Example Example

Face to Face Flip Charts

Goals f2f

The goal of the website was determined to be:

WAI site becomes the first (#1) go-to place for web accessibility

This is based on the following sub-goals:

  • Inspire and engage people to care about web accessibility
  • Update site, making it more clear and engaging to users through tone and language
  • Anyone can ID what's relevant to them
  • Increase traffic/satisfaction
  • Organization of content (decreases drop-off)
  • Improve credibility (reflects leadership in modern web community, demonstrates authority)
  • Provide multiple entry modes to approach SCs
  • Model accessibility best practices
  • Provide comprehensive role-based content for web accessibility
  • Provide support materials

Audience f2f

The group brainstormed audiences with the goal of choosing just three primary and additional secondary audiences. Based on the brainstorm below, the determined audiences are as follows:

  1. Primary Audience
    • Doers
    • Planners
    • Advocates
  2. Secondary Audience
    • Policy Makers

This was based on the following data:

  • Roles involved in web creation:
    • Devs
    • Designers
    • PM
    • Admin
    • Content
  • Levels:
    • Beginner
    • Intermediate
    • Advanced
  • Leaders
  • Procurement
  • Technical (hands on)
  • Advocates (users)
  • Decision makers

Information Architecture f2f

What is information architecture (IA)?

  • The highest priority for the IA of the site is to have really good search ability
  • Users know:
  1. Where they are
  2. How to get where they want to go
  • Employs different techniques/categories
  • How do GitHub, Wiki, etc. work into our thinking about the redesign?
  • How do we address interaction design?
  • What is the special place of Home Page?
  • How to implement search?
  • Breadcrumbs

Do we need IA?

  • Navigation - Yes
  • Site map - Yes
  • Breadcrumbs - Maybe
  • Search - Yes!

Data/Measurement f2f

How do we measure data?

  • Capture traffic
  • Ratings SERP
  • Where is traffic coming from?
  • Define funnels
  • Referral vs. direct links vs. organic search

Set baseline through:

  • Surveys
    • User testing
    • Usability testing

[Discussed that UT was not needed before redesign – that it would be more efficient to wait and do UT on prototypes.]

  • Not too much reliance on SEO analytics (how long do they stay, etc.)
  • Specific, sectional data
  • Judge our effectiveness by how top 50 sites perform in accessibility

Open question: What data do we want?

Methodology f2f

  • Create personas for our audiences
  • Baseline analytics
  • Deliverables
  • Urgent technologies
    • GitHub basic framework issue management
    • Wiki

Assumptions:

  • Checkpoints with Judy
  • Minimal funding
  • Reliance on volunteers
  • Usability testing funding?

Long-term tech considerations:

  • CMs
  • Standardized scripting

Quick Fixes f2f

  • Content updates
  • Navigation reorganization

[Smart Search]

Visual Design f2f

Participants brainstormed practical adjectives and then revisited them with three votes. Based on the votes below, the group chose to use 3 word pairs as the final description of what should be conveyed.

Visual design should be: Engaging/Inspiring, Reliable/Credible, Clear/Practical based on following ranking of the adjective brainstorm:

  • Engaging - 7 votes
  • Reliable - 6 votes
  • Clear - 5 votes
  • Inspiring - 4 votes
  • Credible - 3 votes
  • Modern - 3 votes
  • Comprehensive - 3 votes
  • Encouraging - 1 vote
  • Supportive - 1 vote
  • Welcoming - 1 vote
  • Efficient - 1 vote
  • Current - 1 vote
  • Robust - 0
  • Knowledgeable
  • Comprehensive
  • Global
  • Leading
  • Immersive
  • Fun
  • Warm
  • Trustworthy

Wiki-based redesign brainstorm (prior to F2F)

This is a record of the brainstorm for the re-design plans for the WAI website.
Please use this page to capture your ideas, hopes, and ability to contribute to the redesign and implementation of a new web site for w3.org/WAI. The work that EOWG is doing on the existing resources will help us understand and prioritize content management.

Please use this page to capture your ideas, hopes, and ability to contribute to the redesign and implementation of a new web site for w3.org/WAI. The work that EOWG is doing on the existing resources will help us understand and prioritize content management.

This is a brainstorming page There are a few general categories but please add more, change the headings, do whatever you feel reflects the things we need to think about to develop a workplan to get us to a new WAI web site. Thank you!

If it helps for reference, please review work done by EOWG for the last redesign in 2005, including:

  1. WAI site analysis summary
  2. WAI site user list
  3. WAI site task List

Considering previous analysis, please contribute your thoughts about how to approach the current redesign project to make the most of the talents of this groups and others we might enlist. If a category is missing here, feel free to

Goals (b4f2f)

  • Create web presence that reflects leadership in modern web community
  • Model accessibility and best practice
  • Improve ability to find role-based pathways through materials
  • Get rid of the left hand navigation, it dates the site and takes up 25% of the real estate. Can we find a different way for users to navigate the resources? {Brent, 2 May 2016}
  • Choose modern web site colors, white background for main content areas. Change the image of the bridge, don't need images, use graphics instead. Examples in W3C that are much more modern:
  • Attempt to consolidate or group architecturally similar resources, for example: all of the resources that are introductory or getting started, all of the resources that are technical/coding, all resources for leadership and policy. This may not work for everything, but it could help clean up some areas.{Brent, 2 May 2016}
  • Design an entry page (start point) for all that quickly guides or point people to find what they came for (to assist with the third bullet goal). {Brent, 2 May 2016}
  • I’d like colors that pop, bold large text, easy to read {EricE, 3 May 2016}
  • I think we should have more content that is easy to reuse, for example we could have presentation slides for each of the getting started tips to just download (as an omg, pdf?) and use in their own presentations. {EricE, 3 May 2016}
  • Ensure that we take into consideration those with a cognitive disability when designing the site. {Adina, 4 May 2016}
  • Build a site that speaks credibility to our users. We'll be seen as an authority on what we cover if we have a site that impresses from a visual, content, and experience perspective. {James, 4 May 2016}
  • Increase visits, reduce drop-offs, increase satisfaction. Set up analytics and satisfaction surveys now and when we publish the new site, measure for improvement. {James, 4 May 2016}
    • +1 to analytics {Sharron, 5 May 2016}
  • Improve UX of website - conduct formal Usability testing now and during design and after publication, measure for improvement. {James, 4 May 2016}
  • BIG goal - create a vehicle that is highly effective as an outreach tool, one that people read and look forward to. Improve the outreach mission of EOWG by showcasing all WAI resources in a more interactive and responsive fashion. {Sharron, May 5}
  • Vision - From 2005 redesign, see Vision. How is vision for this redesign the same and different? {Shawn, 6 May 2016}
  • Comment {Name, date}

Leadership (b4f2f)

Use this section to volunteer for your role in the redesign process.

  • Brent | Design brainstorming and wire-framing (with a group) | 1 hour per week
  • Brent | Content edit and review | 1 hour per week
  • Brent | User Testing and Feedback | 1 hour per week -or- as needed, including a few members of my Pearson Education team
  • Adina | Run initial story (journey) mapping with personas (with a group) | 1 hour per week
  • Adina | Design brainstorming and wire-framing (with a group) | 1 hour per week
  • Adina | User Testing and Feedback | 1 hour per week as necessary
  • Susan | Content edit and review | 2 hours per week
  • Susan | Testing development site (especially on mobile) | as needed
  • Name | Role | Hours per week, other resources to contribute

Methodology (b4f2f)

Use this section to suggest technologies and methodologies to use in the redesign/development process.

  • Site is tested on mobile with a switch device (along with JAWS, NVDA, VO, DragonNaturallySpeaking, keyboard, etc.){Adina, 2 May 2016}
  • Align to technology used on W3C site - define it, assign EO participant to be liaison, post regularly to W3C blog for outreach to our internal community as well as rest of the world. {Sharron, 5 May 2016}
  • Consider replacing current Announcement process with a dedicated EOWG blog for that purpose. {Sharron, 5 May 2016}
  • Base decisions on real data, which means creating a user testing plan, including uability to gather baseline data, to inform the redesign work, and for the longer term {Sharron, May11}
  • Suggestion/comment {Name, Date}

Constraints (b4f2f)

What are the constraints that we face and how can we best address them?

  • Name | Perceived constraint | Suggestion for mediation (if one occurs)
  • Sharron | No budget. | Mediation suggestion: beg
  • Sharron | Much (all?) of the work will be done by volunteers, hard to maintain schedules, timelines, progress. | Mediation suggestion: assign staff supervision, enlist committed volunteers, use GitHub
  • Sharron | Design elements throughout the site are inconsistent, challenge is to address all needs with consistent design | Not sure how to address this, hoping for some inspired design thinking at the F2F.
  • James | Design by committee syndrome. | Mediation suggestion: rely heavily on data driven decisions (really get to know our users before beginning), limit EO reviews, train EO staff to only raise major concerns...