145970 2015-06-15 04:17:11 -0700 AX: <legend> should be announced by Voiceover / screenreader 2015-06-17 02:08:21 -0700 1 1 1 Unclassified WebKit Accessibility 528+ (Nightly build) Mac All RESOLVED WORKSFORME InRadar P2 Critical --- 1 aurelien.levy webkit-unassigned faulkner.steve jcraig webkit-bug-importer oldest_to_newest 1101903 0 aurelien.levy 2015-06-15 04:17:11 -0700 <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 1101904 1 webkit-bug-importer 2015-06-15 04:17:35 -0700 <rdar://problem/21380574> 1102167 2 jcraig 2015-06-15 22:36:30 -0700 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> 1102514 3 faulkner.steve 2015-06-17 02:08:21 -0700 (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.