-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Why are <b> and <s> mapped to semantic roles, but <i> is not? #475
Comments
The answer is because I made a mistake :) |
@scottaohara Can you explain the reasoning for collapsing the semantics of |
I (and maybe Scott) argued for b and i to map to generic, but the ARIA WG went a different way. @michael-n-cooper @joanmarie or @jnurthen may be able to find the specific decision. They’d be interested to know that ARIA WG decision conflicts with the primary standard. |
just mentioning here that I've commented in the new issue that James created, so per anyone cc'd in the previous comment, may be worth reading that issue too. |
Closing the loop. The AAM change was rolled back with: The test change was rolled back with: |
Why are
<b>
and<s>
mapped to semantic roles (strong
anddeletion
), but<i>
isgeneric
?FWIW, I think all the style-based tags should be generic, but perhaps we can settle on consistency, one way or the other. Either
<i>
should beemphasis
, or<b>
and<s>
(maybe more) should begeneric
, right?The text was updated successfully, but these errors were encountered: