You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When axe encounters ARIA that is valid but not recommended / deprecated, we currently either pass it or (for deprecated attributes, after #3341) mark it as needs-review by wiring a bespoke check into a rule. There is no general, data-driven way in lib/standards to say "this role/attribute is valid but should return needs-review."
Per @WilcoFiers and Steven Lambert's comments: we should consider adding standards support that lets axe return needs-review for not-recommended-but-valid roles and attributes, rather than each case being handled ad hoc.
Ask
Design a standards-level signal (e.g. a deprecated / notRecommended flag consumed uniformly) that maps to a needs-review outcome for the relevant rule(s).
Follow-up from the discussion on #3341.
When axe encounters ARIA that is valid but not recommended / deprecated, we currently either pass it or (for deprecated attributes, after #3341) mark it as needs-review by wiring a bespoke check into a rule. There is no general, data-driven way in
lib/standardsto say "this role/attribute is valid but should return needs-review."Per @WilcoFiers and Steven Lambert's comments: we should consider adding standards support that lets axe return needs-review for not-recommended-but-valid roles and attributes, rather than each case being handled ad hoc.
Ask
deprecated/notRecommendedflag consumed uniformly) that maps to a needs-review outcome for the relevant rule(s).aria-deprecated-attrcheck added in Indicate that aria-grabbed and aria-dropeffect are deprecated #3341) onto it where it makes sense.This is a design/enhancement ticket, not a spec-data change.
Related: #3341