Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Alt Text Field Prototype #13103

Closed
3 of 13 tasks
laflannery opened this issue Mar 29, 2023 · 3 comments
Closed
3 of 13 tasks

Alt Text Field Prototype #13103

laflannery opened this issue Mar 29, 2023 · 3 comments
Labels
accessibility Issues related to accessibility CMS design CMS Team CMS Product team that manages both editor exp and devops Epic Issue type Research CMS team practice area

Comments

@laflannery
Copy link
Contributor

Background

Problem Statement

How might we improve the image upload editorial interface to allow editors to add better, more useful alt text for the images they are uploading?

Affected users and stakeholders

  • CMS editors of all products

Hypothesis

We believe that by updating the editorial interface and focusing on 3 key areas, we will be able to increase the quality of the alt text for uploaded images. We'll know that to be true when we run the report of alt text metrics and compare statistics against previous statistics.

We will be focusing on:

  • use of filename
  • use of redundant phrases (i.e. "image of", "photo of", etc.)
  • length of alt text

Assumptions

  • We assume that the use of filename in the alt text field will be reduce to 0%
  • We assume 85% of images upload will not use redundant phrases
  • We assume that 90% of images uploaded will have succinct alt text

Design principles

Veteran-centered

  • Single source of truth: Increase reliability and consistency of content on VA.gov by providing a single source of truth.
  • Accessible, plain language: Provide guardrails and guidelines to ensure content quality.
  • Purposely structured content: Ensure Content API can deliver content whose meaning matches its structure.
  • Content lifecycle governance: Produce tools, processes and policies to maintain content quality throughout its lifecycle.

Editor-centered

  • Purpose-driven: Create an opportunity to involve the editor community in VA’s mission and content strategy goals.
  • Efficient: Remove distractions and create clear, straightforward paths to get the job done.
  • Approachable: Offer friendly guidance over authoritative instruction.
  • Consistent: Reduce user’s mental load by allowing them to fall back on pattern recognition to complete tasks.
  • Empowering: Provide clear information to help editors make decisions about their work.

Team

Please check the team(s) that will do this work.

  • CMS Team
  • Public Websites
  • Facilities
  • User support
@laflannery laflannery added Epic Issue type Needs refining Issue status and removed Needs refining Issue status labels Mar 29, 2023
@github-actions github-actions bot added the CMS Team CMS Product team that manages both editor exp and devops label Mar 29, 2023
@laflannery laflannery added the accessibility Issues related to accessibility label Mar 29, 2023
@productmike productmike changed the title Improvements for image alt text field SUPER EPIC: Alt Text Field Improvements Apr 20, 2023
@productmike productmike changed the title SUPER EPIC: Alt Text Field Improvements SUPER EPIC: Alt Text Field Prototype Apr 21, 2023
@productmike productmike changed the title SUPER EPIC: Alt Text Field Prototype Alt Text Field Prototype Apr 21, 2023
@productmike productmike added CMS design Research CMS team practice area labels Jul 24, 2023
@laflannery
Copy link
Contributor Author

I don't know where to put this so it's going here. In the very far future, if we decide to allow decorative images, this could help a lot as a resource for editors: https://www.w3.org/WAI/tutorials/images/decision-tree/

@laflannery
Copy link
Contributor Author

@maortiz-27-80 I think it makes sense that we close this epic since all the tasks are done and we moved onto the next epic. Does that make sense? CC: @BerniXiongA6

@maortiz-27-80
Copy link

Yes, and thanks, @laflannery ! Closing this EPIC in favor of Epic 15785. cc: @BerniXiongA6

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accessibility Issues related to accessibility CMS design CMS Team CMS Product team that manages both editor exp and devops Epic Issue type Research CMS team practice area
Projects
None yet
Development

No branches or pull requests

3 participants