Bug 249715
| Summary: | AX: iOS VoiceOver announces "form start" / "form end" for fieldsets with non-form-related roles | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Scott <scottaohara> |
| Component: | Accessibility | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | andresg_22, marc.solomon, tyler_w, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | Safari 16 | ||
| Hardware: | iPhone / iPad | ||
| OS: | iOS 16 | ||
Scott
VoiceOver on iOS appears to include an extra announcement of "form start" and "form end" when navigating to the first and last elements of a fieldset, respectively. This makes sense so long as someone is in the context of a form, but is not expected if the role of the fieldset is overwritten in a way where this announcement would no longer be expected.
For instance, the 'form start' / 'form end' announcements will still be made for each of the test cases included in the following codepen. A separate 'control' of each test case is also provided, where the same role is used on a div element, and the 'form start' / 'form end' announcements are correctly -not- announced by VoiceOver.
https://codepen.io/scottohara/pen/ExpaeEj
The expected result would be that if a fieldset has a non-form associated role specified to it, then it would -not- announce 'form start' / 'form end'.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/103599790>
marc.solomon
In my opinion, the announcement of "form start/end" is also technically inaccurate and misleading because it is not used to communicate the boundaries of a form.
There may be other form elements outside a fieldset but still within the fieldset's parent form.
Please consider updating the VoiceOver announcement to more clearly describes the content type it is associated with. If fieldset is too technical of a term for the intended audience, consider using plain language like "control group start/end."