-
Notifications
You must be signed in to change notification settings - Fork 776
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
feat: rule aria-hidden-focus #1166
Conversation
On hold, until issue #1208 is resolved. |
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.
I'm so excited for this rule!!!
test/integration/rules/aria-hidden-focus/aria-hidden-focus.html
Outdated
Show resolved
Hide resolved
Performance analysis
|
@dylanb @WilcoFiers updated with perf measurements. |
See if you can get this to 500ms for the large page. |
@JKODU I think the performance impact on large pages is significant enough that its worth refactoring to try to achieve performance improvements. I would like to see what the theoretical minimum would be (if we used all native code for selecting, did one pass only for the entire rule instead of two and did the filtering at the front instead of the back. One more question, how did you measure those performance numbers? |
The numbers reported above are an average of 3 run's for each page, that was measured/ reported on the console for each of those pages. |
@dylanb - Sure, I will attempt some refactoring as suggested. |
For BIG PAGE https://www.tensorflow.org/api_docs/python/tf/InteractiveSession with I have cached Also, had to update certain tests involving Performance analysis (after caching results)
|
Rule: Aria Hidden Focus.
Spec for rule - Spec: auto-wcag.github.io/auto-wcag/rules/SC4-1-2-aria-hidden-focus.html
Closes issue:
Reviewer checks
Required fields, to be filled out by PR reviewer(s)