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
In the ACT test case below the ARIA label does go into the accessibility tree in Chrome and FF, so the accessible name is not empty. However, the developer may be confused because the alt="" was added in their source code, perhaps thinking it would mark the img as decorative, but it wasn't due to the alt attribute being ignored/overridden by the aria attribute because of the accessible name calculation spec for browsers.
However, the Checker should be a new warning or recommendation notifying the developer of the contradiction (this issue). The Checker should add a new fail reason code in the image_alt_null (rule source code).
philljenkins
changed the title
Add fail reason to img_alt_null for conflicts in attributes
ACT: Add fail reason to img_alt_null for conflicts in attributes and map to ACT rule 46ca7f
Aug 27, 2024
In the ACT test case below the ARIA label does go into the accessibility tree in Chrome and FF, so the
accessible name
is not empty. However, the developer may be confused because thealt=""
was added in their source code, perhaps thinking it would mark theimg
as decorative, but it wasn't due to thealt
attribute being ignored/overridden by thearia
attribute because of the accessible name calculation spec for browsers.However, the Checker should be a new warning or recommendation notifying the developer of the contradiction (this issue). The Checker should add a new fail reason code in the image_alt_null (rule source code).
There is another issue against ACT to clarify/ask why the Failed 2 above is a valid fail test case for ACT ruleID 46ca7f: Element marked as decorative is not exposed - see w3c/wcag-act-rules#295
The text was updated successfully, but these errors were encountered: