-
Notifications
You must be signed in to change notification settings - Fork 125
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
Editorial: Remove important terms from CORE-AAM #2293
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. |
443afd8
to
e9fc47f
Compare
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.
Since one of the two definitions ("activation behavior") was removed because it was never referenced, I'm curious if it would be valuable to summarize/include it elsewhere such as section 4.8 Events.
Or alternatively, since "accessible object" now links to the ARIA spec, should the ARIA activation behavior definition be linked as well rather than entirely removing it?
Thanks Rahim, for the thoughts/thoroughness! But there is no reference to anything like activation behavior in the events section, so from my perspective, there is no reason to include it. You got me curious about what that term was originally used for -- so I looked up the commit that added it: https://github.com/w3c/core-aam/pull/92/files @jnurthen -- you added the term |
There were only two important terms listed in CORE-AAM, and one of them had no references. The other was only used in one table, so I moved the definition to above the table.
https://deploy-preview-2293--wai-aria.netlify.app/core-aam