Topics

expected jaws behavior

Don Raikes
 

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:

http://donraikes.github.io/htmlex/radiogroup

 

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,

Donald

 

--
Thanks, Donald

Accessibility, like security, is better when built-in from the beginning rather than bolted on at the end.


Oracle
Donald Raikes | Accessibility Specialist
Mobile: +15202717608 | VOIP: +15205744033
Oracle Accessibility Program Office
| Tucson, Arizona

Green Oracle

Oracle is committed to developing practices and products that help protect the environment

 

Glenn / Lenny
 

Don,
Did you try the letter A for Radio Button?
Glenn

From: Don Raikes
Sent: Wednesday, July 31, 2019 12: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:

http://donraikes.github.io/htmlex/radiogroup

 

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,

Donald

 

--
Thanks, Donald

Accessibility, like security, is better when built-in from the beginning rather than bolted on at the end.


Oracle
Donald Raikes | Accessibility Specialist
Mobile: +15202717608 | VOIP: +15205744033
Oracle Accessibility Program Office
| Tucson, Arizona

Green Oracle

Oracle is committed to developing practices and products that help protect the environment

 

chris judge
 

Hi don.

 

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: jaws-users-list@groups.io <jaws-users-list@groups.io> On Behalf Of Don Raikes
Sent: July 31, 2019 2:59 PM
To: jaws-users-list@groups.io
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:

http://donraikes.github.io/htmlex/radiogroup

 

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,

Donald

 

--
Thanks, Donald

Accessibility, like security, is better when built-in from the beginning rather than bolted on at the end.


Oracle
Donald Raikes | Accessibility Specialist
Mobile: +15202717608 | VOIP: +15205744033
Oracle Accessibility Program Office
| Tucson, Arizona

Green Oracle

Oracle is committed to developing practices and products that help protect the environment

 

Don Raikes
 

Glenn,

 

I always forget that quick key J

 

Using “a” makes JAWS say the label then the radio button value for the first button then just the button value for the remaining buttons which makes sense I suppose.

Going backwards up the page, shift+a reads the label and value for the last button then just the button values for the remainder.

 

Thanks for the suggestion.

 

--
Thanks, Donald

Accessibility, like security, is better when built-in from the beginning rather than bolted on at the end.


Oracle
Donald Raikes | Accessibility Specialist
Mobile: +15202717608 | VOIP: +15205744033
Oracle Accessibility Program Office
| Tucson, Arizona

Green Oracle

Oracle is committed to developing practices and products that help protect the environment

 

From: Glenn / Lenny <glennervin@...>
Sent: Wednesday, July 31, 2019 11:13 AM
To: jaws-users-list@groups.io
Subject: Re: [jaws-users] expected jaws behavior

 

Don,

Did you try the letter A for Radio Button?

Glenn

 

From: Don Raikes

Sent: Wednesday, July 31, 2019 12: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:

http://donraikes.github.io/htmlex/radiogroup

 

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,

Donald

 

--
Thanks, Donald

Accessibility, like security, is better when built-in from the beginning rather than bolted on at the end.


Oracle
Donald Raikes | Accessibility Specialist
Mobile: +15202717608 | VOIP: +15205744033
Oracle Accessibility Program Office
| Tucson, Arizona

Green Oracle

Oracle is committed to developing practices and products that help protect the environment

 

Don Raikes
 

Chris,

 

I agree it reads the monster names, but the thing I am trying to figure out is whether and how it should be reading “choose your favorite monster” which is the group label.

 

--
Thanks, Donald

Accessibility, like security, is better when built-in from the beginning rather than bolted on at the end.


Oracle
Donald Raikes | Accessibility Specialist
Mobile: +15202717608 | VOIP: +15205744033
Oracle Accessibility Program Office
| Tucson, Arizona

Green Oracle

Oracle is committed to developing practices and products that help protect the environment

 

From: chris judge <chrisjudge1967@...>
Sent: Wednesday, July 31, 2019 11:16 AM
To: jaws-users-list@groups.io
Subject: Re: [jaws-users] expected jaws behavior

 

Hi don.

 

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: jaws-users-list@groups.io <jaws-users-list@groups.io> On Behalf Of Don Raikes
Sent: July 31, 2019 2:59 PM
To: jaws-users-list@groups.io
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:

