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

Accessibility: Change bold to strong in step 1 of getting-started.html #2430

Closed
2 tasks done
macho-catt opened this issue Nov 2, 2021 · 4 comments · Fixed by #2786
Closed
2 tasks done

Accessibility: Change bold to strong in step 1 of getting-started.html #2430

macho-catt opened this issue Nov 2, 2021 · 4 comments · Fixed by #2786
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: missing

Comments

@macho-catt
Copy link
Member

macho-catt commented Nov 2, 2021

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

To be WCAG compliant and ensure the same experience to all users, we want to change b tags to strong tags.

Action Items

  • Change the b tags to strong tags within pages/getting-started.html in line 51 only (step 1)
  • Line 51

From:

<p class="getting-started-step-title-header">STEP 1: <b>Attend an Onboarding Session</b></p>

To:

<p class="getting-started-step-title-header">STEP 1: <strong>Attend an Onboarding Session</strong></p>

Resources/Instructions

@macho-catt macho-catt 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 Prioritization labels Nov 2, 2021
@github-actions

This comment was marked as resolved.

@jjung99
Copy link

jjung99 commented Nov 2, 2021

Hi, I would like to work on this issue:)

@macho-catt
Copy link
Member Author

Hi @jjung99, to contribute to our repo, you do need to join the HackForLA organization first. Please check this website to learn more on how to join our team. Thanks!

@Sparky-code
Copy link
Member

Sparky-code commented Feb 16, 2022

Availability for this week: 4hr
ETA for this issue: 30min

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: missing
Projects
Development

Successfully merging a pull request may close this issue.

5 participants