Optimization (accessibility): Elements with an ARIA [role] that require children

[rfultz]

Background

Looking to optimize the site's performance and that of the homepage specifically, the Lighthouse tool in Chromium browsers has made some suggestions. Some of these will have repercussions throughout the app so we're going to make them their own tickets.

Accessibility Recommendation: Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. details

Overview

The WCCF widget needs its aria-role values fixed, specifically the required parent-child relationships. ("row" doesn't have to be in a table but it is required to have certain children)

Benefit (the 80 of 80/20)

Will help aria readers access table data

Effort (the 20 of 80/20)

Minimal

Complications

• Unknown
• Make sure major browsers aren't negatively impacted by any of these changes (Chrome, Safari, Firefox. IE?)

Related tickets

• Preload key requests
• Remove unused JavaScript
• Remove unused CSS
• Preconnect to required origins
• Eliminate render-blocking resources
• Ensure text remains visible during webfont load
• Reduce the impact of third-party code
• Does not use passive listeners to improve scrolling performance
• Image elements do not have explicit width and height
• Serve static assets with an efficient cache policy
• Minimize main-thread work
• Avoid an excessive DOM size
• Reduce JavaScript execution time
• Avoid enormous network payloads
• [aria-hidden="true"] elements contain focusable descendents
• [aria-*] attributes do not have valid values
• ARIA IDs are not unique
• Lists do not contain only
• elements and script supporting elements (<script> and )
• [user-scalable="no"] is used in the element or the [maximum-scale] attribute is less than 5
• Links to cross-origin destinations are unsafe
• Serves images with low resolution