The Accessibility of Styled Form Controls
A repository of styled and “styled” form control elements and markup patterns, and how they are announced by screen readers.
Form controls are necessary in many interfaces, but are often considered annoying, if not downright difficult, to style. Many of the markup patterns presented here can serve as a baseline for building more attractive form controls without having to exclude users who may rely on assistive technology to get things done.
In some cases, there may be a lack of support, or complications that arise when controls are styled. Those instances will be noted as well.
How to use?
The Different Form Elements
The following controls and elements each have demo pages with additional documentation pertaining to implementation, UX, and screen reader announcements.
Regarding screen reader announcements...
Note the documentation of screen reader announcements is based on using the versions of the screen reader and browser combos, as indicated on each test page. Be sure to check the last updated date of each test page. Documentation is noted as "updated" when new testing or techniques have changed. Editorial updates may not constitute a change in the posted updated date.
Things may change as browsers and screen readers are updated, so please refer to these as a snapshot in time rather than being definitive results.
If you find that announcements and/or support has changed, please file an issue!
Checkboxes and Radio Buttons
Styled HTML checkboxes, and radio button patterns.
Checkboxes can be used as a single form option, or grouped with similar checkboxes. Within a group, one or more checkboxes may be checked by the user. In contrast, radio buttons provide users two or more options to choose from, but only one option may be chosen from a radio button grouping at a time.
Switches & Toggle Buttons
Switches are a type of form control that are often visually represented as an on/off toggle. A toggle button may be styled similarly, or as a button that has a clear difference between the default and active (pressed) state. A toggle button is created when a
button has the
aria-pressed attribute set to
Unlike checkboxes, which are largely used in the context of forms where a user submits data after filling out all necessary information, switches and toggle buttons can be used to perform an instant change to a component or application’s state. As there is no “switch” in HTML, a
button element can be progressively enhanced into a
switch, with the appropriate ARIA attributes.
A styled file upload form control that relies on the native HTML
input type="file" for providing the appropriate announcements to screen readers.
A file upload allows users to add one, or more, file(s) to submit with a form.
input type="range" form control that takes multiple browser’s CSS implementations into consideration.
Range sliders allow users to select a point, or a scoped range, from a series of data.
Styled single and multi-select patterns.
Selects allow a user to pick one or more options from a menu of choices.
Progress Bar & Meter
Progress bars indicate the current status of a particular task, or tasks, on a scale of 0 to completion. A meter acts as a gauge and indicates a value within a finite value set.
meter elements are considered form elements, but they are not focusable form controls.
Unfortunately, neither of these elements are consistently accessible to screen readers. Styling each can actually make them even more inaccessible…
A search component offers users an easily discoverable way to find information in a website or application.
There are still patterns to make and test, as well as retesting of current patterns to ensure nothing gets stale. File or check out available issues for some of the stuff that needs working on :)
License, Thanks, and such
Everything here is under an MIT license.
While I was unaware of WTFForms when starting this project, it is still a great example of what can be done with only CSS, and served as an excellent baseline to compare against. Thank you mdo and to those involved with that project.
Additional thanks to Eric Bailey, Josh Drumm, James Curd, Adrian Roselli, Sara Soueidan, Heydon Pickering, Richard Keizer, Chris O’Brien and Alexander Farkas. They have each provided inspiration and/or excellent resources that have been quite helpful in the building of these components.