Fix DatePicker aria attributes #8180
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Storybook’s accessibility addon identifies problems with the PrimeVue Password component. When used inline, the component does not assign a role to its panel section, even though the section defines an aria-label. Because aria-label must always be associated with an explicit role, this omission results in an accessibility violation. Role application seems most applicable?
Another issue arises with the day elements, which set the aria-selected attribute without specifying a corresponding role. While assigning an option role initially seemed appropriate, that approach requires the parent element to have either a group or listbox role, both of which introduce further violations. The effective solution is to assign role="gridcell" to the daycell section. This aligns with the existing hierarchy, as the parent elements already use role="grid". Note that I also added role="row" to be more correct. The final step is to move the aria-selected attribute from the day section to the daycell section, ensuring it resides on an element that correctly defines a role.
Relevant issue: #8181