Re: User stories and user tests for the 3rd objective

My only thought is that by using the standard Agile user story prefix 
'As a XXXX I want...' we are in danger of unnecessarily limiting the 
stories to certain people or functional disabilities.

I feel it is much better to just leave that bit out and just capture the 
requirements in the stories.

Steve


On 23/06/2019 14:14, lisa.seeman wrote:
> Hi Folks
> 
> 
> The third objective 
> <https://w3c.github.io/coga/content-usable/#objective-help-the-user-find-what-they-need> in 
> the design guide is missing user stories. I have written up some. I 
> think they could be improved but are OK for this iterations of the 
> design guided.
> Let me know if there are any essential changes that need to be made for 
> this iteration of the design guide. We hope to put them the draft in 
> tomorow.
> 
> 
>       Help the user find what they need
> 
> 
>         User testing
> 
> Make sure your user groups for user testing has all the different 
> cognitive disabilities represented. Do not just ask questions, but ask 
> the user to do an action that demonstrates usability.
> 
> Test for the following:
> 
>   * Can the user easily  find each different page from the home page,
>     without going down incorrect paths?
>   * Can the user easily find each different page from the main page of
>     each set of pages or template, without going down incorrect paths?
>   * Can  the user identify what key information  and applications are
>     available in the site from the home page?
>   * Can the user can easily find the different key information and
>     applications available in the site from the home page, without going
>     down incorrect paths?
>   * On each page, identify any critical functions  necessary to complete
>     the main purpose of the page and important information. Is the user
>     aware that this information and task are available as soon as the
>     page loads?
>   * On each page, identify any critical functions necessary to complete
>     the main purpose of the page. Can the use find them easily without
>     scrolling. Does the user know where to look the first time they try
>     to find these functions?
>   * On each page, identify any important information, including any
>     information that may affect the well being of the user. Can the user
>     find them easily without scrolling. Does the user know where to look
>     the first time they try to find this information?
>   * Some users are likely to pick up a screen and touch it by mistake,
>     or they may click on the wrong item.  Can they always recover and go
>     back to where they where via the standard back mechanism?
>   * Can users always go back to the step they were at before via a
>     standard mechanism?
> 
> 
>         User stories
> 
> This leads to the following user stories:
> 
> 
>   * As a user who has memory impairments and weak language processing
>     skills, I want to find  the content I need without looking in the
>     wrong place.
>   * As a user who has memory impairments, weak executive function and
>     weak language processing skills, I want to know what
>     important information and functions are on a site quickly and easily.
>   * As a user who has memory impairments, weak executive function and
>     weak language processing skills, I want to know what
>     important information and functions are on a page, quickly and easily.
>   * As a user who has memory impairments, weak spacial skills and  weak
>     executive function and I often touch or click on the wrong item. I
>     want to go back to exactly where  I was easily via a simple familiar
>     action (that I use every time I touch or click on the wrong item).
> 
> 
> 
> 
> 
> All the best
> 
> Lisa Seeman
> 
> LinkedIn <http://il.linkedin.com/in/lisaseeman/>, Twitter 
> <https://twitter.com/SeemanLisa>
> 
> 
> 
> 
>

Received on Monday, 24 June 2019 09:28:16 UTC