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

New Schools Today: Update alt text for New Schools Today image to adhere to WCAG #4046

Closed
1 of 4 tasks
Tracked by #3866
plang-psm opened this issue Feb 25, 2023 · 3 comments · Fixed by #4133
Closed
1 of 4 tasks
Tracked by #3866

New Schools Today: Update alt text for New Schools Today image to adhere to WCAG #4046

plang-psm opened this issue Feb 25, 2023 · 3 comments · Fixed by #4133
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 25, 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 New Schools Today 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/new-schools-today.md:

From:

Team of students each with a laptop sitting around the conference table, attentively engege in a video conference call meeting.

To:

New Schools Today

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 25, 2023
@plang-psm plang-psm added this to the w. Accessibility milestone Feb 25, 2023
@kimberlytanyh kimberlytanyh self-assigned this Mar 7, 2023
@github-actions
Copy link

github-actions bot commented Mar 7, 2023

Hi @kimberlytanyh, 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 :)

@kimberlytanyh
Copy link
Member

Availability: Tuesday, Wednesday, Friday (10:00AM-5:00PM)
ETA: Not too sure since I have never done this before. Maybe 5-8 hours to figure out how to do this? Hopefully with lesser time if I pick this up quickly!

@kimberlytanyh
Copy link
Member

Provide Update

  1. Progress: Finished completing action items in issue.
  2. Blockers: A few unexpected feedback from terminal when following instructions in Contributing.md. Had to re-do forking and cloning in case so am not sure if committing and pushing was done right.
  3. Availability: Same as above.
  4. ETA: Around 2-3 hours, excluding time watching YouTube tutorials and reviewing Contributing.md to better understand branching, committing, and pushing on GitHub.

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.

3 participants