Add tests for Accessibility Insights' FastPass

[carlos-zamora]

Accessibility Insights has a neat tool called FastPass where it can scan the existing UI for common accessibility errors. FastPass is powered by Axe.Windows. This PR adds Axe.Windows to our project and adds a handful of accessibility tests to navigate the app (using WinAppDriver) then scan the UI using Axe.Windows.

Additionally, each error Axe.Windows finds is output to an a11ytest file that can be opened by Accessibility Insights to tell you what error was found and where the error is. These files are output to \bin\x64\Debug\AxeWindowsOutputFiles\
 
There's a few tests that fail already. I've added comments explaining why they fail and saying that they are expected.

[github-actions]

@check-spelling-bot Report

🔴 Please review

See the 📂 files view or the 📜action log for details.

Unrecognized words (1)

etstandard

To accept ✔️ these unrecognized words as correct, run the following commands

... in a clone of the git@github.com:microsoft/terminal.git repository
on the dev/cazamor/a11y/fastpass branch (ℹ️ how do I use this?):

curl -s -S -L 'https://raw.githubusercontent.com/check-spelling/check-spelling/v0.0.21/apply.pl' |
perl - 'https://github.com/microsoft/terminal/actions/runs/6385007194/attempts/1'

Pattern suggestions ✂️ (1)

You could add these patterns to .github/actions/spelling/patterns/e8709bfb6db774e61c6a85f5b99801672950c84c.txt:

# Automatically suggested patterns
# hit-count: 1 file-count: 1
# tput arguments -- https://man7.org/linux/man-pages/man5/terminfo.5.html -- technically they can be more than 5 chars long...
\btput\s+(?:(?:-[SV]|-T\s*\w+)\s+)*\w{3,5}\b

Warnings (1)

See the 📂 files view or the 📜action log for details.

ℹ️ Warnings	Count
ℹ️ candidate-pattern	1

See ℹ️ Event descriptions for more information.

✏️ Contributor please read this

By default the command suggestion will generate a file named based on your commit. That's generally ok as long as you add the file to your commit. Someone can reorganize it later.

⚠️ The command is written for posix shells. If it doesn't work for you, you can manually add (one word per line) / remove items to expect.txt and the excludes.txt files.

If the listed items are:

• ... misspelled, then please correct them instead of using the command.
• ... names, please add them to .github/actions/spelling/allow/names.txt.
• ... APIs, you can add them to a file in .github/actions/spelling/allow/.
• ... just things you're using, please add them to an appropriate file in .github/actions/spelling/expect/.
• ... tokens you only need in one place and shouldn't generally be used, you can add an item in an appropriate file in .github/actions/spelling/patterns/.

See the README.md in each directory for more information.

🔬 You can test your commits without appending to a PR by creating a new branch with that extra change and pushing it to your fork. The check-spelling action will run in response to your push -- it doesn't require an open pull request. By using such a branch, you can limit the number of typos your peers see you make. 😉

If the flagged items are 🤯 false positives

If items relate to a ...

• binary file (or some other file you wouldn't want to check at all).

  Please add a file path to the excludes.txt file matching the containing file.

  File paths are Perl 5 Regular Expressions - you can test yours before committing to verify it will match your files.

  ^ refers to the file's path from the root of the repository, so ^README\.md$ would exclude README.md (on whichever branch you're using).

• well-formed pattern.

  If you can write a pattern that would match it,
  try adding it to the patterns.txt file.

  Patterns are Perl 5 Regular Expressions - you can test yours before committing to verify it will match your lines.

  Note that patterns can't match multiline strings.

[zadjii-msft]

I'm a glutton for the pain of hand-editing .*proj files, so these would otherwise just be nits on what is a solid PR that I'm super excited about

[zadjii-msft]

yikes, can we at the very least add path/to/packages\Axe.Windows.2.1.3 to src\common.nugetversions.props, so that we can just do

<HintPath>$(AxeWindowsPathRoot)\lib\netstandard20\Axe.Windows.Actions.dll</HintPath>

?

[zadjii-msft]

revert me pls

[zadjii-msft]

similar with the path to this package

[zadjii-msft]

do all these System.* packages need the full path too? That seems... wrong.

[zadjii-msft]

huh, did we really not have one of these for this project before? I feel like at least one of the existing packages.config that we're using must have applied to this project, right?

either

• packages\packages.config
• dep\nuget\packages.config

and I forget what the difference is