Usefulness review of Alt text report

Note: The entity id link on the ids will take you to the entity where the image is referenced.

Missing or inaccurate alt text is one of the most common accessibility errors (https://webaim.org/projects/million/#errors). While many accessibility testing tools can identify instances of missing alt text (WAVE, axe-core, etc), they cannot determine when alt text meets conformance requirements to describe an image's purpose in context — only a person can do that accurately. This tool will be incredibly helpful in identifying and aggregating images and their alt text values for review and revision.

Having a report like this that is able to centralize bad accessibility is useful. You'll be able to sort by date which is useful. There may be other ways to organize the information as well in that table.

I would love to see these errors show up on the admin pages where the images are used too.

@mgifford I am not sure what to surface for date. I struggle with including it because it may largely misrepresent what it is.

• Created date - Using the created date would indicate when the node, term or media entity was created, but the image in its current state might not have been there. So in terms of error, the created date would err only on the side of representing a date that was too early.
• Updated date - would indicate when the entity was last updated, but that does not mean when the image field was last updated. Using the updated date would err on the side of being too recent a date.
• revision where the image first appeared - This would tell when it was added, but would never change. The revision processing that is required to determine when an image first appeared would be intensive and likely cause the refresh of this report to take too long to process.
• revision where the image last changed - This is perhaps the most useful information, but would be the most intensive to search the revision histories. for each entity.

Here is the updated look with the addition of the list of violations as well as the accompanying filter.

This is what the report currently looks like pulling from the actual image fields and text fields.

→

I am going to call this review done. We can create new Feature Requests going forward if there are changes needed for the report.