Skip to content
This repository has been archived by the owner on Jun 30, 2018. It is now read-only.

Success Criterion 1.4.13 Content on Hover or Focus #851

Closed
devarshipant opened this issue Apr 4, 2018 · 8 comments
Closed

Success Criterion 1.4.13 Content on Hover or Focus #851

devarshipant opened this issue Apr 4, 2018 · 8 comments

Comments

@devarshipant
Copy link

For 1.4.13, consider revising the text.

From:
Where receiving and removing pointer hover or keyboard focus triggers additional content to become visible and hidden, respectively, the following are true:

To:
When keyboard focus or pointer actions cause additional content to become either visible or hidden, the following are true:

@awkawk
Copy link
Member

awkawk commented Apr 5, 2018

Thank you for commenting. For more information about how the AG WG will process this issue, see the following:

@mbgower
Copy link
Contributor

mbgower commented Apr 5, 2018

Draft response:

Thank you for your comment.

The existing wording covers considerations not covered by your rewording.

Essentially, the SC as worded covers items which appear or disappear in coordination with hover or focus. In order to apply, the content must both appear on focus and also disappear when focus is lost (and likewise for receiving and losing hover).

Your rewording alters what would be covered by the SC. Now, any component that causes new content to appear on focus or hover would apply --even if the content is intended to persist. The bulleted items in the SC would then force the author to make that content disappear when focus is lost, even though that may not be the intended interaction of the component.

@mbgower mbgower self-assigned this Apr 5, 2018
@devarshipant
Copy link
Author

I get it now. It is easy to misread this SC.

Here is another attempt using some keywords (your version is fine too):

Original:

Where receiving and removing pointer hover or keyboard focus triggers additional content to become visible and hidden, respectively, the following are true:

Revised:

Where the sequence of steps for receiving and removing pointer hover or keyboard focus correlate with additional content to become visible and hidden, respectively, the following are true:

@mbgower
Copy link
Contributor

mbgower commented Apr 6, 2018

It is easy to misread this SC.

Agreed! I've updated the Understanding document, which I hope clarifies this as well. #854

@awkawk
Copy link
Member

awkawk commented Apr 9, 2018

@mbgower / @devarshipant what do you think about:
#857

Where receiving and then removing pointer hover or keyboard focus triggers additional content to become visible and then hidden, the following are true:

@devarshipant
Copy link
Author

Much better. thanks!

@awkawk
Copy link
Member

awkawk commented Apr 9, 2018

[Official WG Response]
Thank you for the comment, to clarify this SC we will adjust this SC text to:
"Where receiving and then removing pointer hover or keyboard focus triggers additional content to become visible and then hidden, the following are true:"

@awkawk
Copy link
Member

awkawk commented Apr 12, 2018

The WG decided on the above response, so we changed the text in the comment containing the proposed response to read "[Official WG Response]". Please confirm is you are satisfied with the response within 3 days. If we haven't heard a response by then we will regard the resolution as satisfactory.

@awkawk awkawk closed this as completed Apr 12, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants