RESOLVED WORKSFORME 145970
AX: <legend> should be announced by Voiceover / screenreader
https://bugs.webkit.org/show_bug.cgi?id=145970
Summary AX: <legend> should be announced by Voiceover / screenreader
goetsu
Reported 2015-06-15 04:17:11 PDT
<legend> inside a <fieldset> must be announced as title of the group. When user have focus on input inside a fieldset with a legend the legend must be used as a description of the inputs like with aria-describedby. Furthermore if you have multiple nested fieldset with legend the description must inherit all the legend value Here is my test case http://codepen.io/goetsu/pen/ZGJOWg This have been resolved in the past but it look to be broken again : https://bugs.webkit.org/show_bug.cgi?id=20887 https://bugs.webkit.org/show_bug.cgi?id=122534
Attachments
Radar WebKit Bug Importer
Comment 1 2015-06-15 04:17:35 PDT
James Craig
Comment 2 2015-06-15 22:36:30 PDT
This is is not a WebKit bug. WebKit exposes the fieldset and legend the same way it always has. Reference LayoutTest run on every commit. https://github.com/WebKit/webkit/blob/master/LayoutTests/accessibility/fieldset-element.html https://github.com/WebKit/webkit/blob/master/LayoutTests/accessibility/fieldset-element-expected.txt VoiceOver's behavior changed in 2014, and is tracked as <rdar://problem/17919418>
Steve Faulkner
Comment 3 2015-06-17 02:08:21 PDT
(In reply to comment #2) > This is is not a WebKit bug. WebKit exposes the fieldset and legend the same > way it always has. > > Reference LayoutTest run on every commit. > https://github.com/WebKit/webkit/blob/master/LayoutTests/accessibility/ > fieldset-element.html > https://github.com/WebKit/webkit/blob/master/LayoutTests/accessibility/ > fieldset-element-expected.txt > > VoiceOver's behavior changed in 2014, and is tracked as > <rdar://problem/17919418> Guessing that <rdar://problem/17919418> is not public. Is there any indication that this VO bug will be fixed and in what time frame? Intersted as a client is asking whether they need to change their coding practices to work around this bug.
Note You need to log in before you can comment on or make changes to this bug.