What's New in Version 2.2

This release introduces new ways to test and maintain accessibility for your web-based content, improve your project management, and understand your data. Learn more about the changes in 2.2 below.

New and improved

• Design evaluations: find your requested design evaluations in the platform. On the Design evaluations page you can check the status of your evaluations and review the results for completed evaluations.
• PDF accessibility checker: discover PDFs on your website using the advanced scanner or upload them manually. Test up to 10 PDFs for accessibility and access reports highlighting passed and failed criteria. After you test the PDF, you can request PDF remediation directly from the PDF page. Request support for more information on purchasing more tests and remediation services.
• Multi-factor authentication: increase security with the option to use multi-factor authentication for non-SSO users.

Enhancements

• Azure DevOps connections now support increased functionality. You can now: 
  • Set required fields for your projects.
  • Map Azure DevOps and platform task progress.
• The Monitoring page now:
  • Helps you understand changes in your accessibility health score and finding trends data by:
    • Notifying you with WCAG conformance level changes. 
    • Showing you the number of pages for each monitoring scan in the trend tables.
  • Has collapsable Finding trends table and Accessibility health trend table to improve navigation on the Monitoring page.
  • Lists the five most recent monitoring scans showing the date of the scan, scan score, number of findings, number of pages in the scan, and a link to the scan results.
• You can now find the date and time of your next scheduled monitoring scan from the Portfolio page. Select the Monitoring field on your digital property to show the date and time of the next scan.
• The browser extension is now easier to install (Chrome extension only), configure, and use. Learn more about the browser extension update.
• Manual findings information is now refined to provide more impactful and usable information.
• Expected results are no longer provided in manual evaluation results because the information is similar to the recommendations. Any unique information from the Expected Results field is now included in the recommendations. Removing expected results increases the speed and efficiency of reporting. Learn more about the definitions for manual evaluation results.