Releases: microsoft/accessibility-insights-action
Accessibility Insights for Azure DevOps Extension v3.1.2
Accessibility Insights for Azure DevOps v3.1.2
Get the extension in the Visual Studio Marketplace (Microsoft-Internal Only)
Welcome to the November 11th, 2022 release of Accessibility Insights for Azure DevOps!
Highlights
In v3.1.2, we have made the following bug fixes and improvements to:
- Fix a bug in the classic pipelines UI that forces the AuthType input to be set (#1359)
- Update labels in the classic pipeline UI to be clearer (#1371)
- Fix the viewport size to standardize 1920x1080 for scanning, matching the WebInsights (formerly WCP) defaults (#1379)
- Improve error messaging and scan behavior when Authentication fails (#2270, #2273)
Full Changelog: v3.1.1-sources-ado...v3.1.2-sources-ado
Accessibility Insights Action v3.1.1
Accessibility Insights Action v3.1.1
Welcome to the October 18th, 2022 release of Accessibility Insights Action!
Highlights
In v3.1.1, we have made the following bug fixes:
- Update to accessibility-insights-scan v1.4.1, which fixes a
NavigationErrorissue when crawling some dynamic pages. (#1342) - Improve error logging by surfacing error messages from accessibility-insights-scan. (#1341) [ #1315 ]
Accessibility Insights for Azure DevOps Extension v3.1.1
Accessibility Insights for Azure DevOps v3.1.1
Get the extension in the Visual Studio Marketplace (Microsoft-Internal Only)
Welcome to the October 18th, 2022 release of Accessibility Insights for Azure DevOps!
Highlights
In v3.1.1, we have made the following bug fixes:
- Update to accessibility-insights-scan v1.4.1, which fixes a
NavigationErrorissue when crawling some dynamic pages. (#1342) - Improve error logging by surfacing error messages from accessibility-insights-scan. (#1341) [ #1315 ]
Accessibility Insights Action v3.1.0
Accessibility Insights Action v3.1.0
Welcome to the October 3rd, 2022 release of Accessibility Insights Action!
Highlights
New automated checks rules
In v3.1.0, we have made changes to enable 2 more axe-core rules, to help you catch even more issues sooner (#1321):
Accessibility Insights for Azure DevOps Extension v3.1.0
Accessibility Insights for Azure DevOps v3.1.0
Get the extension in the Visual Studio Marketplace (Microsoft-Internal Only)
Welcome to the October 3rd, 2022 release of Accessibility Insights for Azure DevOps!
Highlights
New automated checks rules
In v3.1.0, we have made changes to enable 2 more axe-core rules, to help you catch even more issues sooner (#1321):
Changes:
Accessibility Insights for Azure DevOps Extension v3.0.0
Accessibility Insights for Azure DevOps v3.0.0
Get the extension in the Visual Studio Marketplace (Microsoft-Internal Only)
Welcome to the August 11th, 2022 release of Accessibility Insights for Azure DevOps!
Highlights
In v2.1.0, we have made changes to:
- Upgrade to Node 16
- Upgrade to axe-core 4.4.1, which includes various additional accessibility checks and bug fixes for previous false-positives
- Improve the report artifact experience to include only relevant files
For new users, see how to use the Azure DevOps extension documentation for more information on how to get started.
Changes:
- 21b6bf5 feat(ado-auth-part-2): Upgrade ADO Extension to use Node16 (#1262)
- 09d8bb9 chore: Clarify that the scan-timeout is in milliseconds in gh-action-usage.md (#1257)
- 1951038 Update ado-extension-usage.md (#1242)
This list of changes was auto generated.
Accessibility Insights Action v3.0.0
Accessibility Insights Action
Welcome to the July 11th, 2022 release of Accessibility Insights Action!
Breaking Changes
This release has some big changes that cause your settings from v2.3.0 to be incompatible with v3.0.0, so be sure to check out our migration guide!
Highlights
The Accessibility Insights Action helps integrate automated accessibility tests in your GitHub workflow. This extension uses the axe-core rules engine to scan websites and web apps for common accessibility issues.
In v3.0.0, we have made changes to:
- Update to accessibility-insights-scan v1.1.0, which uses axe-core 4.4.1 and includes 17 false-positive fixes, 1 rule change, and 1 general improvement. Check the axe-core 4.4.0 and axe-core 4.4.1 release notes for more details. This update also requires the Action to be run with Node >= 16.x. See gh-action-usage.md to ensure that the correct version of Node is being used (#1156, #1228)
- Provide Job Summary functionality, which outlines the number of URLs scanned and information of all relevant failed instances (#1204)
- Make builds fail when accessibility issues are detected by default. To change this, set the
fail-on-accessibility-errorinput to false (#1219) - Add Hosting Mode and improve input names to clarify which inputs are grouped together, and update documentation (#1212, #1221, #1227, #1231)
Accessibility Insights for Azure DevOps Extension v2.0.6
Accessibility Insights for Azure DevOps - Beta v2.0.6
Get the extension in the Visual Studio Marketplace (Microsoft-Internal Only)
Welcome to the May 10th, 2022 release of Accessibility Insights for Azure DevOps - Beta!
Breaking Changes
This release has some big changes that cause your settings from v1.1.1 to be incompatible with v2.0.6, so be sure to check out our migration guide!
Highlights
The Accessibility Insights for Azure DevOps Extension helps integrate automated accessibility tests in your Azure pipeline. This extension uses the axe-core rules engine to scan websites and web apps for common accessibility issues.
In v2.0.6, we have made changes to:
- No longer use Pull Request comments to summarize scan results; instead, you can find result summaries in the improved Pipeline task log and in the "Extensions" tab of your pipeline run
- No longer require a Service Connection option for the task to work
- Make newly detected accessibility issues fail the task. To avoid failures, either use a Baseline File or set failOnAccessibilityError to false.
- Improve our input names, user-options view, and documentation
- Add a method for telemetry collection
For new users, see how to use the Azure DevOps extension documentation for more information on how to get started.
Changes:
- 7c86844 fix: Avoiding the creation of multiple output directories (#1171)
- 19f2ac0 feat(ado-ext-telemetry): add a v1 to v2 migration guide for the ADO extension (#1136)
- b72ddfc feat(ado-ext-telemetry): Making failOnAccessibilityError true by default (#1088)
- 559dd6e feat(ado-ext-telemetry): Avoiding configuration of mutually exclusive parameters (#1122)
- 2994b6c feat(ado-ext-telemetry): Embed upload artifact into task (#1085)
- 7e9a419 feat(ado-ext-telemetry): Grouping rarely used options under Advanced Options group (#1092)
- 928a51f feat(ado-improvement-1): Remove PR Comments, add output to logs (#1041)
- 57e0a08 chore: add script to help run ADO extension locally (#1027)
- d3e8fd0 chore(deps): bump express from 4.17.3 to 4.18.0 (#1157)
See More
- 2dff5e4 fix: staticSiteUrlRelativePath validation issue (#1181)
- 64d39c2 fix(gha): prevent input validator treating unspecified url input as specified (#1163) [ #0000 ]
- 4a5b285 fix: apply yarn resolutions at runtime (#1162) [ #1141, #0000 ]
- 6773cb0 fix(ado-ext-telemetry): fix failOnAccessibilityError interaction with baseline files (#1160) [ #1149 ]
- 3831371 feat(ado-ext-telemetry): Updating input validation to run before scan starts (#1149)
- 93fe067 fix: Fixing one instance of async vulnerability (#1142)
- 0dff9f4 feat(ado-ext-telemetry): Update documentation to reflect new state of Extension (#1130)
- 63a6eb1 fix: Allow manual test extension pipeline deployments without requiring version number (#1101)
- 2ad07ce fix: canary pipeline greater than syntax (#1097)
- fc1a26c Update ado-extension-usage documentation (#1083)
- 7fdb965 Fix invalid yaml syntax in dependabot.yml (#1072)
- d149e9a fix: rules with failures count in markdown and console output (#1077)
- c97c4d1 feat(ADO-improvements-1): update documentation for siteDir and scanUrlRelativePath for Windows Agents (#1074)
- eb20e8f feat(ado-improvements-1): Add Build summary upload to ADO (#1055) [ #0000 ]
- 2c492bf feat(ado-improvements-1): Remove unnecessary auth input from ADO extension (#1045)
- b7ea9ae feat(ado-improvements-1): Map LogLevel to ADO log output (#1042)
- bf955bb fix: Add missing PR scenarios (#985)
- bb94c01 feat(pr-baseline-2): fix behavior when multiple reporters have errors (#943) [ #0000 ]
- e0fcd0b feat(pr-baseline-2): Add documentation for baseline in extension (#932)
- 100865a Update vulnerable packages (#892)
Accessibility Insights for Azure DevOps Extension v1.1.1
Accessibility Insights for Azure DevOps Extension
Get the extension in the Visual Studio Marketplace
Welcome to the November 2nd 2021 release of Accessibility Insights for Azure DevOps Extension!
Bug Fixes
- Fix failure counts in PR comment (#951)
Accessibility Insights for Azure DevOps Extension v1.1.0
Accessibility Insights for Azure DevOps Extension
Get the extension in the Visual Studio Marketplace
Welcome to the November 1st release of Accessibility Insights for Azure DevOps Extension!
Highlights
The Accessibility Insights for Azure DevOps Extension helps integrate automated accessibility tests in your Azure pipeline. The Accessibility Insights for Azure DevOps Extension uses the axe-core rules engine to scan websites and web apps for common accessibility issues.
In v1.1.0, we have added functionality to:
- Support a baseline file that tracks known accessibility violations within the scope of pages that are scanned (note that baseline support is limited to static web pages at this time and is not applicable to pages that contain any dynamic content).
- Identify changes in accessibility scan violations between the current state and the baseline file.
- Highlight new accessibility scan violations in the combined scan report.
- Provide guidance (via PR comments) to help the PR author to either investigate/fix new accessibility violations or to update the baseline file, as appropriate.
Check the how to use the Azure DevOps extension documentation for more information on how to get started.
Changes in this release
- Fix behavior when multiple reporters have errors (#943)
- Support workflow enforcement in GitHub repos (#942)
- Add support to handle escape artifacts in the url (#939)
- Update baseline file after crawling (#938)
- Plumb baselineFile from config to crawler (#936)
- Add ArtifactsInfoProvider to get artifacts URL in ADO PR comment (#935)
- Add documentation for baseline in extension (#932)
- Plumb baseline evaluation to progress reporter (#933)
- Consume scanner package 0.10.3 (#931)
- Use baseline types from scan package (#927)
- Set a singleWorker option in Action/Extension (#928)
- Update scan, report, and inversify packages (#924)
- Modify ADO PR comments to include baseline info (#909)
- Add singleWorker Option (#900)
- Enforce workflow with baseline (#898)
- Add Baseline input parameters (#885)