Impact: Assistive technology doesn't announce it as the right control and might cause confusion for impaired users
Description
Details
Related Objects
Event Timeline
Change 620662 had a related patch set uploaded (by Tam-edwin-microsoft; owner: Tam-edwin-microsoft):
[oojs/ui@master] ToggleSwitchWidget: fixed wrong role type
Change 620662 merged by jenkins-bot:
[oojs/ui@master] ToggleSwitchWidget: fixed wrong role type
Change 621711 had a related patch set uploaded (by VolkerE; owner: VolkerE):
[mediawiki/core@master] Update OOUI to v0.40.2
Change 621989 had a related patch set uploaded (by Michael Große; owner: Michael Große):
[oojs/ui@master] Fix the removing of windows being broken by this scoping issue
Change 621989 merged by jenkins-bot:
[oojs/ui@master] Follow-up I669cfeeb: Fix the removing of windows being broken by this scoping issue
Is there more to do in this task, or could this task be resolved (via Add Action... → Change Status in the dropdown menu)? Thanks in advance! :)
@Volker_E merged the original patch with suggestion. Is there a need to link a separate item to track this feedback or is just documenting here enough?
Merging with some cautionary feedback. Haven't found any clear overview if switch role is as well rendered (supported) as checkbox. Also it's not fully clear if screenreader users are as familiar with toggle switches as with checkboxes. I assume the switch role would imply a direct action in the interface like a light switch. Sadly our ToggleSwitches are not limited to these use cases in current implementation, they are used basically as checkboxes with a submit button further down in some views.
But let's go for the aspirational standard approach.
Change 623824 had a related patch set uploaded (by Jforrester; owner: Jforrester):
[mediawiki/core@master] Update OOUI to v0.40.3
Change 621711 abandoned by Reedy:
[mediawiki/core@master] Update OOUI to v0.40.2
Reason:
Replaced by https://gerrit.wikimedia.org/r/c/mediawiki/core/ /623824
@Aklapper Since "recently" we kept those tasks open until the next release of OOUI is merged into core, vendor and VE to openly clarify when folks can expect changes being visible on test environments and in production.