TPAC planning and specification status report

[LJWatson]

TPAC will be virtual this year. W3C is finalising the details but it is likely there will be events for the whole W3C community during the week of 26 to 31 October (as originally planned), with WG able to organise their own meetings in/around that week.

There are two things we need you to do:

1. Let @marcoscaceres and I know before 17 July if you want meeting time to talk about your specification.
2. Post a specification status report before 30 September.

The specification status report should include:

• What progress has your spec made in the last 12 months?
• Is anything blocking your spec from moving to CR?
• If yes, what is your plan to unblock it and do you need any help?

Your specification status report from 2019 is at #160

[stevefaulkner]

What progress has your spec made in the last 12 months?

The specification has continued to be developed and refined. We have worked closely with the maintainer of the W3C validator to ensure that the normative assertions expressed in the specification are expressed in the w3c validator output.

Is anything blocking your spec from moving to CR?

We need a second implementation

If yes, what is your plan to unblock it and do you need any help?

We are working with the developers of the ARC toolkit chrome extension to incorporate functionality that tests and produces results based on ARIA in HTML normative rules. We believe this will satisfy the requirement for a second implementation which will allow the spec to move to CR. We don't need help with this.

[scottaohara]

Additional note:
Thanks to efforts by @carmacleod, the HTML Living Standard references this specification as "accessibility considerations for authors" from each HTML element.