 Welcome everyone to the accessibility testing isn't hard by Sugistri or Kodopati. We are glad you could all join us today without any further delay over to you Sugistri all the way. Thank you Shama. So let me share the screen. Hi everyone, very good afternoon and thank you so much for joining me to know more about accessibility testing tools. So myself Sugistri Kodopati, I have been associated with DQ and accessibility for 12 years now. And I started my career as a developer and then moved into different roles at DQ. And for the last eight years I have been managing and taking care of DQ India located in Hyderabad. So as the title of this session says, accessibility testing is not hard. I believe those words very strongly because of some of the tools like AX in the market. So AX is a open source free library available in accessibility community. And so I want to cover all the free access suite of products today. And so that it helps you in automating your accessibility and our product testing. So as part of this session in next 20 minutes I will be covering outline of AX, AX Core API, AX Linter, AX Beta and AX for Android. All these are freely available. And my hope is that if everyone starts using these tools, utilize these tools, then we all together can make the digital world a better place for people with disabilities. And this is the reason I have chosen this topic for today. So before getting into the real topic, let me take a minute to introduce DQ to all of you. So we have been in this exclusive accessibility business for more over 20 years now. And we believe in digital equality wherein we enable people with disabilities to access information on the website or mobile or on any digital platform equally without any discrimination. And we support both accessibility products and services. So when it comes to services, we do audits of web applications, mobile applications, documents, and then design wireframes. And we do provide instructor led trainings as well. And we have DQ University, which is a self-pacing online accessibility curriculum available there. And we also support strategic decisions and directions and implementations through accessibility program, office offering. And when it comes to products, we do have enterprise products that helps you under your organization to monitor the accessibility status of your products. And also we have products to support you throughout the development processes like early stage of your software development lifecycle. So we are a very proud sponsor of this event happening today and tomorrow, Selenium Conference. So we have a booth available and my colleagues, Abhinraj Chawjary and Somah Alapati both are available at booth in case if you want to know more about our enterprise products and its features. So feel free to drop by in case if you have any queries. So but in this session, I'll be only covering the outline of the free products for the benefit of the community. All right. So many of you might already know about accessibility, but just for the benefit of everyone, let me take a minute to explain it. So, you know, accessibility is all about enabling people, regardless of their disability, so that they get the same information and use the same functionality on, you know, on any device. So basically, digital accessibility or web accessibility makes sure that it is everything, all the information is available for anyone, regardless of the disability or ability and on any device like desktop, mobile and tablet. So that is the, you know, very simple definition of web or digital accessibility. So coming to the guidelines and standards, you know, every country will have its own laws and standards, you know, but internationally, there is a standard called WCAG, which is Web Content Accessibility Guidelines. And the W3C recent recommendation is that WCAG 2.1 Level AA, so which comprises of 50 success criteria. So whenever you have to make your application accessible, compliant with this standard, then you have to cross check all the 50 success criteria, which is nothing but some test procedures. So, you know, you will find some test procedures under each success criteria. So after DQ, we do recommend for WCAG 2.1 Level AA for all of our clients. And Level AAA is something, you know, it is little difficult to achieve and is the reason 2.1 Level AA is the reasonable accommodation that we recommend at DQ and also from W3C. All right. So let's get into the topic of today. All the free AX tools available from DQ. And so I would say that AX is really a trusted tool in the community. The reason I say is like there are multiple reasons why I say that. So for example, if you consider this number, what is the 58%, right? So usually, you know, our AX core library covers 30% of success criteria from whatever I just listed from WCAG, right? And but what is this 58% of them? So until last month, I worked as a product owner for one of the licensed products at DQ, which is called AX Auditor. It is actually available for commercial sale, but we also use the same tool internally to record our own audit findings for our own clients actually. So it is the data which sits on the server is like real data. So when I was working on this product, I pulled the data from 2017 January to 2020 April. That means three years, four months data to see how AX core is really helping in terms of coverage, right? I found that 58% of the issues are covered by AX core. That means 58% of the issues recorded in the tool are from AX automation. So this is the coverage that we observed recently. And then AX has 60 million plus downloads to be very precise. I heard yesterday that we had 63 million downloads. So, you know, it's just one tool with so many downloads. So that is the reason I say that AX is a trusted tool in the community and it is open sourced in 2015 and freely available. And it comes in two flavors. One is as an extension to the Chrome and Firefox browsers and then as an API as well. And then so I don't have too much time today in this session to demo all these things. So I'm just showing the screenshots. So as you see on the screen, whenever you go to the browser, Chrome or Firefox, open the web page, open the DevTools. And then you see if you install AX extension, you see AX on the DevTool bars and then you just see Analyze button. And once you click it, whatever is the web page on the browser, it will analyze it and show you the list of the issues on the left hand panel. And on the right side, you see the details of the issue with the inspect and highlight features available. More than that, it also gives you the link to DQ University where you can find very detailed information about each of these issues, like how it impacts, which disability gets impacted because of this and why you have to fix that, how you can test, how to remediate this, meaning how to fix this. So all of that information, valuable information is available in DQ University. So this is the extension part and this is free. But in the paid version, as you see on the screenshot, there is an AX export. So we recently, just to tell you how powerful it is, we recently rebranded all of our licensed products to prefix with AX name because of this leading indicator. So as you see, there is an AX export, which is part of our paid package that will have a lot of other commercializer features like export, import, custom rules, different standards, availability, and then page insights, which will help you with manual testing. And then you can test with no scope of a particular page area, not the entire page. So there will be a lot of features available there, reporting and all of that. All right, so moving to the free version of API, which is we call it as AX core API. So this you can integrate with any framework that can execute JavaScript. So for example, Selenium, Jasmine, Jenkins, Mocha, all these, any framework that can execute JavaScript can be integrated with this AX core API. It's just a simple JavaScript library. So as you add any other library, you just add it and you call the method to use it. And then in case of continuous integrations, you can make sure that AX clean before you proceed further with that builder. So again, as I said at the booth, we have Soma who can demo you with the Jenkins and Selenium, all of this. If you are interested, please have a discussion with him. So just for an idea, this is how we configure the AX driver. Actually, I use that test which is a previous name for AX DevTools. So but it is very similarly, you use AX driver as well. So basically to configure and use it, you will create web driver instance of Chrome and AX driver instance, and then configure it with the URL and then call the is accessible method. And you see the results like this in the editor. So that easy it is and it returns a JSON object and you can parse through and get the report. You can build the report as you want. But if you go with the paid package, all that reporting and everything is already available as part of the package itself. So AX Lenter is another recent tool that we added to this free suite of AX products. So which is a GitHub app actually. So it is available at AX-Lenter at dq.com. So what it does is whenever you raise a pull request, you see AX Lenter integration there. And it cross checks some of the area rules on the code that you submitted and it supports React, View, HTML and markdown languages. And this is how it looks actually. So it suggests the name and on top of your pull request, it suggests that what is wrong and how it can be corrected as well. So you can just commit the suggestion. For example, on the screenshot you are seeing article is misspelled and then tab index three is not the right thing to do. So it does that. And then on the whole actually on the pull request, you see the checks tab, right? Inside the checks tab, it will list out all the issues of the number of files it scanned, file, whatever the errors it has. And then the list of all the errors along with the file names. So this is a recent addition. And there is another product which is called AX Beta, which is free. And it is also called Intelligent Guided Tess. So the reason why we call it as Intelligent Guided Tess is, for example, if you take AX core library, right? So our automation team is constantly working on improving the coverage part and trying to make more things automated. But at the same time, we identified that there are certain accessibility rules wherein the system needs little user intervention. But if it can get that little help from the user, it can automatically raise the issues. It can automatically raise the issues. So that's the reason we invented this product and it is available. All you have to do is go to AX extension on Chrome browser. This particular tool works only on Chrome browser. So and then sign up there. And then now you can log in. You get the credentials to log into AX.dq.com. And one beautiful thing is like it doesn't require any of accessibility knowledge. And it guides you through basically a certain set of questions. And based on your answers, it raises the issues for you automatically. That's the beauty of this tool. So this is how the dashboard looks. For example, here I have this dashboard for qaweb.dqcloud.com where it is listing out how many issues are there that are found automatically and how many are found through guided tests. Like for example, 18 are from guided tests and 39 are from AX code. And one other thing that I wanted to mention is all of our including paid, you know, licensed versions of products use AX code as the underlying automation rolling gen. So the only difference will be the public version which is freely available will take certain time to get updated. Whereas the paid versions will have the latest and stable version always. That's the only difference. So as part of AX beta, this is how the manual, you know, guided tests will be. So these are the eight tools available as of today. For example, if you take lists, for example, right, you go to your webpage and you enable AX beta product, right, AX extension. And it will, you know, automatically identify what are all the lists available in that page. And then it shows you, okay, these are the lists I'm finding. And am I missing anything from the list that are supposed to be marked as lists? And then it says, are you finding any list in this list that should not be the list? So it asks some questions, intelligent questions. And then based on how you answer as a user, it automatically raises the issues. For example, let's go to the heading, right? So here on the left side, you're seeing the webpage. On the right side, you have the AX extension. So, you know, it highlighted automatically all the headings that it is finding. And as you see on the screen, it says we have highlighted 10 headings we could find on your website. Do you see any that shouldn't be a heading? So it is asking, like, okay, I see 10, but are these valid headings in your mind, right? And you say, yes, you know, some shouldn't be headings. Then it asks you which, you know, highlight the one which shouldn't be a heading based on the selector. You know, whenever you click something, it pulls the selector and then goes to the next question. And then it asks, like, okay, did I miss any heading that is supposed to be a heading, right? So like that, it asks the questions and based on how you answer, it raises the issues automatically. All right. So and then as I was telling with the same data volume of data for three years, four months, I had, you know, I went back and then, okay, I saw, okay, I come by an axe core automation rule engine that I have, and then axe beta, which is intelligent guided tools that is covering some manual, you know, coverage rate. Then my, my, my coverage is, you know, completely going to be the range in between the 76 to 84%. That's huge. So you might be wondering, how can that be possible, right? Because we observed, I observed that developers are doing certain, you know, repetitive mistakes under certain success criteria. For example, color contrast, for example, label association, unique ID, heading structures, heading hierarchies. So these are very common, you know, I found many number of issues, major, you know, range of issues in under these success criteria. I have top 10 list as well, if anyone is interested to know. So we found some patterns actually, where developers are really doing repetitive mistakes. That's the reason axe is really helping out to find majority of the issues. Okay. And then coming to the mobile, you know, space, axe for Android is free, which you can find in Play Store. You know, it's very simple, just go and find it in Google Play, and then install it. And then you see a setting called axe, as you see in the right side of my screen. And once you enable it, make it on, a purple guy will come on the screen. And, you know, that guy will follow you wherever you are on the phone. And then you can open any native application that you want to test for accessibility. And then once you click that, it runs the accessibility checks. And then, you know, at the bottom of the screen, you will see all the issues listed down because of the screen resolution. That is what the UI, the UI front we could do. But in case if you go for a paid version, we will give you very new, very nice desktop view, which will also, you know, which will be linked with the native application. And, you know, it comes with all the options like highlight options and all of that. And it will be easy to navigate through basically, right? So this is all I have for today. And then coming to the resources, I wanted to tell you that the DQ has come up with, you know, axe conference, which is a free and virtual conference that is going to happen in March 2021, 10th and 11th, I think. So we invite all of you to come and join us and share your accessibility journey, knowledge and, you know, lessons and learnings. We will be happy to host you all in March next year. And then DQ is also giving away a book on agile accessibility written by our chief product officer, Dylan Barrett. So this lists out the best practices that agile teams can follow to make and deliver, you know, to deliver accessible solutions in an agile way. And then I gave some important information that can help you, you know, especially axe dev tools that will help all the dev and QA people. And they, you know, the parts of the axe dev tools really help throughout your life cycle of the, you know, software development and your ROI will be much better if you start using these tools. So my only hope is that, you know, setting, you know, putting all the last and standards, compliance standards, you know, aside, I really request all of you if you have the influence to implement accessibility. As a human, you know, to give a better, you know, better digital world for our generations to come. Please, you know, use these at least free tools and make your products accessible and build a better digital world for everyone, including persons with disabilities. Thank you so much for listening to all of this. And if you, in case of any question, please, please feel free to reach me at Sugistri, S U J A S R E dot kura party K U R A P I K I at the Red DQ dot com. Thank you so much. Thanks Sugistri for sharing your experience with us today.