v2.5.4

June 18th 2019 Release [v2.5.4]

• Install in Microsoft Edge Insider
• Install in Chrome

Welcome to the June 18th Release of Accessibility insights for Web

Highlights

• New Automated Checks Report

Checkout our new report that incorporates a better way to show rules failed and failure instances. The new report also adds a tag for WCAG 2.1 rules and reflows the content when resized.

• Feature requests

  • Add color box to the hex codes for the color-contrast rule(#579)
  • Add line breaks to exported results descriptions (#698)

• New Content

  • New WCAG 2.1 rule from axe-core: autocomplete-valid
  • New guidance for semantics and sequence (#718)

Bug Fixes

• Update semantic CSS guidance content (#771), closes #697
• Fixed product title on guidance page in Canary extension (#714), closes #625
• Users can now inspecting same element twice (#713), closes #627
• Switcher state is now updated correctly (on component did update) (#689), closes #659
• Switcher state is now updated correctly (on view change) (#802), closes #786
• Updated aria label on switcher (#690), closes #680
• Fixed typo (dislosure -> disclosure) (#800), closes #788
• Increase Report Download Size for Chrome (#766), closes #730

v2.4.1

May 20th 2019 Release [v2.4.1]

Install for Web

Features

• fastpass: subtitle suggesting full assessment in fast pass automated checks UI (#632), closes #385
• microsoft-edge Add manifest, icons, build script for Microsoft Edge store package (#648), closes #606
• issue-details-dialog Hide back & next button for elements with only 1 failure (#652), closes #549

Bug Fixes

• guidance content shows "Cannot find t" (#662), fixes #660
• fix typo on in-app text and a typo in git-branch-setup.md (#678), fixes #672
• update FastPass automated checks text (#677)

Thank you

Thank you to the following contributors that helped make Accessibility Insights even better:

• mdecorte (#678 )

v2.3.0

May 1st 2019 Release [v2.3.0]

Install for Web

Welcome to the May 1st, 2019 release of Accessibility Insights for Web.

Highlights

• Accessibility Insights for Web in Microsoft Edge Insider!

You can now use Accessibility Insights for Web in the Microsoft Edge Insider browser (version 75 or later).

We also added a incompatible message for when the popup is opened in older Microsoft Edge browsers PR #637

• Completed Feature request #519: Add Success criteria number in Target page Pop-Up

We received the feature request that it would be good to have the number of the WCAG 2.1 success criterion in the Pop-up that apppears in the target page when you select a failure. After reviewing with the team and getting design input, we have added the Success Criterion number in the dialog.

Bug Fixes

• Ensure that switcher change between Assessment and FastPass announce changes correctly #570
• Add '/issues' if the base url in GitHub issue filing settings does not have it #621
• Fixed Color contrast issues on high contrast mode in assessment overview #624

v2.2.1

April 26th 2019 Release [v2.2.1]

Install for Web

Welcome to the April 26th, 2019 release of Accessibility Insights for Web.

Highlights

-New Issue filing experience
Accessibility Insights for Web makes it easy to file issues directly from automated check failures.
Users can now select between GitHub issues or Azure DevOps to file issues with all the relevant information of a failure.

Bug Fixes

• Fix: assessment overview help box has too much top padding #600
• Fix: a11y issue on issue filing setting dialog #590
• Fix: details view crash when target page is closed #598
• Fix: Secondary text color mismatches design color palette #594
• Fix: Jerky Dialog Box #578
• Fix: vulnerabilities found by npm audit #559
• Fix: error on the console when user issue filing dialog. #552
• Fix: remove guidance for heading best practice rule #520
• Fix: update app bar styling and finish #516
• Fix: update overview styling and finish #515
• Fix: TabStore onTabUpdate gives an exception #484
• Fix: details dialog fails to render icons on pages with restrictive CSP #488
• Fix: Handle out of range heading levels #503
• Add Missing success criteria link #507

v2.1.2

April 1st 2019 Release [v2.1.2]

Install for Web

Welcome to the April 1st, 2019 release of Accessibility Insights for Web. Key highlights include:

Highlights

• Updated Automated checks to Axe 3.2.2

This update includes a fix to the following false negatives:

• 'image-alt' rule: should fail for alt=" " (white space as alt text)
• 'group-labelledby': Added a check in 'checkboxgroup' rule to fail corner cases

And surfaces two new rules in the automated checks:

• aria-hidden-focus: Ensures aria-hidden elements do not contain focusable elements.
• landmark-complementary-is-top-level: Ensures that aside elements or elements with role=complementary are not an internal part of another ARIA landmark.

Finally, there are also some rule bug fixes and improvements:

• Elements accessible name is now considered when labels are hidden
• label rule now does not fail for input elements with explicit hidden label despite having accessible label by other means
• label rule now does not fail for input having explicit label with role presentation
• Usage of aria-role description attribute is now allowed on certain elements
• Updated WCAG tags for frame-title rule

Bug Fixes

• Prevent "best practice" landmark rules from generating failures #390
• Make Failure details more visible by changing background color PR #386
• Changed default values in columns from hyphen to "(no value)" for better accessibility PR #388
• Fixed issue where stuck at Scanning 98% when displaying automated checks from an assessment scan done by 2.0.5 #416
• Added distinguished, date-time-based filenames to reports PR #398
• Fixed issue where scroll bar for requirements dissapeared in newest Chrome update #413
• Added message to indicate users assessment tests will automatically pass when no instances are found PR #414

v2.1.0: Prevent "best practice" landmark rules from generating failures (#407)

#### Pull request checklist

- [x] Addresses an existing issue: Fixes #390
- [x] **N/A** Added relevant unit test for your changes. (`npm run test`)
- [x] Verified code coverage for the changes made. Check coverage report at: `<rootDir>/test-results/unit/coverage`
- [x] Ran precheckin (`npm run precheckin`)
- [x] **N/A** Added screenshots/GIFs for UI changes.

#### Description of changes

This marks the rules noted in #390 as "BestPractice", which practically speaking disables them from consideration by the extension (the `RuleSifter` class omits them).

#### Notes for reviewers

Verified against the repro site noted in #390 that this resolves the unique-landmark violations there and cooperates with loading persisted assessment state that includes the removed requirements.

v2.0.5

Fix casing for details view css (#367)