New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 652011 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Last visit > 30 days ago
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug
Team-Accessibility

Blocking:
issue 656456



Sign in to add a comment

Traversing down the a11y tree from the focused object doesn't get you to the object with the caret

Project Member Reported by nek...@chromium.org, Oct 1 2016

Issue description

According to the IA2 Spec, traversing down from the focused object in the accessibility tree, one should be able to use IAccessibleHyperlink to get to the object containing the caret. Currently, this doesn't happen in content editables because we store text both in static_text nodes and the nodes that have the static_text nodes as children, e.g. a paragraph.
IA2_PARAGRAPH IA2_HYPERTEXT='text'
++STATIC_TEXT IA2_HYPERTEXT='text'
The caret is always in a static_text node, but since there is no embedded object character for the static_text node in its parent, e.g. in the paragraph, assistive software cannot use IAccessibleHyperlink to get to the caret from its parent.
We should fix this by removing the actual text from parent nodes and only expose it on static_text nodes. Before doing this, we should test if this will break any existing assistive software.

 

Comment 1 by chaok@google.com, Dec 5 2016

Blocking: 656456
Labels: NewComponent-Accessibility NewComponent-Accessibility-Compatibility
Components: UI>Accessibility>Compatibility
Components: -UI>Accessibility
Labels: -newcomponent-accessibility-compatibility -newcomponent-accessibility
Labels: triage-dominic

Comment 6 by nek...@chromium.org, Dec 10 2017

Labels: -triage-dominic win-a11y
Increasing priority since this bug concerns text editing and navigation.
Labels: -Pri-3 editing Pri-2
Status: Assigned (was: Available)

Sign in to add a comment