Skip to content

[OUDS] add readonly state on Checkbox/Radio/Switch components #2950

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
2 tasks done
MaxLardenois opened this issue Apr 4, 2025 · 2 comments · May be fixed by #2951
Open
2 tasks done

[OUDS] add readonly state on Checkbox/Radio/Switch components #2950

MaxLardenois opened this issue Apr 4, 2025 · 2 comments · May be fixed by #2951
Labels
🗳️ feature
Milestone
OUDS v1

Comments

@MaxLardenois
Copy link
Collaborator

Prerequisites

Proposal

Add the Readonly state on Checkbox, Radio button and Switch as specified in the Figma

Motivation and context

This state was not implemented as it necessitated some work on a11y side
@MaxLardenois MaxLardenois added this to the OUDS v1 milestone Apr 4, 2025
@MaxLardenois MaxLardenois linked a pull request Apr 4, 2025 that will close this issue
Draft
16 tasks
@MaxLardenois MaxLardenois linked a pull request Apr 4, 2025 that will close this issue
[OUDS] Add readonly on control item components #2951
Draft
16 tasks
@Aniort
Copy link
Contributor

Aniort commented Apr 7, 2025

hello,
we should be precise that disabled components (radio, check, switch must be used for non-informative elements where the user doesn't need them and their status (disabled) to complete the task. And read-only elements should be the ones that convey information, because they and their status are essential to understanding the page and the task to be accomplished..

@MaxLardenois
Copy link
Collaborator Author

hello, we should be precise that disabled components (radio, check, switch must be used for non-informative elements where the user doesn't need them and their status (disabled) to complete the task. And read-only elements should be the ones that convey information, because they and their status are essential to understanding the page and the task to be accomplished..

Agreed, but I think this should mainly be in the guidelines for these components, we could still have a note on this in OUDS Web documentation. What do you think @MaximeTonnerre?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
🗳️ feature
Projects
None yet
Milestone
OUDS v1
2 participants
@Aniort @MaxLardenois