Add hardware support smoke testing instructions#18138
Merged
Conversation
Contributor
|
A browser (Chrome) uses IA2, Win11 Notepad uses UIA. The NVDA GUI and run dialogue use MSAA. Testing all three quickly ensures functionality of major accessibility APIs. |
Member
|
@codeofdusk Edge web views use IA2 as well. |
Co-authored-by: Sean Budd <sean@nvaccess.org>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Link to issue number:
Part of #16304
Summary of the issue:
We do not have manual smoke testing notes for ensuring NVDA is supported on various forms of hardware.
This PR adds smoke testing notes for hardware