Posted on

[Video Guide] How to Dismiss Results

For a transcript synchronized with the video, watch the Q&A: How to Dismiss Results with transcripts open on Youtube.


Welcome to another Q&A; session with [Pope Tech]. We recently had a user ask, “How do we dismiss results?” So as many of you know, [Pope Tech] platform takes the WAVE engine and scans sitewide. So instead of doing one page at a time, you’re able to get your whole site in the platform. As Errors, Alerts, and Contrast are the three WAVE categories that directly test for accessibility failures, they are the three categories where items can be dismissed in the [Pope Tech] Platform.

If results are dismissed, the node of code that has been dismissed will not be included in future scans. Additionally, the count will drop down based upon the number of results that are dismissed. Dismissing code can happen by drilling down in any of the tests on the Results Type; or by Most Common Issues—drilling down into that—or by the Scan Details [drilling down] into one website.

For this QA, I’m just going to select the Alerts button in the Results Type and activate that. And so, I’ve activated the Results Type for the Alerts. It’s now showing all the Alerts happening on all these websites in the account. The first Alert is Redundant Link. I’m just going to activate that one. So we move into it. As I’ve shown in previous videos, we include the same documentation in the [Pope Tech] platform that you have in the WAVE tool.

I activated the link there for Redundant Links documentation on How to Fix It. And so, it brings open the tray that describes how to fix it; why it matters; and links to more documentation out of WebAIM’s site. And so you’re able to review that. Alright, we’ve got redundant links and we have a list of the different websites with redundant links on there and their counts and how many pages they’re on.

Let’s just select the blog at I’m able to see a list of all of the pages on the Dinolytic blog that have Redundant Links. As you are probably familiar you’re able to pop it [the code tray] open and see the line of code, where all the redundant links are and explore them; as well as kicking out to the WAVE tool. So if you kick out to the WAVE tool you’re also able to select— we’re looking at Alerts—Redundant links. And we’re able to see where the redundant links are occurring as well as the line of code for them.

If we’ve determined that the redundant link is not an accessibility issue and would like to dismiss it, You can dismiss it by returning back to the platform, identifying the page that it’s on, and selecting the Dismiss button. This opens up a line of code tray, similar to what we’ve seen before with the difference being that there is now a Dismiss Button next to each line of code. And so, you can select one of these items here, if this is the one I want to dismiss and provide a reason for dismissal.

We encourage that the admins and account owners only assign users who understand enough about accessibility to know when it is appropriate to dismiss a result. Because once a result is dismissed, it will no longer show up in the count for that website. Let me just cancel out here for a second…We’ve got 12 redundant links on this page right here. If I were to dismiss this first result here, and we’ll just call this “test for video,” But again, I would provide probably a more descriptive reason why, after investigating this link, to make sure it was a proper dismissal. I’m going to dismiss that right now.

And then when the page is refreshed; Now, on that page that’s got our Redundant Links: we’ve got our Blogs [Websites]. So before we had two of them that had that 12 count. Just to confirm that we got the “Page 2 Guides,” “Page two” here and we’re going to dismiss this one for the test as well. Alright.

And now we have none of them listing 12 there. So you can see it drop the count there. Additionally, in the dashboard, the dashboard, the overall count on the Alerts have also dropped now from 474 to 472. So the results is dismissed. All the dismissed results are archived. And you’re able to view them by activating the accessibility button. Under that is the button Dismissed Results. And it’s going to show a list of all the results that were dismissed. These two are just dismissed by user—that’s the login that I have right here—Redundant links, and it shows which pages they’re dismissed on. I’m able to then activate the Details button;
see what was dismissed; see the node of code that was dismissed; what page it was; and who dismissed it; and the reason that they gave.

If I wanted to update that status I could select the button and say, “put it back active as it was just a demo.” So I’m able to put that back in the test. And now we’ve “Undismissed it.” So you’re able to Scan it again for that one. Again. I can do the same thing on the other dismissal. It’s gonna load it here. We’ve got this other dismissal right here that we’ve put in there. And if you noticed. If I hit delete instead of update status, if I activate the delete button, it’s going to remove the dismissal.

So now, it will be active in the next scan. But then it’s no longer going to retain the archive of the results in the Dismissed Results. And so Delete deletes both the dismissal and the archive in the log. Now those nodes of code, when it’s being scanned again, will be tested again. Notice here [in the dashboard count], it does not immediately put it back in the dashboard this time. But on the next scan, it will test for that node of code. As mentioned at the start of the video, you can dismiss nodes of code by drilling down from Results Type; Most common issues; or by Scan Details.

The process of drilling down by Most Common Issues is identical to what we just observed by Results Type. As we drill down in Alerts, I could activate the Alerts button in Most Common Issues and then select Redundant Links and proceed from there. Again, the process is identical, after that point forward, to what we just demonstrated by drilling down into Results Type. As the flow is slightly different from Scan Details, I’m going to demonstrate how that works. The Scan Details you select the website you want to drill down into.

In this instance, we are again going to select the [Pope Tech] blog—So the I’m going to activate the Details button to drill down into that. It does provide a summary in the dashboard. As we’re just drilling down into results, we’ll just look at the pages. So now, we can choose from all the different pages that we want to look at. I’m just gonna take the first one, the August 2018 [Pope Tech] blog. It has 0 errors; 12 alerts; 0 contrast.

I’m gonna select the Details button for that one and take a look at those alerts. By activating the details button, there it pops open a page view of that August 2018 [Pope Tech] Blog [page]. It does have the same 6 categories that we’ve seen before for the WAVE engine. By default. It shows all.

Again, we were looking at redundant links here [as] previously in this tutorial. So the first item is Redundant Links. There are 11 of them on this page I can pop up in the tray for node of code.

I can kick out to the WAVE tool and load that for the page. And, again explore the Redundant Links that way. And now I’m moving back into the Dashboard. Once again, after exploring the code—either by looking at the code tray within the platform or kicking out to the WAVE tool—If I determine that there are Redundant Links that need to be dismissed, I can activate the Dismiss button for the redundant links. Which again will pop open the Dismiss [Results] tray, which is similar to the Line of Code tray. And choose which line of code I want to dismiss—which redundant link—and activate the Dismiss button for that particular item. This will once again pop up in the Dismiss Result tray. And I can provide the reason and dismiss it, as I already demonstrated. Alright, that is the flow, drilling down from the dashboard into the Scan Details for Dismiss[ing] code.

Hopefully, this was useful in helping you understand how dismissed results work for in [Pope Tech] platform.

Once again, we love hearing your feedback and questions that different [Pope Tech] users have. If you ever have any questions feel free to just submit a inquiry in the [Pope Tech] platform or give us some feedback. Thanks for joining us on this video. Looking forward to chatting with you and having you on our platform.