Change alt text for card image in lucky parking md file

[SAUMILDHANKAR]

Overview

We need to ensure that alt text for images adhere to Web Content Accessibility Guidelines (WCAG). For this issue, we will change the alt text for the lucky parking project card image on citizen engagement page.

Details

Designers and PMs identified that some alt texts in the Citizen Engagement page should be changed because they are either inaccurate or too long. Ideally, alt text should be descriptive but short and succinct. According to the WCAG page, an accompanying alt text should be short. Additionally, the Functional Accessibility Evaluator (FAE) recommends for alt text to be no more than 100 characters.

Action Items

• For the file _projects/lucky-parking.md, change line 60 for the alt text:

from

card-image-alt: lucky parking project card

to

card-image-alt: 

• For merge team: Once the pull request associated with this issue is approved and merged, please update and edit epic Change alt texts for images on citizen engagement page #3089 by
  • Checking off the dependency for this issue
  • If all dependencies are checked off, please move issue Change alt texts for images on citizen engagement page #3089 to the New Issue Approval column and remove the Dependency label

Resources/Instructions

• This issue is part of epic Change alt texts for images on citizen engagement page #3089
• Citizen Engagement page
• Alt text decision Tree
• FAE rule 4: alt text should be less than 100 characters

File and code links you will need to work on this issue

• Directory to find the page once you have it in your IDE: _projects/lucky-parking.md
• Click on the link below to see the source file code:
  

  website/_projects/lucky-parking.md

  Line 60 in f2ce898

  card-image-alt: lucky parking project card

Information about WCAG

• WCAG
• Web Accessibility Tutorials: Decorative Images
• WCAG section on alt text

[github-actions]

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

[tunglinn]

Availability: Monday-Thursday 6 hours/day
ETA: 6/28/2022

[tunglinn]

Progress Update

1. Progress: completed changes
2. Blockers: waiting for PR reviews
3. Availability: Monday-Thursday 6hrs/day
4. ETA: 6/27/22