Skip to content
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

Closed
LJWatson opened this issue Jun 17, 2021 · 8 comments
Closed

CFC: transition Aria in HTML to CR #326

LJWatson opened this issue Jun 17, 2021 · 8 comments

Comments

@LJWatson
Copy link

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.

@LJWatson
Copy link
Author

Ping @scottaohara, @stevefaulkner, @patrickhlauke, and @marcoscaceres.

@scottaohara
Copy link
Member

note: additional HTML Validator updates have reduced the at risk features list by two items

@marcoscaceres
Copy link
Member

Given that now all engines handle case insensitive matching, I'd still like to see issue #280 addressed and #287 merged.

@scottaohara
Copy link
Member

I have commented on #287

@scottaohara
Copy link
Member

As of today, the number of features at risk is now 9

@scottaohara
Copy link
Member

As of today, the number of features at risk is now 1

@LJWatson
Copy link
Author

With thanks to everyone who responded, this CFC passes with multiple expressions of support and no objections.

@scottaohara
Copy link
Member

Update: number of features at risk is now zero.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants