You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Each preset is has the role of "option" but also contain more interactive items nested in the option to perform actions like delete or edit. This is not an expected pattern for the role, and many non-visual and low-vision users will not anticipate the nested actions in an "option" object.
Separate the different functions of the task into their own interactive elements. The "option" role does not need to be used here because it is typically understood to be part of a select HTML element or a widget with a listbox role, which is not the case for the preset choices.
In addition, the option element should only contain text, so including interactive elements becomes somewhat of an anti-pattern.
One alternative is to have each preset grouped but put the actions into their own interactive elements, e.g., buttons. A very simple example of an alternative UI can be seen here: CodePen Demo.
derekjackson-das
changed the title
Nested Interactive Elements in the Options of the Presets Panel
Presets Panel: Nested Interactive Elements in the Options
Jan 27, 2025
derekjackson-das
changed the title
Presets Panel: Nested Interactive Elements in the Options
Presets Panel: Nested Interactive Elements
Jan 27, 2025
Issue Description
Each preset is has the role of "option" but also contain more interactive items nested in the option to perform actions like delete or edit. This is not an expected pattern for the role, and many non-visual and low-vision users will not anticipate the nested actions in an "option" object.
WCAG Criteria
1.3.1 Info and Relationships - A
Notes
Separate the different functions of the task into their own interactive elements. The "option" role does not need to be used here because it is typically understood to be part of a
select
HTML element or a widget with alistbox
role, which is not the case for the preset choices.In addition, the
option
element should only contain text, so including interactive elements becomes somewhat of an anti-pattern.One alternative is to have each preset grouped but put the actions into their own interactive elements, e.g., buttons. A very simple example of an alternative UI can be seen here: CodePen Demo.
More details about the option role: MDN Option Role.
Screenshot or Screen Recording
Relevant Code
The text was updated successfully, but these errors were encountered: