Potential A11y Violation:
Multiple H1 elements
Point of Failure
Generally, best practice is to have one <h1> and only one <h1> element on the page. This allows users with screen readers to find their way around the page in a logical manner.
Available Automation Evaluation
In checking known available linting and testing tools, these are our findings.
Linting Cannot Exist
Since templates are generally composed together to make a complete "page", a linting check for this violation It does not seem possible to have an automated test for this potential failure, yet. If you an idea about how this could be linted in an automated fashion, or are aware of an automated linting rule that already exists, please file an issue on this app's GitHub Repository.
Testing Could Exist
It's possible that a linting rule could be created for this potential failure.
Other Test Methods
In addition to automated tests, there are other types of tests that could be conducted to prevent this potential violation.
Developer Authored Test Could Exist
Developers should make sure that their code does not violate this rule, and try to write a test that would prevent a regression in accessibility if the code is later changed.
Manual Test Must Exist
Review page and ensure the point of failure does not exist, inspecting the DOM where required.