Editing incorrectly applied Accessible Rich Internet Applications (ARIA) attributes

Helen O'Donnell - NHS Business Services Authority

Accessible Rich Internet Applications (ARIA) attributes have been assigned by default Oracle Analytics Cloud functionality.

As they are ARIA labels instead of html elements, they are read out loud by Screen readers, creating the effect of reading titles twice or be flagged by Wave. Please see below for more details:

Some pages contain an Accessible Rich Internet Applications (ARIA) attribute that has not been applied correctly which makes using assistive technology difficult. This fails WCAG 2.2 success criteria 1.1.1 (Non-text Content), 1.3.1 (Info and Relationships), 2.4.6 (Headings and Labels), 4.1.2 (Name, Role, Value) and 2.5.3 (Label in Name). 

Axe example: 

Certain ARIA roles must contain particular children. Element has children which are not allowed: table[tabindex]. <div role=”tablist”>. 

Certain Aria roles must be contained by particular parents. Element Location: h[role="menuitem"]. Required ARIA parents role not present: menu, menubar, group. 

 

Lighthouse flag: 

Uses ARIA roles on incompatible elements. Many HTML elements can only be assigned certain ARIA roles. Using ARIA roles where they are not allowed can interfere with the accessibility of the web page.