-
-
Notifications
You must be signed in to change notification settings - Fork 847
Closed
Labels
Complexity: See issue making labelSee the Issue Making label to understand the issue writing difficulty levelSee the Issue Making label to understand the issue writing difficulty levelFeature: AccessibilityIssues that would broaden website accessibilityIssues that would broaden website accessibilityIssue Making: Level 1Make issues from a template and a spreadsheetMake issues from a template and a spreadsheetP-Feature: Sitemaphttps://www.hackforla.org/sitemap/https://www.hackforla.org/sitemap/epicgood first issueGood for newcomersGood for newcomersrole: front endTasks for front end developersTasks for front end developerssize: 0.25ptCan be done in 0.5 to 1.5 hoursCan be done in 0.5 to 1.5 hours
Milestone
Description
Dependency
- SiteMap Page: Update alt text for SiteMap Header Hero image to adhere to WCAG #6798
- SiteMap Page: Update alt text for Suggested Site Icon image to adhere to WCAG #6799
- SiteMap Page: Update alt text for Page Card Icon image to adhere to WCAG #6800
Overview
We need to ensure that alt text for images adhere to Web Content Accessibility Guidelines (WCAG). For this epic, we will write issues to change the alt text for the images in the SiteMap page which will then be added to dependency items above.
Details
Designers and PMs identified that some alt texts in the SiteMap 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
- Create issues using the following steps (These steps would be recurring for each issue that would be created, and this action item should stay unchecked until all the issues have been created):
- Check the following Google spreadsheet tab to track the issue creation progress (there are 3 issues in total that need to be made)
- Choose a row for which issue needs to be created and add your name in the Issue writer column. (If multiple team members creating issues simultaneously, let other team members know which row you would be working on, so there are no duplicate issues). See column H to know if an issue has been made already
- Create a new issue with steps to change the alt text for an image following the sample issue below as well as using How to create issues wiki.
- Update the issue link in the Google spreadsheet tab
- Add the issue numbers of all the issues that have been created to the dependency section above.
- If all the issues for the spreadsheet tab have been created, add a dependency label and move this issue to icebox column.
- If all the dependency issues are closed, remove the dependency label, move this issue from ice box to In progress column and close this issue.
Resources/Instructions
- SiteMap page
- Google spreadsheet tab to track issue creation
- How to create issues wiki
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Complexity: See issue making labelSee the Issue Making label to understand the issue writing difficulty levelSee the Issue Making label to understand the issue writing difficulty levelFeature: AccessibilityIssues that would broaden website accessibilityIssues that would broaden website accessibilityIssue Making: Level 1Make issues from a template and a spreadsheetMake issues from a template and a spreadsheetP-Feature: Sitemaphttps://www.hackforla.org/sitemap/https://www.hackforla.org/sitemap/epicgood first issueGood for newcomersGood for newcomersrole: front endTasks for front end developersTasks for front end developerssize: 0.25ptCan be done in 0.5 to 1.5 hoursCan be done in 0.5 to 1.5 hours
Type
Projects
Status
QA