Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[WCAG AAA] - Move H28 from sufficient to advisory in 3.1.4 Abbreviations SC #4195

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

giacomo-petri
Copy link
Contributor

Closes: #3019

H28 is not a sufficient technique, rather than an advisory one, since it would likely fail 2.1.1

Actions: moved H28 from sufficient to advisory.

@giacomo-petri giacomo-petri self-assigned this Jan 12, 2025
Copy link

netlify bot commented Jan 12, 2025

Deploy Preview for wcag2 ready!

Name Link
🔨 Latest commit 0c6f605
🔍 Latest deploy log https://app.netlify.com/sites/wcag2/deploys/6783d63da258e9000888f46e
😎 Deploy Preview https://deploy-preview-4195--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 site configuration.

@bruce-usab
Copy link
Contributor

Discussed on Backlog call 1/17. Moved to Ready for approval.

@mbgower
Copy link
Contributor

mbgower commented Feb 7, 2025

IMO, there should be some language inside the technique, and maybe inside the Understanding document (i.e., in the final example), explaining the matter raised in the issue.

The SC language reads:

A mechanism for identifying the expanded form or meaning of abbreviations is available.

The use of <abbr> with an appropriate value for the title attribute clearly provides a mechanism for identifying the meaning of the abbreviation. So we have to be clear that the reason this is not sufficient is because of the note in the definition of mechanism

The mechanism needs to meet all success criteria for the conformance level claimed.

The argument is that use of title fails to meet 2.1.1 Keyboard and so is not a sufficient mechanism, correct? We should state that.

@bruce-usab bruce-usab self-requested a review February 7, 2025 15:51
Copy link
Contributor

@bruce-usab bruce-usab left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am of the opinion that something should be added to H28 explaining why it has been down graded from sufficient to advisory.

Keyboard support for abbr has been weak, but historically we didn't assert that the default behavior of the element fails 2.1.1. But maybe enough time has passed that we should?

@bruce-usab
Copy link
Contributor

bruce-usab commented Feb 7, 2025

Discussed on backlog call 2/7. @mbgower agreed to take another pass, stays in For discussion.

@mbgower mbgower self-assigned this Feb 18, 2025
@bruce-usab
Copy link
Contributor

Discussed on backlog call 2/21. Keeping in For Discussion as Mike is still has this in his queue.

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.

Technique H28 should not be sufficient to meet 3.1.4: Abbreviations
3 participants