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
WCAG 2.2 Pointer Target Spacing #1179
Commits on Jun 15, 2020
-
Configuration menu - View commit details
-
Copy full SHA for e9fb5cd - Browse repository at this point
Copy the full SHA e9fb5cdView commit details
Commits on Jun 25, 2020
-
Configuration menu - View commit details
-
Copy full SHA for 064bca6 - Browse repository at this point
Copy the full SHA 064bca6View commit details -
Configuration menu - View commit details
-
Copy full SHA for 0f1ba73 - Browse repository at this point
Copy the full SHA 0f1ba73View commit details -
Configuration menu - View commit details
-
Copy full SHA for a2bb34e - Browse repository at this point
Copy the full SHA a2bb34eView commit details -
Michael Cooper committed
Jun 25, 2020 Configuration menu - View commit details
-
Copy full SHA for 0c43268 - Browse repository at this point
Copy the full SHA 0c43268View commit details -
add id to figure in understanding
Michael Cooper committedJun 25, 2020 Configuration menu - View commit details
-
Copy full SHA for f054071 - Browse repository at this point
Copy the full SHA f054071View commit details
Commits on Jun 26, 2020
-
Tackling questions by JAWS-test
Addressing #1179 (comment) The points are addressed in a new section, "Scope and applicability" Also updating the second paragraph in section "Intent of Pointer Target Spacing" to make it easier to understand (or so I hope).
Configuration menu - View commit details
-
Copy full SHA for 6e042ef - Browse repository at this point
Copy the full SHA 6e042efView commit details -
Configuration menu - View commit details
-
Copy full SHA for 914d2d8 - Browse repository at this point
Copy the full SHA 914d2d8View commit details
Commits on Jun 30, 2020
-
Modified the bit on native targets
Took out the bit that the SC applies to the spacing between native elements (I think it that is clear), but addressing @JAWS-test's comments, added an exception for the spacing of targets _inside_ unstyled native elements (i.e. where the vertical spacing of options in a select is determined by the default browser behaviour).
Configuration menu - View commit details
-
Copy full SHA for 33a9049 - Browse repository at this point
Copy the full SHA 33a9049View commit details -
Following comments by @patrickhlauke I removed mention of touch in two places.
Configuration menu - View commit details
-
Copy full SHA for f2afbe4 - Browse repository at this point
Copy the full SHA f2afbe4View commit details -
Added a third example (row of buttons with sufficient spacing above and below). Edited the figcation / legend of thee image with the three differnet positionings of the magnify icon over a profile image, reduced length of the alt attribute.
Configuration menu - View commit details
-
Copy full SHA for 2598fc1 - Browse repository at this point
Copy the full SHA 2598fc1View commit details -
Criteria > criterion, section on adapation
@patrickhlauke Changed criteria to criterion where needed Changed some of the figaption text to make them easier to understand Changed an odd sentence above the profile images /maginfication icons illustiration Changed the paragraph above h2 Benefits (pointing out the benefits of general adaptability of size/spacing) Added a third example in second position (row of buttons where enough vertical spacing is present to meet SC)
Configuration menu - View commit details
-
Copy full SHA for c403203 - Browse repository at this point
Copy the full SHA c403203View commit details -
I improved the ficaption legends of the illustration, some were hard to understand. I improved the image legends / figcaption texts, and removed the heading Scope and applicability, would have needed a further subheading to separate what are essentialy examples with illustrations. It is odd that there is an actual section Examples further down whithout illustrations, but I do not want to carry through a complete overhaul of the Understanding page at this point. I think it would generally be benefitial to have more subheadings in the longier understanding pages, not just Intent / Benefits / examples, but I am not sure how flexible we are in this respect...
Configuration menu - View commit details
-
Copy full SHA for 3cf7ebf - Browse repository at this point
Copy the full SHA 3cf7ebfView commit details -
Configuration menu - View commit details
-
Copy full SHA for 8393a07 - Browse repository at this point
Copy the full SHA 8393a07View commit details -
Configuration menu - View commit details
-
Copy full SHA for 9968230 - Browse repository at this point
Copy the full SHA 9968230View commit details -
Configuration menu - View commit details
-
Copy full SHA for 78b316e - Browse repository at this point
Copy the full SHA 78b316eView commit details -
Configuration menu - View commit details
-
Copy full SHA for 46b5681 - Browse repository at this point
Copy the full SHA 46b5681View commit details -
Configuration menu - View commit details
-
Copy full SHA for dba96a6 - Browse repository at this point
Copy the full SHA dba96a6View commit details -
Configuration menu - View commit details
-
Copy full SHA for 72bd145 - Browse repository at this point
Copy the full SHA 72bd145View commit details -
Configuration menu - View commit details
-
Copy full SHA for 56d7447 - Browse repository at this point
Copy the full SHA 56d7447View commit details
Commits on Jul 2, 2020
-
Configuration menu - View commit details
-
Copy full SHA for fd72e01 - Browse repository at this point
Copy the full SHA fd72e01View commit details -
Configuration menu - View commit details
-
Copy full SHA for 9fca895 - Browse repository at this point
Copy the full SHA 9fca895View commit details -
Configuration menu - View commit details
-
Copy full SHA for c770d73 - Browse repository at this point
Copy the full SHA c770d73View commit details -
Configuration menu - View commit details
-
Copy full SHA for 1fe18b5 - Browse repository at this point
Copy the full SHA 1fe18b5View commit details
Commits on Jul 8, 2020
-
Configuration menu - View commit details
-
Copy full SHA for 4cdc3eb - Browse repository at this point
Copy the full SHA 4cdc3ebView commit details
Commits on Jul 16, 2020
-
Configuration menu - View commit details
-
Copy full SHA for 1fcbc94 - Browse repository at this point
Copy the full SHA 1fcbc94View commit details -
Configuration menu - View commit details
-
Copy full SHA for 94843d1 - Browse repository at this point
Copy the full SHA 94843d1View commit details -
Changed to "or must be placed at the edge" Accepted "to make sure that there is sufficient adjacent spacing in each dimension" Changed to "and a magnifying glass" Changed "excempted" -> exempted
Configuration menu - View commit details
-
Copy full SHA for 00df37d - Browse repository at this point
Copy the full SHA 00df37dView commit details -
Added intro sentence in section benefits
Slightly changed wording: "Having targets with sufficient target spacing can help all users who may have difficulty in confidently targeting or operating small controls. Users who benefit include, but are not limited to:"
Configuration menu - View commit details
-
Copy full SHA for 78fa9d7 - Browse repository at this point
Copy the full SHA 78fa9d7View commit details -
Configuration menu - View commit details
-
Copy full SHA for 128c97e - Browse repository at this point
Copy the full SHA 128c97eView commit details -
Udate of name of sufficient Technique
Updated name to "Using min-height and min-width to ensure sufficient target spacing"
Configuration menu - View commit details
-
Copy full SHA for 3e4dbd0 - Browse repository at this point
Copy the full SHA 3e4dbd0View commit details
Commits on Jul 21, 2020
-
Configuration menu - View commit details
-
Copy full SHA for 4a7ed23 - Browse repository at this point
Copy the full SHA 4a7ed23View commit details