Regrets: usability testing in Austin

As it turns out, Brent was right and I will *not* be in Austin for the
usability sessions.  Regrets

On Wed, Aug 23, 2017 at 1:02 PM, Shawn Henry <shawn@w3.org> wrote:

> Charlotte, Demographic notes are at the end... :-)
>
> -------- Forwarded Message --------
> Date: Thu, 10 Aug 2017 12:43:50 -0500
>
>
> I took a first pass at some research questions and tasks (tweaked from
> earlier list) and participant demographics for the usability testing. All
> open for discussion, of course.
>
> Research questions:
> •       How do people interact with the home page, and the sub-pages?
> Where does their focus go and pause? What do they click on?
> •       Think-out-loud reactions to the visual design, content areas, nav,
> etc.
> •       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.
>
>
> Tasks:
> 1.      Help! We have to make our website accessible and I don't even know
> where to start!
> 2.      I need to check if my website meets accessibility standards.
> 3.      I'm looking for mobile accessibility guidelines.
> 4.      Should I use ARIA or WCAG?
> 5.      What is a screen reader and how do they work?
> 6.      I'm giving a presentation on accessibility and want some basic
> info about WAI and WCAG to include in the presentation.
> 7.      I'm trying to convince my boss to make accessibility a priority
> for our website.
> 8.      What laws require me to make my website accessible?
> 9.      I'm a visual designer. What do I need to do for accessibility?
> 10.     We need to develop an accessibility policy for our website.
> 11.     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.
> 12.     How do I contact someone at WAI to present at my conference?
>
>
> Issue/Question for Charlotte: Ask people not to use Search box so we see
> what they do with the nav? Or let them use it, then redirect to nav?
>
>
> Demographics notes:
> * Most or all involved in web development, management, marketing,
> procurement, or such.
> * Most with low-medium accessibility knowledge.
> * Ideally some project management level; some developers; some *not*
> developers or designers, e.g., procurement or marketing.
> * ...
>
> ###
>
>
>


-- 
Sharron Rush | Executive Director | Knowbility.org | @knowbility
*Equal access to technology for people with disabilities*