Closed Bug 1682865 Opened 4 years ago Closed 4 years ago

In combo edit fields, we don't expose text and popup properties to VoiceOver correctly.

Categories

(Core :: Disability Access APIs, defect, P1)

Firefox 85
Desktop
macOS
defect

Tracking

()

RESOLVED FIXED
86 Branch
Tracking Status
firefox86 --- fixed

People

(Reporter: MarcoZ, Assigned: morgan)

References

Details

(Whiteboard: [Mac2020_2])

Attachments

(1 file)

Test case: data:text/html,<input role="combobox" />.

Steps:

  1. Open the above test case.
  2. Focus the input with VoiceOver.
  3. Type in text.

Results:

  • VoiceOver doesn't echo the text that is typed.
  • The typed text doesn't get displayed on the Braille display until you press Left or Right Arrow, which moves the caret. This and the above point suggest we don't fire a certain event to update the text for VoiceOver, either through Value or some other means that normal text fields do.
  • We don't expose the fact that there are popup menu properties, like for selectelements, to VoiceOver.

Safari does all of the above correctly.

Real-life impact is that on https://google.com, in the search field, no text is spoken when typed or being deleted.

Reported on the AppleVis forum post about the VoiceOver release preview.

Assignee: nobody → mreschenberg
Pushed by mreschenberg@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/b4dd286ab24a
Map roles::EDITCOMBOBOX to mozTextAccessible r=eeejay
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → 86 Branch
Regressions: 1724192
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: