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

Review alt text for WCAG compliance on Sitemap page #2617

Closed
12 of 14 tasks
IsaacDesigns opened this issue Dec 21, 2021 · 18 comments
Closed
12 of 14 tasks

Review alt text for WCAG compliance on Sitemap page #2617

IsaacDesigns opened this issue Dec 21, 2021 · 18 comments
Labels
Complexity: Small Take this type of issues after the successful merge of your second good first issue Feature: Accessibility Issues that would broaden website accessibility P-Feature: Sitemap https://www.hackforla.org/sitemap/ role: design size: 0.5pt Can be done in 3 hours or less

Comments

@IsaacDesigns
Copy link
Member

IsaacDesigns commented Dec 21, 2021

Overview

We need to ensure that alt text for images adhere to Web Content Accessibility Guidelines (WCAG). For this issue, we will tackle the images under the Sitemap page.

Details

Developers identified that some alt texts in the Sitemap page should be reviewed because they are either inaccurate or too long. Ideally, alt text should be descriptive but short and succinct. According to the WCAG page, an accompanying alt text should be short. Additionally, the Functional Accessibility Evaluator (FAE) recommends for alt text to be no more than 100 characters.

Action Items

  • Make a copy of the tab Template [Page Name]- [Status]
  • With the copied tab replace [Page Name] with the page you are reviewing and [Status] with "Audit in Progress". Don't forget to remove brackets "[ ]"
  • Add a link of the page your working on at the bottom in the Resources/Instructions section of this issue where it says "Google sheet Tab for your page".
  • For each image on the page, identify if the alt text needs to be changed or not using the recourses below and fill out the google sheet. To locate the alt text use the Google Chrome browser, right click "inspect" to view pages code.
  • After completing auditing each image change your google sheet tabs [Status] to Audit Complete.
  • Review with Design Lead or another member of the team
  • Mark spreadsheet tab as QA (e.g., About Page - Audit QA)
  • Add note at bottom of issue saying its ready for QA and use the close with comment, so that it goes to the QA column

Product

  • Review the work and sign off on it if ready
    • Mark spreadsheet tab as Complete (e.g., About Page - QA Complete)
    • Add Ready for dev leads label
    • Move to New Issue Approval Column

Development

  • Create issues for that particular alt text should be created (preferably labelled good first issue) for new developers to fix
  • Close this issue

Resources/Instructions

Sitemap page
WCAG section on alt text
FAE rule 4: alt text should be less than 100 characters
Google sheet instructions
Google sheet template
Google sheet Tab for your page

@IsaacDesigns IsaacDesigns added Feature: Accessibility Issues that would broaden website accessibility role: design Complexity: Small Take this type of issues after the successful merge of your second good first issue Ready for Prioritization labels Dec 21, 2021
@github-actions
Copy link

Hi @IsaacDesigns.

Good job adding the required labels for this issue. The merge team will review the issue and add a "Ready for Milestone" label once it is ready for prioritization.

Additional Resources:

@ExperimentsInHonesty ExperimentsInHonesty added this to the z. Accessibility milestone Dec 26, 2021
@ExperimentsInHonesty ExperimentsInHonesty added P-Feature: Sitemap https://www.hackforla.org/sitemap/ and removed Ready for Prioritization labels Dec 26, 2021
@IsaacDesigns IsaacDesigns added the size: 0.5pt Can be done in 3 hours or less label Jan 5, 2022
@gold-o gold-o self-assigned this Jun 22, 2022
@gold-o
Copy link
Member

gold-o commented Jun 26, 2022

The changes indicated in the spreadsheet are ready to be made into issues, and an additional issue must be created that an alt text version of the sitemap will need to be created to accommodate accessibility requirements.

@github-actions github-actions bot added the Status: Updated No blockers and update is ready for review label Jul 1, 2022
@phuonguvan
Copy link
Member

@gold-o Bonnie said that she discussed the alt text for the site map at Sunday's meeting. Was there a note about this?

@gold-o
Copy link
Member

gold-o commented Jul 7, 2022

@phuonguvan Yes, she mentioned that a solution for the site map alt text could be to have a text document laying out the content in the sitemap (using the same hierarchy). And then have a link below the site map that goes to the document. However, she mentioned that this will need to be a different issue. It is related to the comment I made above.

@github-actions github-actions bot added 2 weeks inactive An issue that has not been updated by an assignee for two weeks and removed Status: Updated No blockers and update is ready for review labels Jul 15, 2022
@github-actions

This comment was marked as outdated.

@github-actions

This comment was marked as outdated.

@github-actions

This comment was marked as outdated.

@github-actions

This comment was marked as outdated.

@github-actions

This comment was marked as outdated.

@github-actions

This comment was marked as outdated.

@github-actions

This comment was marked as outdated.

@github-actions

This comment was marked as outdated.

@github-actions

This comment was marked as outdated.

@github-actions

This comment was marked as outdated.

@github-actions

This comment was marked as outdated.

@github-actions

This comment was marked as outdated.

@ExperimentsInHonesty ExperimentsInHonesty added ready for dev lead Issues that tech leads or merge team members need to follow up on and removed 2 weeks inactive An issue that has not been updated by an assignee for two weeks ready for dev lead Issues that tech leads or merge team members need to follow up on labels Oct 5, 2022
@7kram 7kram removed the ready for dev lead Issues that tech leads or merge team members need to follow up on label Oct 5, 2022
@7kram
Copy link
Member

7kram commented Oct 16, 2022

QAed and ready for dev lead to make issues out of this.

@7kram 7kram added the ready for dev lead Issues that tech leads or merge team members need to follow up on label Oct 16, 2022
@ExperimentsInHonesty
Copy link
Member

@ExperimentsInHonesty ExperimentsInHonesty removed the ready for dev lead Issues that tech leads or merge team members need to follow up on label Mar 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complexity: Small Take this type of issues after the successful merge of your second good first issue Feature: Accessibility Issues that would broaden website accessibility P-Feature: Sitemap https://www.hackforla.org/sitemap/ role: design size: 0.5pt Can be done in 3 hours or less
Projects
Development

No branches or pull requests

5 participants