Re: Disclosure Navigation Menu Example Test Plan Feedback

Great clarification, thanks!  I'll look into the setup steps for that test, and determine if they're doing the right thing.  It sounds like they might not be.

Regards,

James Scholes
Director of Digital Accessibility, Prime Access Consulting, Inc.

On 15/11/2021 at 5:51 pm, Alyssa Vo wrote:
> Hi James,
> 
> Thank you for your quick reply!
> 
> In the instructions you listed, focus begins on the "admissions" button. However, for Testing Task 8, focus begins on the "Overview" link (as detailed in the instructions, where it says that a script "sets focus on the first link of the associated dropdown"). Thus, when we were testing, we tried the different navigation keys (up, left, and home) from that starting point which ended up not working. As you detailed, these keys work when starting from the admissions button. 
> 
> Thanks,
> Alyssa
> 
> -----Original Message-----
> From: James Scholes <james@pac.bz> 
> Sent: Monday, November 15, 2021 3:41 PM
> To: Alyssa Vo <avo4@uw.edu>; public-aria-at@w3.org
> Cc: Hadi Rangin <hadir@uw.edu>
> Subject: Re: Disclosure Navigation Menu Example Test Plan Feedback
> 
> Hi Alyssa and Hadi,
> 
> Thanks for this feedback.  I'll let others chime in with thoughts and/or questions about the the app-related aspects.  But to address your last point:
> 
> You wrote: "Testing task 8 (Navigate backwards to an expanded disclosure button in interaction mode) instructs users to use the up arrow key, the home key, and the left arrow key to navigate backwards to the expanded disclosure button. However, these commands are not expected to move focus backwards with or without a screen reader."
> 
> These are built into the example, and were included intentionally.  If you go to:
> 
> https://w3c.github.io/aria-practices/examples/disclosure/disclosure-navigation.html
> 
> ... which is the page the test case example is based on, you can:
> 
> 1. place focus on the "Admissions" button; 2. set the screen reader to interaction mode (e.g. deactivate the Virtual PC Cursor in JAWS); and 3. press all of the keys described from that starting point (Left Arrow, Up Arrow, and Home).
> 
> In all three cases, focus will be moved from the second button ("Admissions") to the first one ("About").
> 
> All test plan feedback is appreciated, particularly when things are unclear.  I'm curious if you tried the commands, though?  In general, I would urge all testers to follow all of the included instructions, and hopefully in this case you would have found that the navigation did work as described.
> 
> Thanks again.
> 
> Regards,
> 
> James Scholes
> Director of Digital Accessibility, Prime Access Consulting, Inc.
> 
> On 15/11/2021 at 5:23 pm, Alyssa Vo wrote:
>> Hi everyone,
>> 
>>  
>> 
>> Hadi and I spent this afternoon reviewing testing tasks 6 – 20 for the Disclosure Navigation Menu Example for JAWS latest and Chrome latest. Below is a couple of notes of feedback we’d like to provide. We apologize if any of this feedback has already been given by another tester. We’d be happy to discuss these notes further or answer any clarifying questions.
>> 
>>  
>> 
>>   * Review conflicts modal is not organized by testing task
>>       o When tasks have conflicting results, there is an alert with a button on the page that opens a “Reviewing Conflicts” modal. This modal has a list of all differences across all testing tasks in the test plan. It would be helpful to organize these differences by test plan to clearly communicate which differences are associated with which specific tasks.
>>   * Interaction mode typo
>>       o Within the instructions for any task requiring the virtual cursor to be off, the test instructions will say to verify if the cursor is active and that “if it is not, turn off the Virtual cursor”. As the virtual cursor should be off, it should instead say “if it is active, turn off the Virtual Cursor…”.
>>   * Testing Task 8 navigation commands
>>       o Testing task 8 (Navigate backwards to an expanded disclosure button in interaction mode) instructs users to use the up arrow key, the home key, and the left arrow key to navigate backwards to the expanded disclosure button. However, these commands are not expected to move focus backwards with or without a screen reader. We were unsure if these commands were included by mistake or if we were testing to see if they don’t work.
>> 
>> Thanks,
>> 
>> Alyssa
>> 
>>  
>> 
>> Alyssa Vo
>> 
>> /She/her/hers/
>> 
>> Student Accessibility Assistant, UW-IT
>> 
>> 425-633-0845
>> 
>> _avo4@uw.edu <mailto:avo4@uw.edu>_
>> 
>

Received on Tuesday, 16 November 2021 00:42:35 UTC