http://donraikes.github.io/htmlex/radiogroup

 

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,

Donald

 

--
Thanks, Donald

Accessibility, like security, is better when built-in from the beginning rather than bolted on at the end.


Oracle
Donald Raikes | Accessibility Specialist
Mobile: +15202717608 | VOIP: +15205744033
Oracle Accessibility Program Office
| Tucson, Arizona

Green Oracle

Oracle is committed to developing practices and products that help protect the environment

 

Holly
 

Hi Don:
 
Using JAWS 2019 and Internet Explorer, the page reads fine and all radio buttons are labeled.

JM Casey
 

Yes, I see what you mean.

Pressing the navigation quick key gets you to the radio buttons right away, but in Firefox 68 and JAWS 2018 at least, the “choose your favourite monster” instruction is only read some of the time, and then, only when the buttons are tabbed to. iE, pressing “a” and then arrowing around will not reveal this.

 

 

 

From: jaws-users-list@groups.io <jaws-users-list@groups.io> On Behalf Of Don Raikes
Sent: July 31, 2019 2:24 PM
To: jaws-users-list@groups.io
Subject: Re: [jaws-users] expected jaws behavior

 

Chris,

 

I agree it reads the monster names, but the thing I am trying to figure out is whether and how it should be reading “choose your favorite monster” which is the group label.

 

--
Thanks, Donald

Accessibility, like security, is better when built-in from the beginning rather than bolted on at the end.


Oracle
Donald Raikes | Accessibility Specialist
Mobile: +15202717608 | VOIP: +15205744033
Oracle Accessibility Program Office
| Tucson, Arizona

Green Oracle

Oracle is committed to developing practices and products that help protect the environment

 

From: chris judge <chrisjudge1967@...>
Sent: Wednesday, July 31, 2019 11:16 AM
To: jaws-users-list@groups.io
Subject: Re: [jaws-users] expected jaws behavior

 

Hi don.

 

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: jaws-users-list@groups.io <jaws-users-list@groups.io> On Behalf Of Don Raikes
Sent: July 31, 2019 2:59 PM
To: jaws-users-list@groups.io
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:

http://donraikes.github.io/htmlex/radiogroup

 

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,

Donald

 

--
Thanks, Donald

Accessibility, like security, is better when built-in from the beginning rather than bolted on at the end.


Oracle
Donald Raikes | Accessibility Specialist
Mobile: +15202717608 | VOIP: +15205744033
Oracle Accessibility Program Office
| Tucson, Arizona

Green Oracle

Oracle is committed to developing practices and products that help protect the environment

 

Van Lant, Robin
 

I tried the below link with three browsers.  I’m using JAWS 2019. 

With Edge, I heard the question, then each time I navigate to a radio button, JAWS is reading all three of the answer choices, but telling me which one I’m on by saying 1 of 3.  This not the behavior I’d want and I do not generally use Edge because of the way radio and checkbox labels are read, among other things.

 

In Internet Explorer, JAWS voices the question and the answer for the radio button I am on.  This can seem most useful to some, however, I have found this behavior very frustrating when doing a survey where the question is quite long.  For.  For example, I might be reading a test question where the scenario is presented then I have to select the answer, but navigating to each answer causes JAWS to re-read the entire scenario.  I think I ended up using the JAWS cursor or something in this case.

 

Google Chrome seems to present the best experience.  I heard the question once, then navigating with quick key A read only the answer.  I liked this best.

 

 

 

 

 

From: jaws-users-list@groups.io <jaws-users-list@groups.io> On Behalf Of Don Raikes
Sent: Wednesday, July 31, 2019 11:59 AM
To: jaws-users-list@groups.io
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:

http://donraikes.github.io/htmlex/radiogroup

 

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,

Donald

 

--
Thanks, Donald

Accessibility, like security, is better when built-in from the beginning rather than bolted on at the end.


Oracle
Donald Raikes | Accessibility Specialist
Mobile: +15202717608 | VOIP: +15205744033
Oracle Accessibility Program Office
| Tucson, Arizona

Green Oracle

Oracle is committed to developing practices and products that help protect the environment

 



