Skip to content

The longdesc attribute explanation remains on the Understanding Conformance page #4243

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

Closed
momdo opened this issue Feb 25, 2025 · 2 comments · Fixed by #4365
Closed

The longdesc attribute explanation remains on the Understanding Conformance page #4243

momdo opened this issue Feb 25, 2025 · 2 comments · Fixed by #4365

Comments

@momdo
Copy link
Contributor

momdo commented Feb 25, 2025

The longdesc attribute is marked as obsolete in WCAG 2.2 Techniques H45, but Understanding Conformance page still contains a reference to it.

Sometimes, supplemental information may be available from another page for information on a page. The longdesc attribute in HTML is an example. With longdesc, a long description of a graphic might be on a separate page that the user can jump to from the page with the graphic. This makes it clear that such content is considered part of the Web page, so that requirement #2 is satisfied for the combined set of Web pages considered as a single Web page. Alternatives can also be provided on the same page. For example creating an equivalent to a user interface control.

@fstrr
Copy link
Contributor

fstrr commented Feb 25, 2025

Correct link to the Understanding Conformance page.

@patrickhlauke
Copy link
Member

Filed #4365

mbgower added a commit that referenced this issue May 20, 2025

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
…of `longdesc` (#4365)

The attribute is deprecated, so shouldn't be mentioned/referenced.

Closes #4243

---------

Co-authored-by: Mike Gower <mikegower@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants