Bug 125015 - AX: [ATK] Caret-moved events missing for children of ARIA buttons
Summary: AX: [ATK] Caret-moved events missing for children of ARIA buttons
Status: RESOLVED WONTFIX
Alias: None
Product: WebKit
Classification: Unclassified
Component: Accessibility (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks: 25531
  Show dependency treegraph
 
Reported: 2013-11-29 09:04 PST by Joanmarie Diggs (irc: joanie)
Modified: 2013-12-04 07:37 PST (History)
2 users (show)

See Also:


Attachments
test case (736 bytes, text/html)
2013-11-29 09:04 PST, Joanmarie Diggs (irc: joanie)
no flags Details
accessible-event listener (234 bytes, text/x-python)
2013-11-29 09:05 PST, Joanmarie Diggs (irc: joanie)
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Joanmarie Diggs (irc: joanie) 2013-11-29 09:04:27 PST
Created attachment 218072 [details]
test case

Steps to reproduce:
1. Load the test case in Epiphany and enable caret navigation (F7)
2. Launch the accessible-event listener in a terminal
3. Up/Down arrow to each line then Right/Left arrow within the line

Expected results: When the caret moves to and within each line, caret-moved events would be seen.

Actual results: When the caret moves to and within the heading child of the div with role="button", there are no caret moved events.

Impact: When an Orca user navigates to that line and arrows within it, Orca is not able to present the new caret location and remains silent.
Comment 1 Joanmarie Diggs (irc: joanie) 2013-11-29 09:05:29 PST
Created attachment 218073 [details]
accessible-event listener
Comment 2 Mario Sanchez Prada 2013-12-04 07:37:15 PST
The problem here is that the text exposed for that button belongs to a child of the ARIA button, which should not be exposing children according to WAI-ARIA User Implementation guide, section 5.1.1:

http://www.w3.org/TR/wai-aria-implementation/#exclude_elements2

As the original issue has been detected in yelp-xsl and already fixed as an authoring issue, I'm resolving this one now as a wontfix