Full Axe Example Code

Pragati Sharma: We've understood all of this. The other thing is that how can we customize the user defects? Now, this is the project that we made, but I have a similar project already created, which is more exhaustive. It has more testcases. So I'll take you to that. So it has todo spec. So this is all that we did. So we tested the pageload, we did the accessibility violation check, but now there is another option wherein you can actually customize your accessibility test cases like in case you want to filter out using particular standards, like we talked about different tags so you can have certain tags specified here according to your product needs and product demands, and you can only find out those issues which are violating particular standards like these. Right? So in case you are in the United States Section 508 is very essential that. So then you can just find out what are all the violations around Section 508 by using this Run only command. Right? So this is a kind of custom parameterization that you can do for check accessibility function. Right. Similarly, in case you want to find out issues with specific impact areas now, in case you will prioritize that in this print, I'll just be picking up critical issues. Then we pick up severe and then moderate. So in case you want to go with that ideology, you can use the test cases in a similar fashion. And then as you go along doing your functional scenarios, you're opening another page, you're opening a frame, you're clicking on a button. After performing every functional scenario, you need to perform an accessibility on the top of it. Right. And this is what my test suit is doing. So let me just run this for you so that you understand this todo spec. And just focus on the right frame, what's happening here, because we are actually performing a lot of functional things as well. So what we're doing is we are adding certain items to the list and then we are striking them off after getting them completed. So, like you can see here we are doing accessibility check after performing every functional action, right after adding, we are again doing an accessibility check and then after checking out the item, we are again doing the accessibility check so as to see what all violations we are getting. And if you see here, it gives you a number of instances also. So there could be just one issue, but it could be on four different elements. Right. So now this takes your count to four plus three, which is seven plus one eight nine. So it has nine issues in total, all four different types. So that is how we actually figure out and categorize our different accessibility violations. 

Comments are closed.

{"email":"Email address invalid","url":"Website address invalid","required":"Required field missing"}