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
Currently, users are able to select and enable multiple accessibility themes (e.g., Dark Mode, Monochrome Mode) at the same time. This behavior is not common, as usually only one theme is active at a time. However, when all themes are selected, they function without causing visual or functional conflicts.
Expected Behavior
Only one accessibility theme should be active at a time. When selecting a new theme, the previously selected theme should automatically be deselected. Alternatively, if multiple themes are intentionally allowed, the interface should clearly communicate that users can activate more than one.
Steps to reproduce
Navigate to the any page
Would you like to work on the issue?
yes
The text was updated successfully, but these errors were encountered:
Enabling multiple accessibility features are by design and it is reasonable to expect intersectional accessibility requirements. I'm not fully sure why this is an issue though, would you be able to elaborate more on what you mean?
Most appropriate sections of the p5.js website?
Reference
What is your operating system?
Windows
Web browser and version
No response
Actual Behavior
Currently, users are able to select and enable multiple accessibility themes (e.g., Dark Mode, Monochrome Mode) at the same time. This behavior is not common, as usually only one theme is active at a time. However, when all themes are selected, they function without causing visual or functional conflicts.
Expected Behavior
Only one accessibility theme should be active at a time. When selecting a new theme, the previously selected theme should automatically be deselected. Alternatively, if multiple themes are intentionally allowed, the interface should clearly communicate that users can activate more than one.
Steps to reproduce
Would you like to work on the issue?
yes
The text was updated successfully, but these errors were encountered: