Controls
Accessible buttons: Examples and Testing
Use a native button for an action performed on the current page, such as saving a draft or opening a dialog.
Accessible patterns
Explore 40 accessible interface patterns, from everyday form controls to dialogs, navigation and feedback. Use the working examples, inspect the markup relationships and record your own tests.
Use the browser’s built-in interaction before choosing a custom widget.
Open, navigate and close a dialog with a predictable return point.
Help people identify a problem and return to the field that needs attention.
40 resources found
Controls
Use a native button for an action performed on the current page, such as saving a draft or opening a dialog.
Controls
A toggle button represents an on/off state for an action or mode.
Navigation
Use a real anchor with a destination when the purpose is navigation.
Forms
Use a checkbox for an independently selectable choice.
Forms
Radio buttons let users choose one option within a named group.
Controls
A switch represents a setting that is on or off.
Forms
Give text inputs visible labels and explain important constraints before entry.
Forms
Use a labeled textarea for multiline input.
Forms
For a straightforward choice from a fixed list, a native select supplies familiar keyboard and platform behavior.
Forms
Use numeric controls when the value is a quantity, and explain units, bounds and valid increments.
Controls
A slider selects a value from an ordered range.
Status and feedback
Use a progress indicator for completion of an ongoing task.
Status and feedback
A meter describes a scalar measurement within a known range, such as storage used.
Status and feedback
An error summary gives users a compact route to all detected problems after submission.
Status and feedback
Inline errors identify the affected field and explain what must change.
Status and feedback
Routine status messages should communicate results without taking focus.
Status and feedback
Use an alert for important, time-sensitive information that needs prompt announcement without requiring focus.
Disclosure and dialogs
A tooltip supplies a brief description for a focused or hovered control.
Data and collections
A carousel needs understandable slide controls and an accessible way to stop automatic rotation when used.
Forms
A combobox combines an input or selection control with an associated popup.
Data and collections
A listbox presents selectable options with a managed keyboard interaction model.
Data and collections
A tree represents a hierarchical collection with expandable branches and a full tree keyboard model.
Controls
A toolbar groups a related set of controls and, when using the ARIA toolbar pattern, provides efficient keyboard movement within that group.
Forms
Keep a labeled native file input available even when a drag-and-drop area is offered.
Forms
Password inputs need clear labels, appropriate autocomplete and support for password managers and paste.
Forms
A search form needs a discoverable search region, a labeled query field, a clear submit action and understandable results.
Page structure
A description list expresses associations between terms and their descriptions or values.
Disclosure and dialogs
A disclosure reveals or hides a section in place.
Disclosure and dialogs
An accordion organizes related expandable sections.
Disclosure and dialogs
A modal dialog temporarily makes the rest of the page unavailable while the user completes a focused task.
Disclosure and dialogs
Use an alert dialog for a brief, important interruption that requires a response, such as confirming a consequential deletion.
Navigation
Tabs switch among associated panels within a single interface.
Navigation
Most website dropdown navigation is a disclosure containing ordinary links, not an application menu.
Navigation
Breadcrumbs communicate a page's location within a site hierarchy.
Navigation
Pagination needs understandable page links, a current-page indication and predictable behavior when results change.
Navigation
A skip link lets keyboard users bypass repeated navigation and reach the page's main task.
Page structure
Landmarks identify major page regions such as navigation, main content, search and the footer.
Page structure
Use heading elements to express the content's hierarchy, and write headings that describe their sections.
Data and collections
Use a table when cells have meaningful row and column relationships.
Data and collections
A sortable table retains its table structure while exposing sorting as an action in the relevant header.