Closed (fixed)
Project:
Alt Text Validation
Version:
1.0.x-dev
Component:
Code
Priority:
Major
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
7 Jul 2025 at 02:01 UTC
Updated:
6 Aug 2025 at 16:00 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
swirtThere were a few items where I deviated from the design#
Comment #3
swirtComment #4
swirtComment #6
swirtTo test
Comment #7
kesmith commentedHi @swirt!
I looked at this today, and I have just a few updates:
- When adding a rule > Rule status > can we change Warn to "Warn allows users to save but displays a warning encouraging them to edit their alt text"? You matched it to what we had in the designs, but in the designs, we had "prevent" listed first so it was clear who the "them" was to start.
- I also noticed that the image doesn't appear in the report if it has a warn and prevent rule applied to it:
So like 'Image of ... ' that's over 100 characters. Because I set the rules to prevent if the alt text contains "image of" it doesn't technically save the image. So I get why it doesn't appear in the report, but just a scenario I hadn't thought about when we were doing the designs - so I'm not sure if it needs to be addressed or not.
I like the changes you made and they make sense! The rest looks good!
Comment #9
swirt@kesmith. Thank you.
I adjusted the warn text to your suggestion. That was a great catch.
Yah if the save never happens it can't show in the report because the report only shows what is actually saved. There is not really a way around that. I also don't think it will be a common use case where people will be avidly watching the report while they are making attempted saves. In most cases I think editors will be handling the saves, and someone else will be utilizing the report. But it can lead to some head scratching moments when trying to test the module like we are doing in development.
Comment #10
swirtReleased with 1.0.0-alpha7