-
Notifications
You must be signed in to change notification settings - Fork 5
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
Success Criterion 1.4.13: Content on Hover or Focus (Level AA) #108
Comments
@nitedog Let me know when this is ready for survey. |
Yes, I think so. |
Non-web documents rely on a user agent, so we should say "controlled by the user agent or operating system". Or however we're saying this elsewhere — I think it's "controlled by the user agent or platform software" ...?
Nit: I would say "created through use of component properties" — name-value pairs I presume |
Created Survey for 1.4.13 Due 2 March. If you aren't a Task Force participant, you can view the survey results. |
It seems to me that use of "operating system" is too limited as this would be applied to non-web documents as well. Exceptions might be controlled through a PDF viewer or Word Processor which are user agents. |
I agree with the previous comments about "operating system" being a little restrictive Would "operating system or platform software" work if we wish to avoid using "user agent"? |
Having just caught up with the latest updates to key terms, I think we should just use the term "platform software", as the definition of this includes the operating system. See definition of "accessibility services of platform software" in key terms for more detail. Temp link is https://deploy-preview-111--wcag2ict.netlify.app/#key-terms or see detail in pull request #111 https://github.com/w3c/wcag2ict/pull/111/files |
I agree with platform software - Section 508 it defines it as: |
There are several issues:
Taking this into account and the previous comments, here is my proposal. For the additional guidance:
That would imply that the exception now reads:
And the note 1 would read:
|
Here is a version with proposals so far (as of 11 AM eastern on 1 March), incorporated and my additional edits to enumerate the word replacements consistent with how all of the other SC are handled. From Success Criterion 1.4.13:
Guidance When Applying Success Criterion 1.4.13 to Non-Web Documents and Software:This applies directly as written, and as described in Intent from Understanding Success Criterion 1.4.13 (also provided below), replacing "user agent" with "user agent or platform software", "browser tooltips" with "tooltips", and "the HTML title attribute" with "user interface object attributes". With these substitutions, it would read:
|
@ChrisLoiselle @pday1 Could one of you please implement the content from my comment above in GitHub? Whomever takes it first, unassign the other person so you aren't both working on it at the same time. |
Incorporating changes from issue #108 to incorporate SC 1.4.13: content on hover or focus
I've made a start on incorporating these changes in pull request PR #119 |
Where can we find a definition of "user interface object attributes"? |
@mraccess77 We don't have these terms defined in the document. "User interface object" is typical object oriented programming terminology for an instance/implementation of a UI component. "Attributes" are related to "properties" and in different programming languages, the "setting", "attribute" or "property" is the term used. In some programming languages there are differences between these. I have to say trying to nail down very specific terms and definitions for these that fits all software programming languages is difficult. Are you thinking we need to come up with a definition? If so, please open an issue. |
If we are replacing title attribute with a generic term it could become to wide an exception - I would recommend we try to narrow the term to cover something that is controlled by the platform/user agent. Word documents have links with title as well as an example. |
@mraccess77 This is simply a note on the exception that provides an example of what constitutes a tooltip whose display is controlled by a user agent or software platform. I don't see this as an expansion of the exception at all. The original notes in WCAG were:
In WCAG, the first note is one example for HTML. We simply provided a non-web example similar to the original one, but in a non-web software context. Are you thinking we need to expand the example to include another example for how a tooltip is typically accomplished in a non-web document? If so, I'd prefer to have a new issue to track and resolve it since the AG WG approved the WCAG2ICT guidance as-is without changes in today's meeting. |
@maryjom Ok, that seems like a reasonable approach. |
The AG WG approved the content on 11 April, so closing. |
From Success Criterion 1.4.13:
Additional Guidance When Applying Success Criterion 1.4.13 to Non-Web Documents and Software:
With these substitutions, it would read:
The text was updated successfully, but these errors were encountered: