Skip to content

Always speak labels of landmarks and regions when jumping inside from outside using quicknav or focus in browse mode#14303

Merged
michaelDCurran merged 3 commits into
masterfrom
i13307
Oct 26, 2022
Merged

Always speak labels of landmarks and regions when jumping inside from outside using quicknav or focus in browse mode#14303
michaelDCurran merged 3 commits into
masterfrom
i13307

Conversation

@michaelDCurran

Copy link
Copy Markdown
Member

Link to issue number:

Fixes #13307
Fixes #13996

Summary of the issue:

Some time after NVDA 2019.2, labels of landmarks and regions were no longer automatically spoken when jumping inside from outside using quick nav or focus in browse mode.
Although a label should not be spoken when moving into a landmark or region with the arrow keys if the label is from an associated node via aria-labelledby, when jumping in with quick nav / focus, it always should, as context is more important than rare duplication.

Description of user facing changes

A landmark or region's name is always automatically spoken when jumping inside from outside using quick navigation or focus in browse mode.

Description of development approach

landmark and region roles are treated the same as groupings and propertypages in getcontrolFieldSpeech. I.e. the name is always announced if it has one when entering from outside for a reason of quicknav or focus.

Testing strategy:

Performed steps in issue #13307
Created a system test based on testcase in #13307.

Known issues with pull request:

None known.

Change log entries:

New features
Changes
Bug fixes

Code Review Checklist:

  • Pull Request description:
    • description is up to date
    • change log entries
  • Testing:
    • Unit tests
    • System (end to end) tests
    • Manual testing
  • API is compatible with existing add-ons.
  • Documentation:
    • User Documentation
    • Developer / Technical Documentation
    • Context sensitive help for GUI changes
  • UX of all users considered:
    • Speech
    • Braille
    • Low Vision
    • Different web browsers
    • Localization in other languages / culture than English
  • Security precautions taken.

… jumping inside them from outside with focus or quicknav.
@michaelDCurran michaelDCurran requested a review from a team as a code owner October 26, 2022 06:55

@seanbudd seanbudd left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good @michaelDCurran

@AppVeyorBot

Copy link
Copy Markdown

See test results for failed build of commit 2690e366a1

@michaelDCurran michaelDCurran merged commit a30fbdc into master Oct 26, 2022
@michaelDCurran michaelDCurran deleted the i13307 branch October 26, 2022 23:41
michaelDCurran pushed a commit that referenced this pull request Jan 29, 2023
Fixes #14519
Fixup of #14303

Summary of the issue:
#14303 fixed a bug where landmarks and regions were not correctly reported in some cases.
However, #14303 failed to check/respect the config setting for reportLandmarks

Description of user facing changes
Landmarks are no longer reported incorrectly

Description of development approach
Check the config setting when reporting landmarks/regions in the case introduced by #14303
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Screen Reader is not announcing associated information. regions labeled by aria-labelledby won't read with NVDA.

3 participants