Potential A11y Violation:
Keyboard trap due to multiple content formats
Point of Failure
When multiple content formats are used, the user must not become trapped in any of the content.
Available Automation Evaluation
In checking known available linting and testing tools, these are our findings.
Linting Cannot Exist
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 Cannot Exist
It does not seem possible to have an automated test for this potential failure, yet. If you an idea about how this could be tested in an automated fashion, or are aware of an automated test that already exists, please file an issue on this app's GitHub Repository.
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 Should Exist
Developers should avoid using multiple content formats- it increases the chance that something will go terribly wrong and will take weeks to debug. But if developers choose to engage in risky behavior, they should ensure that their code does not violate this rule, and write a test that prevents regressions in code if it is later changed.
Manual Test Must Exist
Review page and ensure the point of failure does not exist, inspecting the DOM where required.