Implement necessary text retrieval bits of NSAccessibility protocol

NEW
Unassigned

Status

()

defect
6 years ago
4 years ago

People

(Reporter: MarcoZ, Unassigned)

Tracking

(Blocks 1 bug)

Trunk
x86_64
macOS
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

In both HTML and XUL, necessary bits are missing to retrieve the current character, text typed so far, and other text and navigation-related bits so VoiceOver can track what's been typed. The only thing that does work is, when tabbing to a field which already contains text, and the text is selected. That is spoken. But neither the removal of the selection nor arrowing through, nor newly typed text is picked up by either speech or braille.
I believe it would help to split this bug into smaller issues & provide reduced testcases and details for each issue etc

A first analysis:

On text field, WebKit exposes the following attributes (http://trac.webkit.org/browser/trunk/Source/WebCore/accessibility/mac/WebAccessibilityObjectWrapperMac.mm#L1412):

NSAccessibilityAccessKeyAttribute
NSAccessibilityInsertionPointLineNumberAttribute
NSAccessibilityInvalidAttribute
NSAccessibilityNumberOfCharactersAttribute
NSAccessibilityPlaceholderValueAttribute
NSAccessibilityRequiredAttribute
NSAccessibilitySelectedTextAttribute
NSAccessibilitySelectedTextRangeAttribute
NSAccessibilityTitleUIElementAttribute
NSAccessibilityValueAutofilledAttribute
NSAccessibilityVisibleCharacterRangeAttribute

While we currently only exposes the following attributes (http://hg.mozilla.org/mozilla-central/file/5f16c6c2b969/accessible/mac/mozTextAccessible.mm#l66):

NSAccessibilityInsertionPointLineNumberAttribute
NSAccessibilityInvalidAttribute
NSAccessibilityNumberOfCharactersAttribute
NSAccessibilityRequiredAttribute
NSAccessibilitySelectedTextAttribute
NSAccessibilitySelectedTextRangeAttribute
NSAccessibilityVisibleCharacterRangeAttribute
You need to log in before you can comment on or make changes to this bug.