-
Notifications
You must be signed in to change notification settings - Fork 355
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
Guidelines for aria-level attribute #1003
Guidelines for aria-level attribute #1003
Conversation
@spectranaut, should we close this PR and replace it with one from the aria-level branch? I didn't compare this bocoup:aria-level branch to the w3c:aria-level branch, but I do see you committed to w3c:aria-level on June 26. So, I am guessing the one in the w3c repo is actually the latest work? |
I just compared and actually bocoup:aria-level has two more commits than w3c:aria-level (they are otherwise identical) -- I might have accidentally pushed to w3c:aria-level instead of bocoup:aria-level once. I'm going to delete the branch on w3c to avoid confusion in the future! |
I prefer to work on a branch in the w3c repo. I will make a new one and land this work there. |
@spectranaut, could you please create a new PR with a compare branch of issue259-aria-level-guidance and base branch of master? |
sure thing :) |
Initial draft of content for issue #259 to provide a guidance section on aria-level.
Initial draft of content for issue #259 to provide a guidance section on aria-level.
Initial draft of content for issue #259 to provide a guidance section on aria-level.
Initial draft of content for issue #259 to provide a guidance section on aria-level.
Initial draft of content for issue #259 to provide a guidance section on aria-level.
Rendered
Including this open issue on ARIA: w3c/aria#915
@zcorpan
Preview | Diff