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

[EPIC] Alt Text Improvements within Drupal #17443

Open
2 of 3 tasks
srancour opened this issue Mar 7, 2024 · 4 comments
Open
2 of 3 tasks

[EPIC] Alt Text Improvements within Drupal #17443

srancour opened this issue Mar 7, 2024 · 4 comments
Labels
accessibility Issues related to accessibility CMS design CMS Team CMS Product team that manages both editor exp and devops Epic Issue type Needs refining Issue status

Comments

@srancour
Copy link
Contributor

srancour commented Mar 7, 2024

Background

The VA 508 Office does an audit of alt text within VA.gov and CMS wants to explore how that is defined, so that we can reduce the amount of times that CMS content is flagged in the audit.

The previous CMS Agile 6 team did a lot of research on alt text that we can rely on when we are defining our improvements.

Problem Statement

As a drupal editor, I need to understand how to use the alt text field to input information that would be useful for a veteran viewing images through a screen reader.

How might we further improve the alt text validation 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 users are still not understanding how to use alt-text for images. By increasing their knowledge and improving the alt-text field we can improve the quality of the alt-text submitted.

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
  • Accelerated Publishing

Acceptance Criteria

  • A defined and measurable approach to improve alt text with Drupal CMS, using the alt text standards that are set at the VA 508 Office.

Tasks

Preview Give feedback
  1. CMS Team CMS design accessibility
    edmund-dunn srancour
  2. CMS Team
    srancour
  3. CMS Team Needs refining accessibility
@srancour srancour added Epic Issue type Needs refining Issue status CMS Team CMS Product team that manages both editor exp and devops accessibility Issues related to accessibility CMS design labels Mar 7, 2024
@srancour srancour changed the title Alt Text field upgrades [EPIC] Alt Text field upgrades Mar 7, 2024
@aklausmeier
Copy link

aklausmeier commented Apr 17, 2024

@srancour @MDomngz In Facilities recent VBA regional office editor research, related insights were uncovered.

  • Description and Alt text were confusing to user, he assumed they were the same thing
  • Alt text was very clear to him, more help text is needed for description to better understand alt text best practices

Historical context, when the alt text work was done last year (research and full ux flow), the description field was not addressed. Is this necessary?

Question to you both, do you feel the above insights can be addressed within the scope of this epic?

@srancour
Copy link
Contributor Author

@aklausmeier I actually chatted with @edmund-dunn about the description field for the images a couple weeks ago as I was digging into the alt-text work and thought that it probably confused editors with alt-text. We did come to the agreement that the description field is an unnecessary field, since the only place where that field is used is in the storage of the file, and we should look at getting rid of it.

I do think those insights can absolutely be addressed in this epic as it shows that editors are directly being confused about the alt-text field because the description field exists.

@aklausmeier
Copy link

the description field is an unnecessary field, since the only place where that field is used is in the storage of the file, and we should look at getting rid of it.

I would support this.

@michelle-dooley
Copy link
Collaborator

We will pick this back up after accessibility audit to see what we learn from that and how that may apply here.

@srancour srancour changed the title [EPIC] Alt Text field upgrades [EPIC] Alt Text upgrades within Drupal Aug 27, 2024
@gracekretschmer-metrostar gracekretschmer-metrostar changed the title [EPIC] Alt Text upgrades within Drupal [EPIC] Alt Text Improvements within Drupal Oct 1, 2024
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 Needs refining Issue status
Projects
None yet
Development

No branches or pull requests

3 participants