🇺🇸United States @adriancooke

Account created on 13 January 2022, about 3 years ago
#

Recent comments

🇺🇸United States adriancooke

@arijit acharya thanks for the mockups and thought process you shared. It was very helpful to get my head around what we’re doing here. I had a chance to discuss with @kesmith and @swirt, get some feedback, and came up with some ideas to consider:

Reworking of admin UI fields:

  • Enable/disable all alt text validation (off switch preserves config)
  • Customize alert headings
    • Warn heading text (e.g. “Alt text errors found on page.”)
    • Prevent heading text (e.g. “Alt text errors found. Page cannot be saved.”)
  • Individual rule configuration:
    • Rule type
      • Alt cannot match image filename
      • Alt cannot match image title
      • Alt cannot exceed length (Max characters)
      • Alt cannot begin with, contain, end with (text, regex)
      • Alt cannot be empty unless decorative (how do we check for this?)
    • Rule status
      • Off, Warn, Prevent
    • Rule message (HTML)
    • Rule scope? (not MVP)
      • Global
      • Out out specific field?
      • Out out content type?

Alert the author sees:

Suggested pattern for message fields: “what happened” followed by “what’s wrong and where,” then “how to fix” and“how to get help”. For example (where the bolded text may be a heading):

Alt text errors found. Page cannot be saved.
The alt text in the {filename} image contains the filename. Please replace the filename with a description of the image. Get help with alt text →

The idea is that there would be default text but it can all be customized and we can provide authors with a link to get more information.

Production build 0.71.5 2024