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
We currently use an <i> tag for representing terms in YFM. This tag primarily serves stylistic purposes and doesn't fully convey the semantic meaning or interactive capabilities of the element and impacting accessibility.
The current role=term does not convey the interactivity of the element, role=button would work better in this case. And in order for the terms to be selectable from the keyboard, an tabindex has already been added what is the default behavior for the button.
Proposal
I propose that we refactor our term representation element to use more semantic and accessible HTML tag such as <button> for interactive elements that trigger actions.
We currently use an
<i>
tag for representing terms in YFM. This tag primarily serves stylistic purposes and doesn't fully convey the semantic meaning or interactive capabilities of the element and impacting accessibility.The current
role=term
does not convey the interactivity of the element,role=button
would work better in this case. And in order for the terms to be selectable from the keyboard, antabindex
has already been added what is the default behavior for the button.Proposal
I propose that we refactor our term representation element to use more semantic and accessible HTML tag such as
<button>
for interactive elements that trigger actions.Current:
Proposal:
The text was updated successfully, but these errors were encountered: