Skip to content

Conversation

@vladimir-krestov
Copy link
Contributor

@vladimir-krestov vladimir-krestov commented Oct 16, 2019

Issue description

Proposed changes

  • Set SupportsUiaProviders property as true
  • Use FormAccessibleObject as AccessibleObject instead default

This allows customizing Form AccessibleObject how we want.
For example, fix UIA navigation in the accessibility tree. It changes the focus order of Narrator.
Form AccessibleObject works as before.

Customer Impact

  • Improved Bounds No

Regression?

  • No

Risk

  • No

Test methodology

  • Manual UI testing

Accessibility testing

  • Using Inspect tool

Test environment(s)

  • .NET Core Version: 3.1.0-preview1.19458.7
  • Microsoft Windows [Version 10.0.18362.356]
Microsoft Reviewers: Open in CodeFlow

@codecov
Copy link

codecov bot commented Oct 16, 2019

Codecov Report

Merging #2096 into release/3.1 will decrease coverage by 0.05208%.
The diff coverage is 4%.

@@                  Coverage Diff                  @@
##           release/3.1       #2096         +/-   ##
=====================================================
- Coverage      26.5056%   26.45352%   -0.05208%     
=====================================================
  Files              805         806          +1     
  Lines           268083      268108         +25     
  Branches         38068       38070          +2     
=====================================================
- Hits             71057       70924        -133     
- Misses          191947      192096        +149     
- Partials          5079        5088          +9
Flag Coverage Δ
#Debug 26.45352% <4%> (-0.05209%) ⬇️
#production 26.45352% <4%> (-0.05209%) ⬇️
#test 100% <ø> (ø) ⬆️

Copy link
Contributor

@RussKie RussKie left a comment

Choose a reason for hiding this comment

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

LGTM

/// This inherits from the base ControlAccessibleObject
/// to have all base functionality.
/// </summary>
internal class FormAccessibleObject : ControlAccessibleObject
Copy link
Contributor

Choose a reason for hiding this comment

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

Can this be placed in a separate file? e.g. Form.FormAccessibleObject.cs

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes, I'll change this file location.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This file location is changed.

@RussKie RussKie added the waiting-author-feedback The team requires more information from the author label Oct 17, 2019
@vladimir-krestov vladimir-krestov changed the title Implementing UIA supporting for Form control WIP: Implementing UIA supporting for Form control Oct 17, 2019
@ghost ghost removed the waiting-author-feedback The team requires more information from the author label Oct 17, 2019
@vladimir-krestov vladimir-krestov added the 🚧 work in progress Work that is current in progress label Oct 17, 2019
@vladimir-krestov vladimir-krestov changed the title WIP: Implementing UIA supporting for Form control Implementing UIA supporting for Form control Oct 17, 2019
@vladimir-krestov vladimir-krestov removed the 🚧 work in progress Work that is current in progress label Oct 17, 2019
@vladimir-krestov
Copy link
Contributor Author

Needs review and approve before testing.

RussKie
RussKie previously approved these changes Oct 17, 2019
@vladimir-krestov vladimir-krestov added the waiting-for-testing The PR is awaiting manual testing by the primary team; no action is yet required from the author(s) label Oct 17, 2019
@RussKie
Copy link
Contributor

RussKie commented Oct 18, 2019

Please don't forget to squash

@vladimir-krestov
Copy link
Contributor Author

I'll squash commits after testing before final approval. Thanks for reminding.

@vladimir-krestov
Copy link
Contributor Author

Removed Bounds implementation because it breaks RT test cases. At the moment Form AccessibleObject the same as before, but supports UIA provider.

@merriemcgaw
Copy link
Member

business case approved. Please add ask-mode when ready with the tested fix.

zsd4yr
zsd4yr previously approved these changes Oct 18, 2019
@RussKie RussKie added waiting-review This item is waiting on review by one or more members of team and removed waiting-review This item is waiting on review by one or more members of team labels Oct 22, 2019
@vladimir-krestov vladimir-krestov removed the waiting-for-testing The PR is awaiting manual testing by the primary team; no action is yet required from the author(s) label Oct 22, 2019
@vladimir-krestov
Copy link
Contributor Author

Testers approved the fix. ✔️
But Bounds property and BoundingRectangle property don't match.
BoundingRectangle is the correct yellow rectangle of Inspect.
Bounds made as before the fix. All automation tests passed.

@merriemcgaw merriemcgaw added servicing-consider .NET Shiproom label indicating a PR seeks to enter into a branch under Tell-Mode criteria ask-mode and removed waiting-approval servicing-consider .NET Shiproom label indicating a PR seeks to enter into a branch under Tell-Mode criteria labels Oct 22, 2019
@leecow leecow added the servicing-approved .NET Shiproom approved the PR for merge label Oct 22, 2019
@RussKie RussKie removed the ask-mode label Oct 22, 2019
@RussKie RussKie merged commit 274b4c1 into release/3.1 Oct 22, 2019
@RussKie RussKie deleted the dev/v-vlkres/FormUIAAccessibleObject branch October 22, 2019 23:55
@ghost ghost locked as resolved and limited conversation to collaborators Feb 3, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

servicing-approved .NET Shiproom approved the PR for merge

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants