- Status changed to RTBC
over 1 year ago 2:00am 21 January 2023 - Status changed to Needs work
over 1 year ago 12:08pm 21 January 2023 - 🇨🇦Canada mgifford Ottawa, Ontario
@xjm I don't think we need to backport issues that fall under WCAG SC 4.1.1. There's a big debate about removing it from WCAG 2.2, so it may not be in WCAG's future.
The thing is that most parsing errors aren't a problem for accessibility. When 4.1.1 was written, there was some assistive technology that worked with HTML source code. Now they all use the DOM or Accessibility Tree, both of which have been cleaned up by the browser.
So we're an organization that supports open standards, so it is good to fix parsing errors, but it may not make sense to see them as accessibility issues.
I tagged this with WCAG SC 4.1.2 Name, Role, Value.
Redundancy isn't good, but not sure if it needs backporting. It's a pretty low impact issue.
I have to say I also had trouble finding this reference "Where to find it in WCAG 2: 4 Robust > 4.1 Compatible > A > 4.1.2 Name, Role, Value > Warning > Redundant WAI-ARIA attribute" from the project descrption. Not sure why a link wasn't given.
- 🇩🇪Germany mrshowerman Munich
Re-roll against current 10.1.x. Leaving in NW as per #34.
- 🇺🇸United States bnjmnm Ann Arbor, MI
Tagging for accessibility maintainer review of whether it is okay to backport this to 10.0.x and 9.5.x. I considered FEFM signoff, but in this case I think the accessibility aspect is the main thing that's important.
It is OK to backport this change to 10.0.x and 9.5.x, but as mentioned in in #44 it is also not imperative that this happens.
- Merge request !8514Issue #3096790: aria-required attribute is redundant when required attribute is present → (Open) created by mrshowerman
- 🇸🇪Sweden Mohammed Motar
I have created a patch file from the latest commit in the merge request.