Hey @swirt!
Sorry I didn't get this uploaded on Sunday, but @adriancooke and I are meeting today to go over our drafts. Mine is included in the figma file. Today we'll share our drafts, pick what we like, remove what we don't like, merge the 2 drafts together, and hopefully have something for review by tomorrow or Friday.
Thanks!
@swirt -
Awesome - thank you! I wanted to make sure I wasn't just missing or assuming something! I'm hoping to have the mockup in the first draft form by Sunday night at the latest. I'll update here when I'm done! Thank you for your response and the clarification!
@swirt - I'm working on a mockup for the report now, but I noticed in the screenshot I captured in simplytest.me that the filter options don't include an "image title" and a "host entity" to filter by, but the table header of the report includes those two filters. Before I just assume, is that because you can't filter by image title or host entity? Or should I add those two filter options?
volkswagenchick → credited kesmith → .
@swirt - if I understand the cron setting correctly, each time I run the cron a new alt text report gets published, correct? And apologies if this is a silly question, but is there only one cron to rule them all? I know we used to force cron to run if our sites had updates that weren't appearing, but I don't know if there's like a whole-site cron, a report cron, an update cron, etc. I think this UI is ok as-is, but in the event that there's more than one cron (or you have an admin who is ignorant about cron like I am) maybe including why you would want this rebuild feature to be on or off and a suggested/best practice number of days?
@swirt @adriancooke I have a few thoughts around the language specifically, but also something else to suggest for the rules:
- For the individual rules - I don't see any way to edit or delete a rule (which just might not appear in the "rule building" part, so if that's the case, ignore this comment :) ) but for the "View rules" page we should have a way to edit or delete a rule.
- For the language: I wonder if we could say "Your page won't be saved" instead of "Page cannot be saved"? It's a bit friendly and avoids using passive voice.
- I love the "tell me what's wrong and how to fix it" language suggestion, @swirt, but I'm wondering if each rule having its own warning or prevent message will result in overload for the user reading through each one? For instance, if I have 7 images, none of which is decorative, and 5 of them get an error for 5 different rules, that's now 5 different pieces of feedback I have to read, understand, and fix. Don't get me wrong, I *love* "teach a man to fish" but I wonder if a more generic message suggestion for each might result in a better experience. I'm guessing most people, even with the option to write their messages, will stick with the proposed default message we're giving them, but I might be wrong!
- @adriancooke - this looks amazing! Should we include a tooltip or helper text with "Rule status" to explain what those different options mean? Or do you think users can infer the statuses from the "Customize alert" information?
One content suggestion - could we change the content to:
Choose how to handle errors if they occur when it runs:
Gracefully skip any errors and keep processing the remaining items
Fail on error and don’t process any remaining items