{"id":106,"date":"2021-07-19T12:57:23","date_gmt":"2021-07-19T19:57:23","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/engineering-at-microsoft\/?p=106"},"modified":"2021-07-19T08:58:30","modified_gmt":"2021-07-19T15:58:30","slug":"shifting-accessibility-left-with-accessibility-insights","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/engineering-at-microsoft\/shifting-accessibility-left-with-accessibility-insights\/","title":{"rendered":"Shifting accessibility left with Accessibility Insights"},"content":{"rendered":"<p><a href=\"https:\/\/www.accessibilityinsights.io\/\">Accessibility Insights<\/a> is an open-source suite of tools to help developers deliver accessible software. We originally developed these tools as proprietary and internal to Microsoft, but in 2019 we decided to open-source them and share them with the world.<\/p>\n<p>We were motivated by Microsoft\u2019s mission to \u201cempower every person and every organization on the planet to achieve more.\u201d We realized that to empower every person, we need to help support all developers in building more accessible products. The power of open-source software is increasing transparency into our methodologies and encouraging trust in our tools. It also allows us to accept contributions and to allow developers to experiment with our tools. These products belong to the community now and I am excited to see how we will develop them together over the coming years.<\/p>\n<h3>FastPass: Shifting accessibility left for developers<\/h3>\n<p>While anyone can use Accessibility Insights, most of our users are software developers. We believe that we can only solve the problem of inaccessible software by shifting accessibility left into the software design and development cycle. Our vision is that a software developer can use Accessibility Insights every time they make a change to the code to ensure that they are not introducing issues that will block some users from using their products.<\/p>\n<p>That\u2019s why we created FastPass\u2014a five minute process for identifying some of the most common accessibility issues. The first step of FastPass is an automated scan, which includes detailed how-to-fix guidance and the ability to file an issue to be shared with another developer. The second step is the <a href=\"https:\/\/accessibilityinsights.io\/docs\/en\/web\/getstarted\/fastpass\/#complete-the-manual-test-for-tab-stops\" rel=\"noopener\" target=\"_blank\">Tab Stops test<\/a>\u2014a visualization of how a person would use a keyboard to navigate the user interface. This process is quick enough that a developer can use it on any UI change.<\/p>\n<p><figure id=\"attachment_114\" aria-labelledby=\"figcaption_attachment_114\" class=\"wp-caption aligncenter\" ><a href=\"https:\/\/devblogs.microsoft.com\/engineering-at-microsoft\/wp-content\/uploads\/sites\/72\/2021\/07\/automated-checks-start.png\"><img decoding=\"async\" src=\"https:\/\/devblogs.microsoft.com\/engineering-at-microsoft\/wp-content\/uploads\/sites\/72\/2021\/07\/automated-checks-start.png\" alt=\"Accessibility Insights for Web split screen showing site being reviewed on the left, and automated checks guidance on the right.\" width=\"1923\" height=\"1054\" class=\"alignnone size-full wp-image-124\" srcset=\"https:\/\/devblogs.microsoft.com\/engineering-at-microsoft\/wp-content\/uploads\/sites\/72\/2021\/07\/automated-checks-start.png 1923w, https:\/\/devblogs.microsoft.com\/engineering-at-microsoft\/wp-content\/uploads\/sites\/72\/2021\/07\/automated-checks-start-300x164.png 300w, https:\/\/devblogs.microsoft.com\/engineering-at-microsoft\/wp-content\/uploads\/sites\/72\/2021\/07\/automated-checks-start-1024x561.png 1024w, https:\/\/devblogs.microsoft.com\/engineering-at-microsoft\/wp-content\/uploads\/sites\/72\/2021\/07\/automated-checks-start-768x421.png 768w, https:\/\/devblogs.microsoft.com\/engineering-at-microsoft\/wp-content\/uploads\/sites\/72\/2021\/07\/automated-checks-start-1536x842.png 1536w\" sizes=\"(max-width: 1923px) 100vw, 1923px\" \/><\/a><figcaption id=\"figcaption_attachment_114\" class=\"wp-caption-text\"><em>Accessibility Insights for Web automated checks<\/em><\/figcaption><\/figure><\/p>\n<h3>No false positives<\/h3>\n<p>It is essential that developers can trust that the issues we identify need to be addressed to ensure accessibility. We are committed to ensuring that our automated checks are clear of false positives, and we employ scanning libraries, such as <a href=\"https:\/\/www.deque.com\/axe\/\">axe-core from Deque Systems<\/a>, that share that commitment. We can promise that if Accessibility Insights flags an issue, it should be addressed.<\/p>\n<p>Of course, automated testing and a keyboard pass only provides so much coverage. In our Web product we have our <a href=\"https:\/\/accessibilityinsights.io\/docs\/en\/web\/getstarted\/assessment\/\">Assessment feature<\/a> that leads you through a guided evaluation covering all the success criteria in <a href=\"https:\/\/www.w3.org\/WAI\/WCAG2AA-Conformance\">WCAG 2.1 AA<\/a>. Along the way, there are detailed descriptions of how to test your application and examples of how to fix issues. There are also \u201cWhy it matters\u201d and \u201cFrom a user\u2019s perspective\u201d sections to help gain a deeper understanding of how people could be impacted by these issues.<\/p>\n<p><a href=\"https:\/\/accessibilityinsights.io\/docs\/en\/web\/overview\/\">Accessibility Insights for Web<\/a> is available as a browser extension for both Chrome and Microsoft Edge and runs on Windows, Mac, and Linux. It is part of a larger suite of open-source accessibility products. <a href=\"https:\/\/accessibilityinsights.io\/docs\/en\/windows\/overview\/\">Accessibility Insights for Windows<\/a> is available as a desktop application and includes <a href=\"https:\/\/github.com\/microsoft\/axe-windows\">axe-windows<\/a>, our scanning library that can be used separately. We also have a <a href=\"https:\/\/www.npmjs.com\/package\/accessibility-insights-scan\">CLI<\/a> for running tests in a CI\/CD scenario and providing the same results and reporting experience. Our newest addition is <a href=\"https:\/\/accessibilityinsights.io\/docs\/en\/android\/overview\/\">Accessibility Insights for Android<\/a> for your mobile applications if you are developing on Windows, Mac, or Linux. In the future, we will have more blog posts with more information about all the Accessibility Insights products.<\/p>\n<p>Please visit <a href=\"https:\/\/accessibilityinsights.io\">https:\/\/accessibilityinsights.io<\/a> to download these tools and to learn more. <strong>Want to come work with us?<\/strong> Check out <a href=\"https:\/\/aka.ms\/1esjobs\">https:\/\/aka.ms\/1esjobs<\/a> for open positions.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>We believe that we can only solve the problem of inaccessible software by shifting accessibility left into the software design and development cycle. In this post, Mark Reay describes how our open-source offering, Accessibility Insights, can help.<\/p>\n","protected":false},"author":64456,"featured_media":113,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[4,6,5],"class_list":["post-106","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-engineering-at-microsoft","tag-1es","tag-a11y","tag-accessibility"],"acf":[],"blog_post_summary":"<p>We believe that we can only solve the problem of inaccessible software by shifting accessibility left into the software design and development cycle. In this post, Mark Reay describes how our open-source offering, Accessibility Insights, can help.<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/engineering-at-microsoft\/wp-json\/wp\/v2\/posts\/106","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/engineering-at-microsoft\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/engineering-at-microsoft\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/engineering-at-microsoft\/wp-json\/wp\/v2\/users\/64456"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/engineering-at-microsoft\/wp-json\/wp\/v2\/comments?post=106"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/engineering-at-microsoft\/wp-json\/wp\/v2\/posts\/106\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/engineering-at-microsoft\/wp-json\/wp\/v2\/media\/113"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/engineering-at-microsoft\/wp-json\/wp\/v2\/media?parent=106"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/engineering-at-microsoft\/wp-json\/wp\/v2\/categories?post=106"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/engineering-at-microsoft\/wp-json\/wp\/v2\/tags?post=106"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}