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

Specification status report for TPAC 2019 #233

Closed
LJWatson opened this issue Aug 21, 2019 · 1 comment
Closed

Specification status report for TPAC 2019 #233

LJWatson opened this issue Aug 21, 2019 · 1 comment

Comments

@LJWatson
Copy link
Contributor

@LJWatson LJWatson commented Aug 21, 2019

Please can you respond to this comment with a brief specifications status report for the WebApps meeting at TPAC. The report should address the following:

  • 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?
  • What do you want to achieve for your spec in the next two days (of breakout sessions)?

We're tracking these status reports in WebApps issue #19

Thanks.

@scottaohara

This comment has been minimized.

Copy link
Member

@scottaohara scottaohara commented Sep 7, 2019

  • What progress has your spec made in the last 12 months?
    Further rounding out expectations for elements and attribute mappings. Working on rectifying and clarifying accessible name algorithms. Many pieces are still in progress, but I've identified much of what I think needs to be completed and worked towards to move to CR.

  • Is anything blocking your spec from moving to CR?
    Issues I want to resolve before CR. There is nothing blocking these beyond time and resources to write tests and update the spec accordingly. While I have been doing work to resolve a good majority of these issues, any assistance in writing tests and contributing to the following is appreciated:

    • Updated naming algorithms and general guidance, which would resolve:
      #231, #227, #225, #211, #210, #209, #205, #179, #160, #158, #148, #134, #100, #29, #25, #238
    • HTML element removal, updates and additions which would resolve:
      #189, #188
    • Updating not mapped elements to indicate how they could map, if given attributes that are important for accessibility
      #151, #143
    • Completion of attribute table for AX API
      #97
    • Complete or remove any notes in the specification that are marked as "to do"
  • What do you want to achieve for your spec in the next two days (of breakout sessions)?
    While I will not be able to attend TPAC, I'm hoping that any issues / solutions that may be discussed and are applicable to the HTML AAM will be logged and PRs will be submitted.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.