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

Update F26.html #3863

Merged
merged 1 commit into from
Jun 12, 2024
Merged

Update F26.html #3863

merged 1 commit into from
Jun 12, 2024

Conversation

ljoakley
Copy link
Contributor

Add a link to ARIA14 in F26.

@mgifford
Copy link

So adding a link here https://www.w3.org/WAI/WCAG22/Techniques/failures/F26#related

to add https://www.w3.org/WAI/WCAG22/Techniques/aria/ARIA14 to the Related Techniques section.

So how is Technique ARIA14: Using aria-label to provide an invisible label where a visible label cannot be used related to Technique F26:Failure of Success Criterion 1.3.3 due to using a graphical symbol alone to convey information?

It isn't as direct a relationship as either H37 or ARIA24 in my reading.

@mbgower
Copy link
Contributor

mbgower commented Jun 4, 2024

So how is Technique ARIA14: Using aria-label to provide an invisible label where a visible label cannot be used related to Technique F26:Failure of Success Criterion 1.3.3 due to using a graphical symbol alone to convey information?

@mgifford, since the failure check for F26 is:

  1. Examine the page for non-text marks that convey information.
  2. Check whether there are other means to determine the information conveyed by the non-text marks.

aria-label would be a method of resolving step 2.

In regard to your statement

It isn't as direct a relationship as either H37 or ARIA24 in my reading.

H37 is an existing related technique, which makes sense, since putting an ALT on an image is a way of resolving step 2 as well.

ARIA24, which is not in the existing failure technique nor part of this PR, can be proposed in a new issue if you like, but my feeling is that it does not actually satisfy the failure. It resolves where something isn't identified as an image; that is a different use case than where an image has no alternative (which is the failure situation in F24).

@mbgower mbgower merged commit ba81e62 into main Jun 12, 2024
1 check passed
@mbgower mbgower deleted the F26-update branch June 12, 2024 13:25
@bruce-usab
Copy link
Contributor

bruce-usab commented Jun 14, 2024

Perhaps off-topic, but I had expected the build process to automagically add the name of the technique?

Does the (F26) page title need to be entered manually? (as would be needed for any/all off-site links)

@patrickhlauke
Copy link
Member

for techniques, it doesn't seem to do this automagic thing (see the old/current F26 https://www.w3.org/WAI/WCAG22/Techniques/failures/F26) - if there is some kind of automation that runs at build time, i suspect it doesn't happen for techniques, just understanding docs cc /@iadawn

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.

None yet

5 participants