Should form labels be wrapped or separate?
Is it strictly necessary for form fields and labels to have for/id association, or is it enough to wrap the label around the input?
Article Category
Posts
-
-
Is swiping a path-based gesture?
A path-based gesture involves an interaction where not just the endpoints matter. So does that include swiping? Well … it depends.
-
How to test 2.4.11: Focus Not Obscured (Minimum)
This SC requires that interactive controls are not entirely obscured by author-created content, at the point when they receive focus.
-
How to test 3.3.8 Accessible Authentication (Minimum)
This SC is concerned with cognitive function tests that are used to authenticate users, such as username and password input, CAPTCHA, and 2FA.
-
How to test 2.5.8 Target Size (Minimum)
Resuming our series after the season’s hiatus, this article looks at testing for minimum target size and spacing of interactive controls.
-
The Road to Accessible Drag and Drop (Part 3)
The conclusion to our mini-series is detailed documentation, with everything you need to configure and use the DragAct codebase.
-
The Road to Accessible Drag and Drop (Part 2)
Drag and drop can indeed be made accessible to assistive technologies. This article explores some techniques and solutions for achieving that.
-
The Road to Accessible Drag and Drop (Part 1)
How can drag and drop be made accessible to assistive technologies? We’ll explore this question over three articles, beginning with a fundamental question.
-
How to test 2.5.7 Dragging Movements
This article is about testing for 2.5.7 Dragging Movements, which requires that things like drag and drop can also be operated by single pointer actions.
-
How to test 3.3.7 Redundant Entry
Continuing our series of articles on how to test the new Success Criteria (SC) in WCAG 2.2, this time we’ll be looking at 3.3.7 Redundant Entry.
-
How to test 3.2.6 Consistent Help
This is the first in a series of articles, looking at how to test each of the new Success Criteria in WCAG 2.2, beginning with 3.2.6 Consistent Help.
-
Evolving custom sliders
Combining the accessibility and usability benefits of a native range input, with the markup and design flexibility of a pure custom slider.
-
Prevent focused elements from being obscured by sticky headers
Focused elements disappearing under sticky headers is a long-standing accessibility problem. Here’s a solution.
-
The anatomy of visually-hidden
You’ve probably used visually-hidden content before. But how does the CSS actually work, and why do we use those particular properties?
-
New Success Criteria in WCAG 2.2
This article is an overview of the new SCs in WCAG 2.2, describing their requirements in plain language, and discussing how to meet them.
-
The Ballad of Text Overflow
The text-overflow property can be used to show visual indication of truncated text. I’m not a fan, and take every opportunity to discourage its use.
-
Testing with speech recognition
This article is a guide to testing your web content using speech recognition, looking at the ways in which speech recognition users interact with content, and the accessibility considerations these imply.
