The GW-Info list is a discussion list, which can be very active with many messages per day. Any subscriber of the GW-Info list has the ability to post on-topic messages.
From:
Yusuf <yusufaosman@btinternet.com>Subject:
Re: WebAIM Survey on Screen ReadersDate:
Thu, May 3, 2012 10:57:56 amThank you Jared for your email message. It does however leave something
unanswered. Whilst what you say seems to apply to Internet Explorer, I
was able to access the relevant information in browse mode using the
latest version of Firebox, that I downloaded yesterday specifically to
answer the survey. If the problem is a limitation in Window Eyes, why
did it work correctly using Firebox?
Yusuf
On 03/05/2012 15:01, Jared Smith wrote:
> Thank you for the comments on the WebAIM Screen Reader User Survey.
> Some of the comments referred to the apparent lack of accessibility
> for radio button and check box questions. I can assure you that the
> survey is authored using best accessibility practices and markup. The
> issue is with Window-Eyes. It has been pointed out several times on
> this list over the last 5 years that Window-Eyes does not support the
> fieldset and legend elements when navigating a form. This is the
> standard mechanism for grouping checkboxes and radio buttons and has
> been part of HTML and accessibility standards since the late 90's.
>
> We encourage GW Micro to enable default access to this information
> when navigating form controls. The lack of support for this standard
> accessibility practice has a distinct impact on end users (e.g., YOU).
> All other screen readers have had support for reading the fieldset
> legend when a grouping of check boxes and radio buttons is encountered
> for nearly a decade.
>
> As was noted, you can get around this lack of standards support by
> going to browse mode and reading the question which is found
> immediately before the first check box or radio button.
>
> Some historical background and additional details are in these list
> archives at http://www.gwmicro.com/Support/Email_Lists/Archives/GW-Info/index.php?message_id9517
> and the entire thread at
> http://www.mail-archive.com/gw-info@gwmicro.com/msg14508.html
>
> Thank you for the participation on the survey. We encourage all screen
> reader users to complete the survey. Your responses greatly informs
> the development community.
>
> Jared Smith
> WebAIM.org
> If you reply to this message it will be delivered to the original sender only. If your reply would benefit others on the list and your message is related to GW Micro, then please consider sending your message to gw-info@gwmicro.com so the entire list will receive it.
>
> GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You can manage your list subscription at http://www.gwmicro.com/listserv.
>
>
If you reply to this message it will be delivered to the original sender only. If your reply would benefit others on the list and your message is related to GW Micro, then please consider sending your message to gw-info@gwmicro.com so the entire list will receive it.
GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You can manage your list subscription at http://www.gwmicro.com/listserv.
unanswered. Whilst what you say seems to apply to Internet Explorer, I
was able to access the relevant information in browse mode using the
latest version of Firebox, that I downloaded yesterday specifically to
answer the survey. If the problem is a limitation in Window Eyes, why
did it work correctly using Firebox?
Yusuf
On 03/05/2012 15:01, Jared Smith wrote:
> Thank you for the comments on the WebAIM Screen Reader User Survey.
> Some of the comments referred to the apparent lack of accessibility
> for radio button and check box questions. I can assure you that the
> survey is authored using best accessibility practices and markup. The
> issue is with Window-Eyes. It has been pointed out several times on
> this list over the last 5 years that Window-Eyes does not support the
> fieldset and legend elements when navigating a form. This is the
> standard mechanism for grouping checkboxes and radio buttons and has
> been part of HTML and accessibility standards since the late 90's.
>
> We encourage GW Micro to enable default access to this information
> when navigating form controls. The lack of support for this standard
> accessibility practice has a distinct impact on end users (e.g., YOU).
> All other screen readers have had support for reading the fieldset
> legend when a grouping of check boxes and radio buttons is encountered
> for nearly a decade.
>
> As was noted, you can get around this lack of standards support by
> going to browse mode and reading the question which is found
> immediately before the first check box or radio button.
>
> Some historical background and additional details are in these list
> archives at http://www.gwmicro.com/Support/Email_Lists/Archives/GW-Info/index.php?message_id9517
> and the entire thread at
> http://www.mail-archive.com/gw-info@gwmicro.com/msg14508.html
>
> Thank you for the participation on the survey. We encourage all screen
> reader users to complete the survey. Your responses greatly informs
> the development community.
>
> Jared Smith
> WebAIM.org
> If you reply to this message it will be delivered to the original sender only. If your reply would benefit others on the list and your message is related to GW Micro, then please consider sending your message to gw-info@gwmicro.com so the entire list will receive it.
>
> GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You can manage your list subscription at http://www.gwmicro.com/listserv.
>
>
If you reply to this message it will be delivered to the original sender only. If your reply would benefit others on the list and your message is related to GW Micro, then please consider sending your message to gw-info@gwmicro.com so the entire list will receive it.
GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You can manage your list subscription at http://www.gwmicro.com/listserv.
