Facing accessibility-related issues with primeNg controls and AXE tools.

Post Reply
nandam
Posts: 2
Joined: 01 Dec 2020, 07:45

07 Jan 2021, 13:54

We are facing issue with below controls in execution of Axe tool, ARIA label property is not getting added though we specified "ariaLabelledBy", due to that Axe tool shows it as WCAG non compliance. Need help in resolving it.


1. Dropdown
a. Ensures every ARIA button, link and menuitem has an accessible name
b. Ensures elements with an ARIA role that require child roles contain them
c. Ensures role attribute has an appropriate value for the element

2. Radiobutton
a. Ensures every ARIA toggle field has an accessible name

3. Checkbox
a. Ensures every ARIA toggle field has an accessible name

merve7
Posts: 808
Joined: 12 Sep 2017, 10:44

08 Jan 2021, 13:30

Hi,
@yigitfindikli Could you please check this issue?

Best regards,

nandam
Posts: 2
Joined: 01 Dec 2020, 07:45

19 Jan 2021, 04:52

Hi,
Can you let us know, if we need to take care anything?

mert.sincan
Posts: 4765
Joined: 29 Jun 2013, 12:38

21 Jan 2021, 12:04

Hi,

This issue is related to PrimeNG core. Could you please create a github issue for these?

Best Regards,

yigitfindikli
Posts: 419
Joined: 08 Aug 2018, 14:09

01 Feb 2021, 13:21

Added for next milestone. Thanks for the GitHub ticket.

Regards.

pankaj1106
Posts: 3
Joined: 30 Aug 2021, 06:11

01 Sep 2021, 06:53

Hi Prime NG Team,

We are using Prime NG drop downs with Angular 11 and facing the same issues:
1. Ensures every ARIA button, link and menu item has an accessible name
2. Ensures every form element has a label

Please let me know if you have any update on this.

Thanks
Pankaj

Post Reply

Return to “Serenity - PrimeNG”

  • Information
  • Who is online

    Users browsing this forum: No registered users and 1 guest