Skip to content

Tweak Understanding Headings and Labels 2.4.6#4876

Open
bruce-usab wants to merge 2 commits intomainfrom
bruce-usab-patch-understanding
Open

Tweak Understanding Headings and Labels 2.4.6#4876
bruce-usab wants to merge 2 commits intomainfrom
bruce-usab-patch-understanding

Conversation

@bruce-usab
Copy link
Contributor

@bruce-usab bruce-usab commented Jan 16, 2026

Editorial suggestion for Understanding for Headings and Labels, removing the use of requires in a couple of places.

A preview diff is available.

Editorial suggestion for Understanding for Headings and Labels, removing the use of <q>requires</q> in a couple of places.
@netlify
Copy link

netlify bot commented Jan 16, 2026

Deploy Preview for wcag2 ready!

Name Link
🔨 Latest commit 008ae5e
🔍 Latest deploy log https://app.netlify.com/projects/wcag2/deploys/696a9d1ae1d4250008925689
😎 Deploy Preview https://deploy-preview-4876--wcag2.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@bruce-usab bruce-usab changed the title Tweak Understanding Headings and Labels 2.4.3 Tweak Understanding Headings and Labels 2.4.6 Jan 16, 2026
@bruce-usab
Copy link
Contributor Author

I was prompted to propose change by “does not require headings or labels” when meeting WCAG does (generally) require (good) use of headings and labels. I will also confess to being triggered by the semicolon.

@patrickhlauke
Copy link
Member

the "does not require" wording was added (by me at the time) because far too often i was seeing auditors failing pages under 2.4.6 for not having headings or labels where they felt there should be some

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants