False positive for use of new-ish aria-description attribute - supported in all major browsers

[scottaohara]

One of the new features being added to ARIA 1.3 - the aria-description attribute allows authors to provide an element a description, similar to now aria-label allows authors to provide an element a name.

Added to the editor's draft in 2020, aria-description has been implemented in all browsers for quite awhile now. it'd be nice if the equal access checker no longer reported its use as a violation due to being an invalid attribute.

thanks!

Definition of Done

• Design artifacts reviewed
• Work item implemented
• Automated test case created (when applicable)
• Unit test completed
• Run Checker (when applicable)
• Manual and Screen Reader Testing (when applicable)
• Video recording of user experience walkthrough (if impact to UX)
• PR created

[tombrunet]

Just to be clear - this isn't part of the latest recommendation yet (ARIA 1.2). Due to end of year vacations, we probably won't be able to discuss this as a team for a couple of weeks.

[tombrunet]

Removing the label of false positive since it isn't a false positive by spec. More of a question of timing of draft spec features.

[scottaohara]

Correct, it is not a false positive going by the ARIA 1.2 Recommendation. If this product is only going by published recommendations, then can definitely understand your pov on this.

It can be interpreted as a false positive by people using the product that know the feature is supported, but they are getting violations anyway. As an FYI - ARIA is moving towards becoming an evergreen / living standard spec, much like HTML, ARIA in HTML and the AAM specs. Right now, features being added to ARIA 1.3 need implementations / commitments to even be merged into the spec. Again, just so you know for the pending discussion on this.

Thanks