Add h tags to Getting Started page (Steps 4-5)

[SAUMILDHANKAR]

Overview

As a developer, I need to replace p tags with h tags on the headings of Getting Started page (Steps 4-5) so it becomes WCAG compliant

Action Items

• Review Getting Started html file
• In line 166, change the p tag to an appropriate h tag:

  website/pages/getting-started.html

  Line 166 in 96f02c4

  <p class="getting-started-step-title-header">STEP 4: <strong>Choose a Role</strong></p>

• In line 201, change the p tag to an appropriate h tag:
  

  website/pages/getting-started.html

  Line 201 in 96f02c4

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

• Ensure h tags (h1, h2, h3 etc.) reflect the correct hierarchy of the page for screen readers
• Make sure the Getting started page still looks the same.

Resources/Instructions

• Getting Started page
• Getting Started html file
• Headings in Page Structure Tutorial
• WCAG guidelines
• Related issue Add h tags to Getting Started page (Steps 1-3) #2952

[arpitapandya]

Availability for this week: 6hrs
My estimated ETA for completing this issue: 1.5hr

[arpitapandya]

• Time spent: 6hrs to complete
• Availability: 6hrs for next week
• Blockers: None for this issue

[arpitapandya]

@JessicaLucindaCheng

• Found a bug which can be a separate new issue to work on(or it's already in issues list) in Getting Started html,
• At present Step 3 and Step 4 in Getting Started page isn't pointing to correct card.
• changes required for the link Step 3 and Step 4
• move line 27 and 28 to line 33 and 34
• move line 33 and 34 to line 27 and 28
  

[JessicaLucindaCheng]

@arpitapandya
Thanks for bringing this up! It's already in the [issues spreadsheet] (https://docs.google.com/spreadsheets/d/1qEiDFUKPCVH3JNzGQSKl_HMl9vqNv8Z9gGrvw9MyYvU/edit#gid=772902542) as row #19. It actually should be the larger, detailed cards 3 and 4 should be switched so it matches the header order as per the Figma design.

Also, please leave your issue in the In Progress column. When your pull request is merged, there is automation that will close and move your issue to another column. I am going to go ahead and move this issue back to In Progress.