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
Let's consider a case when we have some technical iframe on the page (e.g. collect some user actions). According to a11y rules we will add aria-hidden=true to hide it from assistive techs and tabIndex=-1 to exclude it from keyboard access.
In this case eslint plugin still requires title attribute but it seems to be redundant.
Please let me know, what do you think about this case :)
The text was updated successfully, but these errors were encountered:
Why would aria-hidden mean a user wouldn’t be able to hover their mouse cursor over it?
Good question, btw. Since aria-hidden means that we do not want iframe to be interactable for screen readers, I don’t think it’s a good idea to force any accessibility attributes on it. Don’t you think so?
Title for an element that is hidden from assistive techs seems to be redundant
People navigating with assistive technology such as a screen reader can use the title attribute on an <iframe> to label its content
Negative tabIndex or inert is required for consistency because:
aria-hidden="true" should not be used on elements that can receive focus. Additionally, since this attribute is inherited by an element's children, it should not be added onto the parent or ancestor of a focusable element
Hey!
Let's consider a case when we have some technical iframe on the page (e.g. collect some user actions). According to a11y rules we will add
aria-hidden=true
to hide it from assistive techs andtabIndex=-1
to exclude it from keyboard access.In this case eslint plugin still requires
title
attribute but it seems to be redundant.Please let me know, what do you think about this case :)
The text was updated successfully, but these errors were encountered: