-
Notifications
You must be signed in to change notification settings - Fork 124
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
Remove Core-AAM UA requirement to disallow orphaned role context. #2284
base: main
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for wai-aria ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd like to understand the exceptions a bit better!
<div role="list"> <!-- computedrole returns "list" --> | ||
<div role="listitem"> <!-- computedrole returns "listitem" in the required context. --></pre | ||
> | ||
<pre><div role="listitem"> <!-- Author error: orphaned listitem. computedrole is unspecified. --></pre> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually, I think I should keep the second example.
<pre><div role="listitem"> <!-- Author error: orphaned listitem. computedrole is unspecified. --></pre> | |
<pre> | |
<div role="listitem"> <!-- Author error: orphaned listitem. computedrole is unspecified. --> | |
<div role="list"> <!-- computedrole returns "list" --> | |
<div role="listitem"> <!-- computedrole returns "listitem" in the appropriate context. --></pre> |
in scenarios deemed by the implementation to be harmless. This unspecified permissiveness in how engines treat author role usage errors is occasionally overridden for a specific role in | ||
other specs such as [[HTML-AAM]]. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
in scenarios deemed by the implementation to be harmless. This unspecified permissiveness in how engines treat author role usage errors is occasionally overridden for a specific role in | |
other specs such as [[HTML-AAM]]. | |
in scenarios deemed by the implementation to be harmless. Please note that this permissiveness in how engines treat author role errors might be overridden in a language-specific mapping document such as [[HTML-AAM]]. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@spectranaut The Prettier bot broke the thread (because of the line breaks it needlessly added) but this is in response to your feedback suggestion.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, this seems better to me!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approval with the change to list html-aam specifically
in scenarios deemed by the implementation to be harmless. This unspecified permissiveness in how engines treat author role usage errors is occasionally overridden for a specific role in | ||
other specs such as [[HTML-AAM]]. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, this seems better to me!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm when the suggested changes are merged in
@cookiecrook if you include your proposed changes I will land! |
Remove Core-AAM UA requirement to disallow orphaned role context.
Closes #2166