-
Notifications
You must be signed in to change notification settings - Fork 49
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
CFC: transition Aria in HTML to CR #326
Comments
Ping @scottaohara, @stevefaulkner, @patrickhlauke, and @marcoscaceres. |
note: additional HTML Validator updates have reduced the at risk features list by two items |
I have commented on #287 |
As of today, the number of features at risk is now 9 |
As of today, the number of features at risk is now 1 |
With thanks to everyone who responded, this CFC passes with multiple expressions of support and no objections. |
Update: number of features at risk is now zero. |
This is a Call For Consensus (CFC) to transition ARIA in HTML to Candidate Recommendation (CR).
The results of the most recent horizontal review were tracked in #273, and there are no outstanding issues.
An implementation report is also available. All but 14 features have at least two implementations, and those 14 are noted as being "at risk" should the implementations not happen before we exit CR.
If you support this proposal, please add a "thumbs up" reaction to this comment.
If you do not support the proposal, please add a "thumbs down" reaction to this comment instead, and post a comment with your reasons.
If you do not respond to this CFC at all, W3C convention regards it as implicit support for the proposal. It is therefore much better if you respond directly.
Please respond to this CFC by the end of your day on Friday 25 July 2021. Thank you.
The text was updated successfully, but these errors were encountered: