dequelabs
Relegate Internet Explorer (IE) accessibility supported issues to best practices
At some point we need to stop support for IE. We should make a decision on how we do this and when we can make this sort of change.
I propose that we relegate the m to best practices and I propose that we do this in a normal point release
I was thinking to do it as part of 5.0, somewhere Q1 2023.
This is actually a fairly substantial bit of work. There are two things axe-core currently assumes about the page that it can't assume anymore once we stop flagging IE issues as violations;
- no fallback roles,
- and no css
content.
Axe-core currently assumes fallback roles are never used and just fails elements that have them. We'll have to change that. I'm not fully sure I know how yet either. We'll probably need something like #1350 and/or #2864 so that we can select based on an element's actual role. We may also want to explore the possibility of some rules applying multiple requirements based on each valid fallback role. For example, what are the allowed attributes on role="spinbutton button"? Should that use the attributes of spinbutton? Should we allow this element to have attributes allowed for either spinbutton or button? Or even should we only permit attributes that are valid on both roles? We'll have to go through the entire code base and tease that out.
The second one is that we need to add CSS content to the accessible name computation. That's not too complicated, but it'll be slow. We'll probably need caching to make that work well.
