New Failure Technique for 1.4.13 Content on hover or focus when popup content cannot be dismissed #4770
Conversation
✅ Deploy Preview for wcag2 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Changed Technique `title` and `h1` to include SC 1.4.13
Change of "When to use" text
syntax corrections
Extension of description
Slight change to title and h1
Edit of description
Editing examples
minor typo corrections
detlevhfischer
changed the title
New Failure Technique for 1.4.13 Content on hover or focus (popup content disappears when the pointer is moved over it)
detlevhfischer
changed the title
Failure techniwque for 1.4.13 Content on hover or focus to cover situations where the pointer cannot be moved over popup content without that content automatically closing.
detlevhfischer
changed the title
detlevhfischer
changed the title
|
@detlevhfischer is this addressing an existing github issue? |
There was a problem hiding this comment.
@detlevhfischer, failure techniques normally follow a set structure. A succinct description of the scenario that is actually the failure (not a regurgitation of the SC), then an example, and then a test procedure that is in a very structure format. Here's how I'd suggest the description and test procedure could start.
Description
This describes the failure condition that results when content that appears on hover or focus cannot be dismissed in a way that meets the requirements of 1.4.13. The success criterion lists three conditions that must be true, and one of these is that the content that appears must be dismissible:
A mechanism is available to dismiss the additional content without moving pointer hover or keyboard focus, unless the additional content communicates an input error or does not obscure or replace other content;"
Tests
Procedure
For content that appears on hover and focus:
It is picking up two of the future techniques listed here: #4378 ...which made me believe such techniques should be welcome. I have followed the scenario of description, examples, test that you point at, keeping it short. What do you think is missing? As to your suggestion to explain the SC (the three things that are covered) I personally think that is the task of the understanding doc. The failures I have drafted cover one of these points individually (dismissability and hoverability of new popup content) so IMHO, dilating into the other aspects does not seem helpful in applying the respective failure technique. |
I have attempted to write a Failure Technique for 1.4.13 Content on hover and focus.
Preview: https://deploy-preview-4770--wcag2.netlify.app/techniques/failures/f114
The concern I have is whether the Failure Technique should not also allow (and check) for other author-specified and documented ways of dismissing popup content, such as -- to give a morwe or less random example -- a documented "pressing ALT + C closes popup content". This may reside on the page or in generic settings where discoverability is poor. The normative text does not delimit ways to dismiss content. Not sure if this can be added as a third point and how that would be phrased, something like "Check if there are documented methods for dismissing popup content. If this is the case, check if the documented method succeeds in closing popup content called up by pointer hover or keyboard focus." If this is difficult to nail down, this could be an indication that a watertight FAILURE Technique is not feasible here.