Usability testing Oct 2017
Prototype for usability testing
Test Plan
- Final Version 3: 3 Word doc
- Version 2 with comments: 2 Word doc
- Version 1 comments: 1 Word doc
- Test plan draft 1
Things to watch for
- General
- Is the all the navigation throughout clear, including what's available, where they are, where they've already been, where they can go next?
- Is the non-primary navigation clear, e.g., in-page navigation, related pages, etc.?
- Can users find a page that they previously looked at — especially if they got to it from a home page feature box?
- Navigation interaction — How do users understand and navigate the menu items with additional flyouts? e.g., under "Accessibility Fundamentals", "How People with Disabilities Use the Web" is clickable and also flysout to reveal additional nav items. Do users know "How People with Disabilities Use the Web" is clickable? Do they click it, or go straight to the sub-pages?
- Back to Top — Do users expect it to go to the H1 (which it currently does), or to the top of the page? Do they want it to go to the top of the page, e.g., to access overall navigation?
Home page
- Video — What do participants expect to happen when they click on the video? Are they OK with the interaction of opening a new page?
- News — Do participants get down to the News section on the home page?
Other Tips and Perspectives Videos
- Perspectives — If/when participants go to the Perspective page, do they figure out easily that it is one of 10, and they can see the other 10?
- Tips — If/when participants follow the link for the Tip, are they comfortable that it drops them in the middle of a page? Do they figure out easily that there are other Tips pages?
Important: Audiences and Tasks not included
It's important that we don't forget that these types of audiences and tasks are not included in this particular usability study (nor the prototype much yet):
- I'm a W3C Advisory Committee Representative and I want to see what W3C is doing on accessibility in Working Groups, Interest Groups, and Community Groups — both within WAI and throughout other areas of W3C.
- I'm a WG participant and I need to look up stuff related to our WG.
- I'm an international policy maker and I need to know the status of accessibility-related standards in development.
- I'm a potential WAI funder and I want to see the XYZ Working Group Charter.
- I am a post-doc researcher and I need to know how to evaluate accessibility and report results.
Known prototype issues
see list at https://www.w3.org/WAI/EO/wiki/Redesign_-_October_Revisions#Prototype_issues
Observations from UT
NOTE: please put specific suggestions of things to address in Redesign - October Revisions
{fyi, Shawn has tons more, but might not get to writing them up in a consumable way :-(}
Home page
- "When I come back to the home page, I want to be able to find what was there before. I wouldn't expect things to change." — Norah
- Is there any home page on the web where this is the case? The primary function of a home page is to promote different things over time. – Eric
- "Test & Evaluate" - several UT participants thought this was an automated test. Maybe the word "test" is the issue? Change brainstorms:
- Assess & Evaluate
- How to test
Misc
- accessibility = blind myth — saw myth that accessibility is screen reader only
Pages in Tasks
(just fyi so we could prioritize those for UT)
- Introduction to Accessibility
- Business Case
- Easy Checks
- How People with Disabilities Use the Web: Diverse Abilities and Barriers
- ? How People with Disabilities Use the Web: Tools and Techniques
- Tutorials – Carousels
- Tips for Designing
- Tips for Writing
- Tutorials - Forms - User Notifications
- Accessible Audio and Video
- WAI-ARIA Overview ; WAI-ARIA Dev Intro
- ? How to Meet WCAG 2.0 Quick Reference
- ? Developing Organizational Policies on Web Accessibility
- ? Laws & Policies