6a9554dc47
#### Details <!-- Usually a sentence or two describing what the PR changes --> Migrated release pipeline to 1ES PT as per the changes mentioned in the documentation link provided for the 1ES pipeline migration. Test Run link: https://dev.azure.com/mseng/1ES/_build/results?buildId=29327650&view=results ##### Motivation <!-- This can be as simple as "addresses issue #123" --> [Feature 2211959](https://dev.azure.com/mseng/1ES/_workitems/edit/2211959) ##### Context <!-- Are there any parts that you've intentionally left out-of-scope for a later PR to handle? --> <!-- Were there any alternative approaches you considered? What tradeoffs did you consider? --> #### Pull request checklist <!-- If a checklist item is not applicable to this change, write "n/a" in the checkbox --> - [x] Addresses an existing issue: [Feature 2211959](https://dev.azure.com/mseng/1ES/_workitems/edit/2211959) - [ ] Added relevant unit test for your changes. (`yarn test`) - [ ] Verified code coverage for the changes made. Check coverage report at: `<rootDir>/test-results/unit/coverage` - [x] Ran precheckin (`yarn precheckin`) --------- Co-authored-by: Vikash Yadav <95463767+v-viyada@users.noreply.github.com> |
||
|---|---|---|
| .github | ||
| .vscode | ||
| .yarn | ||
| dev | ||
| docs | ||
| guardian/SDL | ||
| icons | ||
| packages | ||
| pipelines | ||
| tools | ||
| .eslintrc.js | ||
| .gitattributes | ||
| .gitignore | ||
| .prettierignore | ||
| .yarnrc.yml | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| LICENSE | ||
| README.md | ||
| SECURITY.md | ||
| copyright-header.txt | ||
| jest.config.base.js | ||
| license-check-and-add-config.json | ||
| package.json | ||
| prettier.config.js | ||
| tsconfig.base.json | ||
| yarn.lock | ||
README.md
Accessibility Insights Azure DevOps (ADO) extension
About
The Accessibility Insights Azure DevOps (ADO) extension helps integrate automated accessibility tests in your Azure pipeline. You can configure the ADO extension to scan a single page or crawl an entire site. This can work for static HTML files in your repository, a local web server, or remote URLs. It is currently only available for Microsoft internal teams.
The ADO extension uses the axe-core rules engine to scan websites and web apps for common accessibility issues.
While automated checks can detect some common accessibility problems such as missing or invalid properties, most accessibility problems can only be discovered through manual testing. The best way to evaluate web accessibility compliance is to complete an assessment using Accessibility Insights for Web.
For Microsoft internal teams, visit how to use the Azure DevOps (ADO) extension.
Contributing
To build and test, visit developer docs.
Visit CONTRIBUTING.md for more information about the contributor license agreement.