Re: expected jaws behavior
toggle quoted messageShow quoted text
I have this page in front of me now. I’m using google chrome with jaws 2019, latest build. I’ve navigated through the radio buttons by tabbing in to them. I’ve also used the letter A to move through the radio buttons, It’s behaving consistently for me. It’s reading Kraken, sasquatch and Mothman, every time.
I can’t get it to misbehave no matter how hard I try.
From: email@example.com <firstname.lastname@example.org> On Behalf Of Don Raikes
Sent: July 31, 2019 2:59 PM
Subject: [jaws-users] expected jaws behavior
Hello JAWS users:
I need some help from the folks on this list as a representative group of “typical” JAWS users.
I have been tasked with creating a short class on how to test web pages for accessibility, and I have run into a situation where JAWS is not behaving the way I would have expected, so I want some feedback from other s on how you would expect jaws to behave.
I have a webpage with a group of radio buttons on it:
If I jump to the first heading on the page, then tab to the first radio button, depending on the browser sometimes jaws will read the radiogroup label then the radio button value, some times it doesn’t read the label.
The same is true if I go past the radio group and shift-tab back to the last button in the group.
Sometimes I can tab through the entire list of buttons in the group sometimes tabbing once takes me into the list then the next tab takes me out of the list altogether.
When I use the forms quick navigation sometimes jaws reads the label then the button value sometimes it doesn’t.
I would appreciate any opinions/feelings on what jaws should be doing also if anyone is experiencing anything different with this particular webpage.
For those techie types, the page contains a form with a fieldset inside of it. The fieldset has a legend and three input tags inside of it to form the radio group.
Thanks in advance,
Accessibility, like security, is better when built-in from the beginning rather than bolted on at the end.