[go: nahoru, domu]
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.

Sign up for GitHub

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

Jump to bottom

WCAG/HTML name computation discrepancy with `<img alt="" title="foo"> #99

Closed
cookiecrook opened this issue Jul 7, 2017 · 4 comments
Closed

WCAG/HTML name computation discrepancy with `<img alt="" title="foo"> #99

cookiecrook opened this issue Jul 7, 2017 · 4 comments

Comments

@cookiecrook
Copy link
Collaborator

The following text in HTML-AAM:

~If "any labeling attribute … specifies an empty label … indicates the author's intention to indicate that the img is decorative or redundant. In this case, the user agent MUST set the name to an empty string."

Conflicts with WCAG Success Criteria H67: https://www.w3.org/TR/WCAG20-TECHS/H67.html

For each image that should be ignored: Check that title attribute is either absent or empty. Check that alt attribute is present and empty. ...

Furthermore, both Blink and Gecko allow this behavior. WebKit currently matches the HTML-AAM spec, but will likely change to match the other behavior. https://webkit.org/b/173870

Test case 7 here:
https://bugs.webkit.org/attachment.cgi?id=314203
@cookiecrook
Copy link
Collaborator Author

HTML-AAM also specifies this normative requirement in an non-normative note. The normative text does not include this "empty label" exception.

@cookiecrook cookiecrook mentioned this issue Jul 7, 2017
Closed
@cookiecrook
Copy link
Collaborator Author

Similar issue in w3c/aria#602

@stevefaulkner
Copy link
Contributor

I think this is a reasonable change, as while it is a conformance error to use the empty alt, title with content pattern, it is useful for end users to get some accessible name in this case.

@stevefaulkner
Copy link
Contributor

I have removed the 'normative note' ;-) which should resolve the issue from the aam perspective.

@jnurthen jnurthen mentioned this issue May 21, 2018
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@cookiecrook @stevefaulkner