govau/design-system-components

How screen readers pronounce 'content' in context with...

Open

#868 opened on Aug 8, 2019

View on GitHub
 (3 comments) (3 reactions) (0 assignees)HTML (741 stars) (115 forks)batch import
accessibilitygood first issuemodule: skip-linksm7

Description

Minor recommendation:

Screen readers announce the word 'content' in the 'Skip to content' bypass block in the context of 'feeling content' the inflection is different to the intended meaning of 'the word.

Adding the word 'main' into the mix fixes the pronunciation 'Skip to main content' is vocalized in the correct pronunciation.

Pedantic; I know :-)

Contributor guide

Tech stack
html
Domain
frontendaccessibility
Issue type
accessibility
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
HTMLaccessibility basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
95
Research direction
Locate the 'Skip to content' link in the component templates (likely in the header or layout component). Update the anchor text to 'Skip to main content' to ensure screen readers pronounce the word correctly. Test using a screen reader to verify the fix.