Skip to content

Alternatives match language #4262

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

Merged
merged 25 commits into from
Apr 22, 2025
Merged

Alternatives match language #4262

merged 25 commits into from
Apr 22, 2025

Conversation

mbgower
Copy link
Contributor

@mbgower mbgower commented Mar 4, 2025

Closes #3873 by adding a concept of matching language to understanding documents and techniques for 1.1 and 1.2

Also for the 1.2 Time-based Media page, added some previously missing content.

mbgower added 2 commits March 4, 2025 15:18
Update to 1.1.1 Understanding document to address #3873
Copy link

netlify bot commented Mar 4, 2025

Deploy Preview for wcag2 ready!

Name Link
🔨 Latest commit eea3760
🔍 Latest deploy log https://app.netlify.com/sites/wcag2/deploys/68067d491c50a40008cc26ce
😎 Deploy Preview https://deploy-preview-4262--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.

mbgower and others added 17 commits March 5, 2025 08:38
Added matching language concept to the technique and test
Updated G159 to incorporate the concept of matching the language of the page or video in the alternative
Added language considerations to the G166 technique
Added matching language concept to the G93 technique
Added matching language to G87
Modified G87 to more closely match the pre-existing wording of H95
Adding language consideration to G69
Added concept of matching language to G78.
Added matching language to the technique description
added matching language to technique description for G8
Added matching language to G9
Added matching language concept to 1.2.5
Added concept of human language to 1.2.8
Added subsection on matching language for 1.1
@mbgower mbgower marked this pull request as ready for review March 5, 2025 19:45
@patrickhlauke patrickhlauke self-requested a review March 7, 2025 16:51
@patrickhlauke patrickhlauke self-assigned this Mar 7, 2025
@mbgower
Copy link
Contributor Author

mbgower commented Mar 7, 2025

@patrickhlauke on today's call I was momentarily confused into thinking I'd adjusted a definition by this line
<a class="glossary">audio description</a>. This is done by providing an alternative for time-based media in the same <a>human language</a> as the video or page on which it appears.

However, as is likely apparent to you, this is not the glossary definition within the Understanding, but a link in the Understanding doc to the definition, followed by more text. So it works fine as is.

@mbgower mbgower merged commit 44b2303 into main Apr 22, 2025
5 checks passed
@mbgower mbgower deleted the Alternatives-match-language branch April 22, 2025 13:21
EricDunsworth added a commit to EricDunsworth/wcag that referenced this pull request Apr 22, 2025
Some of the content added by w3c#4262 contained links that were closed with <a> tags instead of </a>. That in turn caused large chunks of content to be transformed into hash (#) links.

Specifically:
* Understanding Guideline 1.1: Text Alternatives
  * https://w3c.github.io/wcag/understanding/text-alternatives.html#text-alternatives-and-equivalents-match-the-language-of-the-content
* Understanding SC 1.1.1: Non-text Content (Level A)
  * https://w3c.github.io/wcag/understanding/non-text-content.html#note-on-alternatives-matching-the-language-of-content
* Understanding Guideline 1.2: Time-based Media
  * https://w3c.github.io/wcag/understanding/time-based-media.html#text-alternatives-and-equivalents-match-the-language-of-the-content

This resolves it by replacing the affected <a> tags with </a>.
kfranqueiro pushed a commit that referenced this pull request Apr 30, 2025
Some of the content added by #4262 contained links that were closed with
`<a>` tags instead of `</a>`. That in turn caused large chunks of
content to be transformed into hash (`#`) links.

This resolves it by replacing the affected `<a>` tags with `</a>`.
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.

1.2.3 / 1.2.5 Audio description - right language required?
3 participants