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

Guides Team: Update alt text for Guides Team image to adhere to WCAG #4006

Closed
2 of 4 tasks
Tracked by #3866
plang-psm opened this issue Feb 19, 2023 · 3 comments · Fixed by #4048
Closed
2 of 4 tasks
Tracked by #3866

Guides Team: Update alt text for Guides Team image to adhere to WCAG #4006

plang-psm opened this issue Feb 19, 2023 · 3 comments · Fixed by #4048
Assignees
Labels
Feature: Accessibility Issues that would broaden website accessibility good first issue Good for newcomers role: back end/devOps Tasks for back-end developers role: front end Tasks for front end developers size: 1pt Can be done in 4-6 hours

Comments

@plang-psm
Copy link
Member

plang-psm commented Feb 19, 2023

Prerequisite

  1. Be a member of Hack for LA. (There are no fees to join.) If you have not joined yet, please follow the steps on our Getting Started page.
  2. Please make sure you have read our Hack for LA Contributing Guide before you claim/start working on an issue.

Overview

As a developer, we need to provide clear and descriptive alt text on the Guides Team page so that we adhere to the Web Content Accessibility Guidelines (WCAG) and we can achieve our mission of inclusivity.

Action Items

  • Change the image alt property value within _projects/guides-team.md:

From:

Globe Map made of dots and hackforla logo and text reading Guides Team

To:

Guides Team

For PM, Merge Team, or Tech Lead

Resources/Instructions

File and Code links you will need to work on this issue

Background information about the Jekyll framework (optional reading)

Information about WCAG and alt text (optional reading)

@plang-psm plang-psm added good first issue Good for newcomers role: front end Tasks for front end developers role: back end/devOps Tasks for back-end developers Feature: Accessibility Issues that would broaden website accessibility ready for dev lead Issues that tech leads or merge team members need to follow up on size: 1pt Can be done in 4-6 hours Ready for Prioritization and removed ready for dev lead Issues that tech leads or merge team members need to follow up on labels Feb 19, 2023
@github-actions github-actions bot added ready for dev lead Issues that tech leads or merge team members need to follow up on and removed Ready for Prioritization labels Feb 19, 2023
@plang-psm plang-psm added this to the w. Accessibility milestone Feb 19, 2023
@plang-psm plang-psm added Ready for Prioritization and removed ready for dev lead Issues that tech leads or merge team members need to follow up on labels Feb 19, 2023
@annierm18 annierm18 self-assigned this Feb 22, 2023
@github-actions
Copy link

Hi @annierm18, thank you for taking up this issue! Hfla appreciates you :)

Do let fellow developers know about your:-
i. Availability: (When are you available to work on the issue/answer questions other programmers might have about your issue?)
ii. ETA: (When do you expect this issue to be completed?)

You're awesome!

P.S. - You may not take up another issue until this issue gets merged (or closed). Thanks again :)

@github-actions github-actions bot added the To Update ! No update has been provided label Feb 24, 2023
@github-actions
Copy link

@annierm18

Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the developer meeting discussion column and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel.

You are receiving this comment because your last comment was before Monday, February 20, 2023 at 11:17 PM PST.

@annierm18
Copy link
Member

Availability: 2/25 & 2/26
ETA: 2/26

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature: Accessibility Issues that would broaden website accessibility good first issue Good for newcomers role: back end/devOps Tasks for back-end developers role: front end Tasks for front end developers size: 1pt Can be done in 4-6 hours
Projects
Development

Successfully merging a pull request may close this issue.

4 participants