This communication may contain privileged and/or confidential information. It is intended solely for the use of the addressee. If you are not the intended recipient, you are strictly prohibited from disclosing, copying, distributing or using any of this information. If you received this communication in error, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. This communication may contain nonpublic personal information about consumers subject to the restrictions of the Gramm-Leach-Bliley Act. You may not directly or indirectly reuse or redisclose such information for any purpose other than to provide the services for which you are receiving the information.

127 Public Square, Cleveland, OH 44114


If you prefer not to receive future e-mail offers for products or services from Key
send an e-mail to mailto:DNERequests@... with 'No Promotional E-mails' in the SUBJECT line.

 

Hello Don:

 

In my opinion, this has nothing to do with JAWS, but with the DOCTYPE declaration of the webpage.   If you try to replace the top two lines of your webpage with just this:

 

<DOCTYPE html>

 

To indicate that it is an HTML5 page, the current standard, instead of the antiquated HTML 1.0 and xtml, I imagine you would find that the legend would be repeated each time you tab to the next control, as it should, therefore it should be a short legend, and radial choices would be chosen automatically as you down-arrow while on forms mode.

 

hTH,

 

Humberto

.

 

 

From: jaws-users-list@groups.io <jaws-users-list@groups.io> On Behalf Of Don Raikes
Sent: Wednesday, July 31, 2019 1:59 PM
To: jaws-users-list@groups.io
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:

http://donraikes.github.io/htmlex/radiogroup

 

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,

Donald

 

--
Thanks, Donald

Accessibility, like security, is better when built-in from the beginning rather than bolted on at the end.


Oracle
Donald Raikes | Accessibility Specialist
Mobile: +15202717608 | VOIP: +15205744033
Oracle Accessibility Program Office
| Tucson, Arizona

Green Oracle

Oracle is committed to developing practices and products that help protect the environment

 

Don Raikes
 

Humberto,

 

Interesting catch, but now it is really odd:

 

When none of the radio buttons is selected, jumping to the heading before the radio group then tabbing into the radiogroup causes jaws to read the group label along with the first button’s label tabbing again jaws reads just the button label for the remaining two buttons.

The same kind of behavior is true if I start at the bottom of the page and shift-tab through the radio buttons.

 

If I select the first button, then go back to the top of the page and jump to the heading then tab to the radiogroup, jaws reads the group label then the label for the first button and that it is checked and that there are three buttons.

Tabbing again causes jaws to bypass the remainder of the buttons and go to the browser toolbar.

 

If the second button is selected, then after jumping to the header tabbing once takes me to the first radio button and jaws reads the group label and the button label. Tabbing again takes me to the second button and reads  just the button label and that it is checked. Tabbing again takes my to the browser toolbar bypassing the third button altogether.

 

--
Thanks, Donald

Accessibility, like security, is better when built-in from the beginning rather than bolted on at the end.


Oracle
Donald Raikes | Accessibility Specialist
Mobile: +15202717608 | VOIP: +15205744033
Oracle Accessibility Program Office
| Tucson, Arizona

Green Oracle

Oracle is committed to developing practices and products that help protect the environment

 

From: Humberto Rodriguez <sub@...>
Sent: Wednesday, July 31, 2019 1:04 PM
To: jaws-users-list@groups.io
Subject: Re: [jaws-users] expected jaws behavior

 

Hello Don:

 

In my opinion, this has nothing to do with JAWS, but with the DOCTYPE declaration of the webpage.   If you try to replace the top two lines of your webpage with just this:

 

<DOCTYPE html>

 

To indicate that it is an HTML5 page, the current standard, instead of the antiquated HTML 1.0 and xtml, I imagine you would find that the legend would be repeated each time you tab to the next control, as it should, therefore it should be a short legend, and radial choices would be chosen automatically as you down-arrow while on forms mode.

 

hTH,

 

Humberto

.

 

 

From: jaws-users-list@groups.io <jaws-users-list@groups.io> On Behalf Of Don Raikes
Sent: Wednesday, July 31, 2019 1:59 PM
To: jaws-users-list@groups.io
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:

http://donraikes.github.io/htmlex/radiogroup

 

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,

Donald

 

--
Thanks, Donald

Accessibility, like security, is better when built-in from the beginning rather than bolted on at the end.


