-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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.
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
Mouse icon: No change possible on disabled state #14522
Comments
msg-ptavoul
added
the
Status: Needs Triage
Issue will be reviewed by Core Team and a relevant label will be added as soon as possible
label
Jan 10, 2024
cetincakiroglu
added
Status: Discussion
Issue or pull request needs to be discussed by Core Team
and removed
Status: Needs Triage
Issue will be reviewed by Core Team and a relevant label will be added as soon as possible
labels
Jan 10, 2024
mertsincan
removed
the
Status: Discussion
Issue or pull request needs to be discussed by Core Team
label
Jan 16, 2024
Hi, We wrap .p-disabled class with @layer primeng to customize easily. Please try the following css;
Best Regards, |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Old Bug:
#1385
The need to use a different mouseicon for the "disabled" state in german and also in european-government applications is mandatory. Via EU Laws the different States are forced to implement the rules of accessibility. For this example the Rules "1.4.1 Use of Color" and "1.4.11 Non-text contrast" of the WCAG 2.1 come to frution. The Rules are also implemented in the DIN EN 301549 v3.1.1.
This means the colorchange as primary and only option to differ is not sufficient. A button needs the option with other characteristics (like the mousicon) to show a different state (in this case: disabled).
The Change would further enable PrimeNGs as a suitable framework for the public sector.
Environment
Windows 11
Reproducer
No response
Angular version
17.0.8
PrimeNG version
17.3.0
Build / Runtime
Angular CLI App
Language
TypeScript
Node version (for AoT issues node --version)
20.9.0
Browser(s)
Chrome 119.0.6045.200
Steps to reproduce the behavior
No response
Expected behavior
No response
The text was updated successfully, but these errors were encountered: