Skip to content
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

Calendar selecting disabled year/month (Accessibility) #14637

Closed
mristov opened this issue Jan 26, 2024 · 2 comments
Closed

Calendar selecting disabled year/month (Accessibility) #14637

mristov opened this issue Jan 26, 2024 · 2 comments
Labels
Component: Accessibility Issue or pull request is related to WCAG or ARIA Resolution: Stale Issue or pull request is inactivity and unfortunately it will be *closed* if there is no response

Comments

@mristov
Copy link

mristov commented Jan 26, 2024

Describe the bug

We can select disabled year or month via tab key even when is disabled (Accessibility)

Environment

Angular 17
PrimeNg 17.3.3

Reproducer

https://stackblitz.com/edit/sz4dye?file=src%2Fapp%2Fdemo%2Fcalendar-reactive-forms-demo.ts

Angular version

17.0.5

PrimeNG version

17.3.3

Build / Runtime

Angular CLI App

Language

TypeScript

Node version (for AoT issues node --version)

18.16.1

Browser(s)

No response

Steps to reproduce the behavior

In Stackblitz link we can clearly see that if we set maxDate
-> open p-datepicker-header
-> via click we can't click on disabled years, but if we press Tab key we can focus in disabled years and then with Space key or Enter key we can select it.
-> with selected disabled year we are opening months for that year, and again as part of Accessibility if we press Tab key focus is losing outside datepicker

This clearly cannot happen

The same scenario happens also and for selecting disabled months.

image image

Expected behavior

As we cannot click on disabled year/month, the same applies and for press Enter key or Space key over disabled.

@mristov mristov 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 26, 2024
@mehmetcetin01140 mehmetcetin01140 added Component: Accessibility Issue or pull request is related to WCAG or ARIA and removed Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible labels Feb 5, 2024
Copy link

github-actions bot commented Jun 5, 2024

This issue has been automatically marked as stale. If this issue is still affecting you with the latest version, please leave any comment, and we will keep it open. We are sorry that we have not been able to prioritize it yet. If you have any new additional information, please include it with your comment!

@github-actions github-actions bot added the Resolution: Stale Issue or pull request is inactivity and unfortunately it will be *closed* if there is no response label Jun 5, 2024
Copy link

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please create a new issue with up-to-date information. Thank you for your understanding!

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jun 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: Accessibility Issue or pull request is related to WCAG or ARIA Resolution: Stale Issue or pull request is inactivity and unfortunately it will be *closed* if there is no response
Projects
None yet
Development

No branches or pull requests

2 participants