Oracle
Donald Raikes | Accessibility Specialist
Mobile: +15202717608 | VOIP: +15205744033
Oracle Accessibility Program Office
| Tucson, Arizona

Green Oracle

Oracle is committed to developing practices and products that help protect the environment

 

Van Lant, Robin
 

This sounds like the behavior I was seeing in Chrome and is the behavior I would expect and want.  Again,  when you header question ins short, it’s not a problem to hear it before each  answer, but I the question is long, it is really cumbersome and time wasting to have to listen to the question over before each answer option is read.  I would be more likely to use insert A or insert F to navigate in a survey, not tab.

 

 

 

 

From: jaws-users-list@groups.io <jaws-users-list@groups.io> On Behalf Of Don Raikes
Sent: Thursday, August 1, 2019 12:08 PM
To: jaws-users-list@groups.io
Subject: Re: [jaws-users] expected jaws behavior

 

Humberto,

 

Interesting catch, but now it is really odd:

 

When none of the radio buttons is selected, jumping to the heading before the radio group then tabbing into the radiogroup causes jaws to read the group label along with the first button’s label tabbing again jaws reads just the button label for the remaining two buttons.

The same kind of behavior is true if I start at the bottom of the page and shift-tab through the radio buttons.

 

If I select the first button, then go back to the top of the page and jump to the heading then tab to the radiogroup, jaws reads the group label then the label for the first button and that it is checked and that there are three buttons.

Tabbing again causes jaws to bypass the remainder of the buttons and go to the browser toolbar.

 

If the second button is selected, then after jumping to the header tabbing once takes me to the first radio button and jaws reads the group label and the button label. Tabbing again takes me to the second button and reads  just the button label and that it is checked. Tabbing again takes my to the browser toolbar bypassing the third button altogether.

 

--
Thanks, Donald

Accessibility, like security, is better when built-in from the beginning rather than bolted on at the end.


Oracle
Donald Raikes | Accessibility Specialist
Mobile: +15202717608 | VOIP: +15205744033
Oracle Accessibility Program Office
| Tucson, Arizona

Green Oracle

Oracle is committed to developing practices and products that help protect the environment

 

From: Humberto Rodriguez <sub@...>
Sent: Wednesday, July 31, 2019 1:04 PM
To: jaws-users-list@groups.io
Subject: Re: [jaws-users] expected jaws behavior

 

Hello Don:

 

In my opinion, this has nothing to do with JAWS, but with the DOCTYPE declaration of the webpage.   If you try to replace the top two lines of your webpage with just this:

 

<DOCTYPE html>

 

To indicate that it is an HTML5 page, the current standard, instead of the antiquated HTML 1.0 and xtml, I imagine you would find that the legend would be repeated each time you tab to the next control, as it should, therefore it should be a short legend, and radial choices would be chosen automatically as you down-arrow while on forms mode.

 

hTH,

 

Humberto

.

 

 

From: jaws-users-list@groups.io <jaws-users-list@groups.io> On Behalf Of Don Raikes
Sent: Wednesday, July 31, 2019 1:59 PM
To: jaws-users-list@groups.io
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:

http://donraikes.github.io/htmlex/radiogroup

 

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,

Donald

 

--
Thanks, Donald

Accessibility, like security, is better when built-in from the beginning rather than bolted on at the end.


Oracle
Donald Raikes | Accessibility Specialist
Mobile: +15202717608 | VOIP: +15205744033
Oracle Accessibility Program Office
| Tucson, Arizona

Green Oracle

Oracle is committed to developing practices and products that help protect the environment

 



This communication may contain privileged and/or confidential information. It is intended solely for the use of the addressee. If you are not the intended recipient, you are strictly prohibited from disclosing, copying, distributing or using any of this information. If you received this communication in error, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. This communication may contain nonpublic personal information about consumers subject to the restrictions of the Gramm-Leach-Bliley Act. You may not directly or indirectly reuse or redisclose such information for any purpose other than to provide the services for which you are receiving the information.

127 Public Square, Cleveland, OH 44114


If you prefer not to receive future e-mail offers for products or services from Key
send an e-mail to mailto:DNERequests@... with 'No Promotional E-mails' in the SUBJECT line.