Emit a warning if the base URL leads to an empty page about accessibility-insights-action HOT 6 CLOSED

This issue has been marked as ready for team triage; we will triage it in our weekly review and update the issue. Thank you for contributing to Accessibility Insights!

from accessibility-insights-action.

PM to determine next steps for UI changes

from accessibility-insights-action.

This issue requires additional investigation by the Accessibility Insights team. When the issue is ready to be triaged again, we will update the issue with the investigation result and add "status: ready for triage". Thank you for contributing to Accessibility Insights!

from accessibility-insights-action.

We will bundle this into feature work: ADO-Improvements -1

from accessibility-insights-action.

I'm not certain we want to pursue this. If the webserver returns a success code the page is scanned. The scanner package does check the status codes and throws if the page doesn't exist. In the case of the user mentioned above, I assume the webserver was serving a page it just happened to be empty? That seems like an edge case that on its own is probably good for the end-user to fix.

The accessibility-insights-scan package doesn't currently have infrastructure for detecting a blank page. If the base URL or a linked page is served successfully with a 200 status code but is blank it will return two failure instances from axe-core:

2 failure instances
* (1) document-title:  Ensures each HTML document contains a non-empty <title> element
* (1) html-has-lang:  Ensures every HTML document has a lang attribute

There is also no way of doing this without modifying the service repo to handle this case. If we were to pursue this further, we would likely want to make it optional with a flag that can be passed into the crawler. We would also have to figure out how to structure the output properly to handle this scenario, as the crawler is expected to return axe results.

This is the last open issue on the ADO-improvements-1 feature. I talked to Rob and he said he was okay with either closing this issue as-is if everyone agrees. Otherwise we'll want to discuss it further and the plan will be to push it to a later feature.

from accessibility-insights-action.

Closed after discussion with the managers.

from accessibility-insights-action.