-
Notifications
You must be signed in to change notification settings - Fork 17
Change page.goto to wait for DOM content to load #97
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
This PR addresses an issue where axe accessibility violations were being detected while pages were still loading, potentially resulting in incorrect violation reports. The change adds an explicit wait condition to the page navigation in the accessibility scanning function.
Key Changes:
- Modified
page.goto()to wait for DOM content to be loaded before proceeding with accessibility scanning
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Increased the timeout for page navigation to 20 seconds.
Log raw findings from AxeBuilder analysis for debugging.
Added logging for page content retrieval.
|
based on this conversation, the issue was accessibility-bot permissions. Closing |
|
temporarily reopening to test something. will close after |
Fix an issue where axe violations are found while the page is still potentially loading (so the flagged violation is potentially incorrect)