FLUID-2741: JAWS does not read labels associated with radio buttons

Metadata

Source
FLUID-2741
Type
Bug
Priority
Major
Status
Closed
Resolution
Fixed
Assignee
Alison Benjamin
Reporter
Alison Benjamin
Created
2009-05-15T15:48:28.000-0400
Updated
2011-02-28T16:45:15.589-0500
Versions
N/A
Fixed Versions
  1. 1.1
Component
  1. UI Options

Description

Under "Easier to see" there are two sets of radio buttons:

JAWS does not read the label associated with the buttons (e.g. "Background Images" & "Simplified Layout" ).

Environments

FF3 / Win XP
IE 8 / Win XP

Attachments

Comments

  • Justin Obara commented 2009-05-16T13:25:00.000-0400

    Bug Parade 1.1 release

  • Justin Obara commented 2009-05-16T13:25:08.000-0400

    a11y issue

  • Alison Benjamin commented 2009-05-20T10:13:22.000-0400

    patch uses fieldset & legend tags. Tested & works with JAWS.

  • Michelle D'Souza commented 2009-05-20T10:31:50.000-0400

    I committed Alison's patch

  • Antranig Basman commented 2009-05-20T21:26:24.000-0400

    Note that the current markup violates the XHTML DTD, since "legend" is not a legal occupant of "label". However, the opposite combination is still legal:
    http://www.december.com/html/x1/element/legend.html
    Could we check that swapping "legend" and "label" still leaves the labels readable by JAWS and if so do that? Clearly if that combination does not work we will regrettably have to violate XHTML, but we should try to comply if we can.

  • Alison Benjamin commented 2009-05-21T11:05:51.000-0400

    This patch, which Jacob committed, corrects how 2741 didn't have valid HTML. Note that FLUID-2399 duplicates 2741 and has been closed. I am re-testing with JAWS to evaluate the accessibility.

  • Alison Benjamin commented 2009-05-22T11:19:02.000-0400

    I've just been testing with JAWS, and experimented with some different strategies (using text hidden in offscreen spans, adding titles to inputs, and using aria-labelledby). In JAWS forms mode, the legend/fieldset combination was most successful across browsers (IE 6,7,8 & FF3). The caveat is I don't know how other screen-readers will deal with this problem. User testing with users who use diverse ATs could offer more insight.

  • Michelle D'Souza commented 2011-02-28T16:45:15.587-0500

    Closing issues that were fixed in 1.1