New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

browse mode document should not be announced when entering from a descendant #4069

Closed
nvaccessAuto opened this Issue Apr 11, 2014 · 3 comments

Comments

Projects
None yet
1 participant
@nvaccessAuto

nvaccessAuto commented Apr 11, 2014

Reported by mdcurran on 2014-04-11 06:05
When ever focus enters a browse mode document (i.e. falls on an object that is rendered by a browse mode document) the document itself is announced similar to the way we would for focusEntered, and then the current line in the document is spoken. This includes when focus moves into the browse mode document from completely outside the document, or when the focus moves from a non-rendered descendant (such as an ARIA dialog or application). It could be argued that we should not announce the document when entering from a non-rendered descendant as we are already within the document's subtree. It would be easy enough to limit the speaking of the document to only when coming in from an outside object by using focus ancestors and focus difference level etc.

@nvaccessAuto

This comment has been minimized.

nvaccessAuto commented Apr 11, 2014

Comment 1 by Michael Curran <mick@... on 2014-04-11 06:14
In [f91ee96]:

Merge branch 't4069' into next. Incubates #4069

Changes:
Added labels: incubating

@nvaccessAuto

This comment has been minimized.

nvaccessAuto commented Apr 27, 2014

Comment 2 by Michael Curran <mick@... on 2014-04-27 23:09
In [e1d7081]:

Merge branch 't4069'. Fixes #4069

Changes:
Removed labels: incubating
State: closed

@nvaccessAuto

This comment has been minimized.

nvaccessAuto commented Apr 27, 2014

Comment 3 by mdcurran on 2014-04-27 23:12
Changes:
Milestone changed from next to 2014.2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment