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

SiteMap Page: Update alt text for Suggested Site Icon image to adhere to WCAG #6799

Closed
5 of 6 tasks
Tracked by #3859
Maarimar opened this issue May 1, 2024 · 3 comments · Fixed by #6894
Closed
5 of 6 tasks
Tracked by #3859

SiteMap Page: Update alt text for Suggested Site Icon image to adhere to WCAG #6799

Maarimar opened this issue May 1, 2024 · 3 comments · Fixed by #6894
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

@Maarimar
Copy link
Member

Maarimar commented May 1, 2024

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 SiteMap page 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: pages/sitemap.html

From:

 <img src="/assets/images/sitemap/lightbulb.svg"> 

To:

 <img src="/assets/images/sitemap/lightbulb.svg" alt=""> 
  • Ensure that the corresponding SiteMap page stays the same after the change
  • Using developer tools to inspect the image, ensure that the new alt text gets incorporated after the change.
    • Note: alt="" in code while show up as alt when using developer tools to inspect the image's alt text property.

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)

@Maarimar Maarimar 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 Complexity: Missing labels May 1, 2024
@ExperimentsInHonesty ExperimentsInHonesty added this to the w. Accessibility milestone May 6, 2024
@ExperimentsInHonesty ExperimentsInHonesty added ready for merge team needs a senior review either to do some re writing or to approve it for ready for prioritization and removed ready for dev lead Issues that tech leads or merge team members need to follow up on labels May 6, 2024
@jphamtv jphamtv added Ready for Prioritization and removed ready for merge team needs a senior review either to do some re writing or to approve it for ready for prioritization labels May 10, 2024
@deepak-getpu deepak-getpu self-assigned this May 23, 2024
Copy link

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

@deepak-getpu deepak-getpu removed their assignment May 23, 2024
@ino-iosdev ino-iosdev self-assigned this May 24, 2024
Copy link

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

@ino-iosdev
Copy link
Member

i. Pretty available recently
ii. ETA: 2-3 days

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
Development

Successfully merging a pull request may close this issue.

5 participants