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 2.2 errata: encloses definition title, style and presence? #3510

Open
rscano opened this issue Oct 20, 2023 · 7 comments · May be fixed by #3636
Open

WCAG 2.2 errata: encloses definition title, style and presence? #3510

rscano opened this issue Oct 20, 2023 · 7 comments · May be fixed by #3636
Assignees
Labels
ErratumRaised Potential erratum for a Recommendation WCAG 2.2

Comments

@rscano
Copy link
Contributor

rscano commented Oct 20, 2023

Title attibute for encloses states: title="Found definition for "encloses", but nothing links to it. This is usually a spec bug!" should not be present.

Also there is a class for this term that let it underlined by red color: class="respec-offending-element" . Why?

Another question: due this term is not referred in any part of document, why is present inside spec?

@mbgower
Copy link
Contributor

mbgower commented Oct 20, 2023

To confirm, you are referring to https://www.w3.org/TR/WCAG22/#:~:text=encloses,bounds%20or%20surrounds ?

@mbgower mbgower added WCAG 2.2 ErratumRaised Potential erratum for a Recommendation labels Oct 20, 2023
@rscano
Copy link
Contributor Author

rscano commented Oct 20, 2023

Yes. Seems to be not needed (and also keep attention of users with wave underline)

@mbgower
Copy link
Contributor

mbgower commented Nov 3, 2023

@alastc what's the best thing to do with this?

@maryjom
Copy link
Contributor

maryjom commented Nov 9, 2023

This error comes from the new term "encloses" which is defined but not used or linked to anywhere in the spec. I was just looking at this for WCAG2ICT. At one point it was used in the Level AA Focus Appearance SC.

@alastc alastc linked a pull request Jan 12, 2024 that will close this issue
@yatil
Copy link
Contributor

yatil commented Jan 24, 2024

Until #3636 is merged and an update to WCAG 2.2 published (which could take weeks), @alastc maybe update the Errata document for WCAG 2.2. Translators otherwise need to translate it.

@rscano
Copy link
Contributor Author

rscano commented Jan 24, 2024

Until #3636 is merged and an update to WCAG 2.2 published (which could take weeks), @alastc maybe update the Errata document for WCAG 2.2. Translators otherwise need to translate it.

So, need to remove this from translation or add something in WCAG 2.2 errata in italian language?

@patrickhlauke
Copy link
Member

patrickhlauke commented Jan 24, 2024

related (though likely not worth the pain of making a normative change): Note 1 for https://www.w3.org/TR/WCAG22/#focus-appearance still includes remnants of the fact that this SC included the concept of "encloses" at an earlier point (which is where the definition came from, before that idea was removed from the normative wording of the SC, if I recall correctly).

What is perceived as the user interface component or sub-component (to determine enclosure or size)

that now doesn't really make sense/is a non-sequitur

patrickhlauke added a commit that referenced this issue Jan 24, 2024
Removes the reference to "encloses" (which still comes from an earlier version of the SC text) and "size", and instead uses "perimeter" which is directly relevant to the normative text itself

See #3510 (comment)
mbgower pushed a commit that referenced this issue Apr 2, 2024
Removes the reference to "encloses" (which still comes from an earlier
version of the SC text) and "size", and instead uses "perimeter" which
is directly relevant to the normative text itself

See #3510 (comment)


<!--
    This comment and the below content is programmatically generated.
    You may add a comma-separated list of anchors you'd like a
    direct link to below (e.g. #idl-serializers, #idl-sequence):

    Don't remove this comment or modify anything below this line.
    If you don't want a preview generated for this pull request,
    just replace the whole of this comment's content by "no preview"
    and remove what's below.
-->
***
<a href="https://pr-preview.s3.amazonaws.com/w3c/wcag/pull/3657.html"
title="Last updated on Feb 29, 2024, 8:46 PM UTC (2b8f1be)">Preview</a>
| <a
href="https://pr-preview.s3.amazonaws.com/w3c/wcag/3657/33a5559...2b8f1be.html"
title="Last updated on Feb 29, 2024, 8:46 PM UTC (2b8f1be)">Diff</a>

Co-authored-by: Bruce Bailey <bailey@access-board.gov>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ErratumRaised Potential erratum for a Recommendation WCAG 2.2
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants