Re: [ftr] usability testing tasks, questions, characteristics

On 13 Sep 2017, at 16:35, Shawn Henry wrote:

> On 9/13/2017 9:00 AM, Wise, Charlotte wrote:
>>  From a usability standpoint, it would be good if we could be 
>> consistent in our patterns and I would recommend we try to do that. 
>> Why do we use two different models here? Is there a way we could 
>> change the secondary page design to accommodate a consistent pattern?
>
> I *strongly* support that - always have. :)
>
> (ftr, I was very hesitant about moving the In-Page Contents from the 
> right side.)

Can I also note that some pages currently have both, a context (same 
resource) and a content (in-page) navigation? This is the case in the 
tutorials, for example. When we talked about it waaaaaay back, the 
consensus seemed to be that we would drop the in-page navigation in such 
cases.

While I am happy to keep in-page navigations, this means introducing yet 
another template very late in the process, which is sub-optimal.

Best, Eric

>
> ~Shawn
>
>
>>
>> Best,
>> Charlotte
>>
>> -----Original Message-----
>> From: Shawn Henry [mailto:shawn@w3.org]
>> Sent: Tuesday, September 12, 2017 4:38 PM
>> To: WSTF <public-wai-eo-site@w3.org>; Wise, Charlotte 
>> <cwise@visa.com>
>> Subject: Re: [ftr] usability testing tasks, questions, 
>> characteristics
>>
>> Hi Charlotte, a more specific issue below...
>>
>>> -------- 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.
>>
>> On some pages, the left nav links to related info on other pages.
>> On some pages, the left nav is in-page links.
>>
>> Do users get that? Is it confusing? Helpful?
>>
>> ~Shawn
>>
>> <snip rest of message>
>>



--

Eric Eggert
Web Accessibility Specialist
Web Accessibility Initiative (WAI) at World Wide Web Consortium (W3C)

Received on Wednesday, 13 September 2017 14:42:18 UTC