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
Now, per WAI-ARIA Graphics Module specs, role="graphics-document" requires acc name. Moreover, SVG AAM set the default platform WAI-ARIA role mappings to "graphics-document" and ARIA in HTML maps the element to role="graphics-document".
Web authors expect svg not to be exposed by default; but if authors have to follow current specs, they are forced to either set an accessible name, or role=none to each svg element, even if the svg doesn't convey any information.
Moreover, different AT don't expose the svg element to the user unless it has an acc name, ignoring the browsers computed role; browsers are exposing svg elements differently (see last WPT test).
The Passed Example 4 currently creates accessibility failures (1.1.1) as browsers that expose the svg as an image cause the svg to be exposed as an image with no acc name.
Moreover, the applicability, IMO, is wrong anyway, since now, it's against specs, and if specs will be updated marking as presentational svg elements without acc name, is no longer needed.
As ACT group, we need to understand what to do.
In the meantime, I've opened an issue for ARIA specs: w3c/aria#2427
The text was updated successfully, but these errors were encountered:
Image not in the accessibility tree is decorative has the following applicability:
and the following Passed Example 4:
Now, per WAI-ARIA Graphics Module specs, role="graphics-document" requires acc name. Moreover, SVG AAM set the default platform WAI-ARIA role mappings to "graphics-document" and ARIA in HTML maps the element to role="graphics-document".
Web authors expect svg not to be exposed by default; but if authors have to follow current specs, they are forced to either set an accessible name, or role=none to each svg element, even if the svg doesn't convey any information.
Moreover, different AT don't expose the svg element to the user unless it has an acc name, ignoring the browsers computed role; browsers are exposing svg elements differently (see last WPT test).
The Passed Example 4 currently creates accessibility failures (1.1.1) as browsers that expose the
svg
as an image cause thesvg
to be exposed as an image with no acc name.Moreover, the applicability, IMO, is wrong anyway, since now, it's against specs, and if specs will be updated marking as presentational svg elements without acc name, is no longer needed.
As ACT group, we need to understand what to do.
In the meantime, I've opened an issue for ARIA specs: w3c/aria#2427
The text was updated successfully, but these errors were encountered: