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.

Sign up for GitHub

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

Jump to bottom

Accessibility: Change bold to strong in step 5 of getting-started.html #2429

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

Accessibility: Change bold to strong in step 5 of getting-started.html #2429

macho-catt opened this issue Nov 2, 2021 · 2 comments · Fixed by #2787
Assignees
@answebdev
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
Milestone
w. Accessibility

Comments

@macho-catt
Copy link
Member

macho-catt commented Nov 2, 2021 •
edited by answebdev
Loading

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 tag to strong tag within pages/getting-started.html in line 201 only (step 5)
  • Line 201

From:

<p class="getting-started-step-title-header">STEP 5: <b>Join a Project</b></p>

To:

<p class="getting-started-step-title-header">STEP 5: <strong>Join a Project</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
Copy link

github-actions bot commented Nov 2, 2021

Hi @macho-catt.

Good job adding the required labels to this issue.

Additional Resources:
Wiki: How to add status labels to issues (WIP. Link will be updated when the wiki is done)
Wiki: How to create issues (WIP. Link will be updated when the wiki is done)

@Hallecsy Hallecsy mentioned this issue Nov 2, 2021
Closed
@ExperimentsInHonesty ExperimentsInHonesty added this to the z. Accessibility milestone Nov 4, 2021
@answebdev answebdev assigned answebdev and unassigned answebdev Feb 16, 2022
@answebdev answebdev self-assigned this Feb 17, 2022
@answebdev
Copy link
Member

answebdev commented Feb 17, 2022 •
edited
Loading

  1. Progress: Finished, submitted pull request
  2. Blockers: None
  3. Availability: 3 hours
  4. ETA: 2/16/2022 (end of day)

@answebdev answebdev mentioned this issue Feb 17, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@answebdev answebdev

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
P: HfLA Website: Project Board
Archived in project
Milestone
w. Accessibility
Development

Successfully merging a pull request may close this issue.

Change bold to strong in step 5 answebdev/website
4 participants
@answebdev @ExperimentsInHonesty @macho-catt @Josiah-O