- From: Matt King <a11ythinker@gmail.com>
- Date: Tue, 21 Apr 2026 23:26:49 -0700
- To: Hadi Rangin <hadir@uw.edu>
- Cc: "public-aria-at@w3.org" <public-aria-at@w3.org>
- Message-ID: <CAKg_NzL1T_Br2rrtj5e08W=_h+z7_CpdX0aOHQZjnNwpr=mFrQ@mail.gmail.com>
Hadi, thank you for the update. That is correct; the expected JAWS behavior is that JAWS switches to forms mode when the spin button gets focus. So, you do have to press numpad plus or capslock+; for the VC commands in test 3. There have been times when the bot runner doesn't successfully complete activation of the correct JAWS mode before capturing the output. So, thank you for updating the JAWS response field if the bot didn't capture the correct output. Matt On Tue, Apr 21, 2026 at 8:59 PM Hadi Rangin <hadir@uw.edu> wrote: > Hi team, > > > > I wanted to share an update regarding my testing of the Quantity spinbox, > specifically related to question 3 about requesting information for the > spinbox. > > > > Here’s the issue I’m encountering: when I run the test, the focus > automatically shifts to the spinbox field, and JAWS immediately switches > from Virtual mode to Form mode, regardless of the mode in which I start the > test. Because of this, if we want to test commands like insert+tab or > insert+up in Virtual mode, we’d first need to manually switch JAWS back > from Form mode to Virtual mode. Otherwise, these commands are being tested > in Form mode by default. > > I think the Jaws output fields for insert+up in Virtual mode was not > correct. To be on the safe side, I copied the Jaws output manually from > Jaws history. > > > > I won’t be able to attend tomorrow’s meeting due to a prior commitment > with Microsoft colleagues. If you want to compare my results with Joe’s > test results, this explains the method I used. So far I see, there is only > one conflict. > > > > Thanks, > > Hadi > > > -- Matt King as A11yThinker "Oh the thinks you can think!" -- Dr. Seuss
Received on Wednesday, 22 April 2026 06:27:06 UTC