Potential A11y Violation:
Unequal non-text content descriptions
Point of Failure
Long descriptions for non-text content should serve the same purpose and present the same information (not more or less)
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. How would we programmatically be able to not only identify what should be compared but also compare the two and determine that they are the same?
If you have any thoughts on how to solve this problem, 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. How would we programmatically be able to not only identify what should be compared but also compare the two and determine that they are the same?
If you have any thoughts on how to solve this problem, 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 Could Exist
When adding long descriptions for non-text content, ensure that it presents the same information as is visible. Developers could even write a test that ensures the long description text is not changed.
Manual Test Must Exist
A manual test must exist. Observe if there is any non-text content on the page, and inspect the DOM for long descriptions. Ensure that they serve the same purpose and present the same information, not more or less.