Scan fails when a page does not have a body tag
See original GitHub issueDescribe the bug
Scan fails when a page does not have a body tag
To Reproduce
- Create a page with the following html:
<!DOCTYPE html>
<html>
<head>
<title>Page Title</title>
</head>
<h1>Hello world</h1>
</html>
- Open AI-web
- Run automated checks
- See error in the console
Expected behavior
The scan should be able to run.
Extension (please complete the following information)
- OS: any
- Version any
- Browser Version any
- Target Page N/A
Issue Analytics
- State:
- Created 4 years ago
- Comments:14 (6 by maintainers)
Top Results From Across the Web
Scan page and find missing header tags - Stack Overflow
To check for skipped heading levels you need to iterate through the headings on a page and check that they either:.
Read more >Error message when adding sites into Security Scan
User is not able to add sites into the Commerce Security Scan. ... and make sure the validation code appears in the home...
Read more >Common security scan detected issues and how to address ...
This article provides information for Common security scan vulnerabilities which mostly may be detected as false positives during automated ...
Read more >Common problems found by Web Audit
End tag for "body" seen, but there were unclosed elements. Most likely missing a closing div tag. Fieldset does not contain a legend...
Read more >Heading off confusion: When do headings fail WCAG? - TPGi
Non-descriptive headings Of course, determining whether heading text is sufficiently “descriptive” is subjective and context dependent. ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@ferBonnin, I already clarified in the reopening comment: this is our issue, axe-core and axe’s web extension both work fine on all repro variants.
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!