Specification status report for TPAC 2019

[LJWatson]

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]

• 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:
    Inconsistent name calculations for input elements #231, Editorial: Consider adding text to element mapping tables pointing to accessible name rules #227, output element is a labelable element #225, Order of "Submit Query" vs title attribute for <input type=image> #211, Clarify "Other form elements" #210, "Other form elements" doesn't say to use all associated label elements #209, Outline naming for contendediable elements #205, Is the documentation regarding the computation of name and description of tabular elements correct? #179, Consider prohibiting author naming certain elements #160, Add generic case for name calculation #158, Clarification sought regarding exposing title attribute via description when also part of name calculation #148, Name calculation for input type="file" not covered #134, name and description computation #100, HTML-AAM - test and update name calc for labelable elements #29, HTML-AAM: @title on <abbr> and <dfn> needs to be covered in name calculation #25, Whitespace alone should be ignored in accName algorithms #238
  • HTML element removal, updates and additions which would resolve:
    Add HTML elements #189, Remove/update menuitems and menu #188
  • Updating not mapped elements to indicate how they could map, if given attributes that are important for accessibility
    Need language/mapping for "not-mapped" elements which must be exposed due to attributes #151, Should var really be mapped to "No accessible object"? #143
  • Completion of attribute table for AX API
    AxAPI completion #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.

[marcoscaceres]

Thanks @scottaohara for writing up the summary early. You get extra points! 🌟

Leaving this open, as using this for TPAC meeting planning.

[LJWatson]

@marcoscaceres this is the status report from 2019. HTML AAM has been returned to the ARIA WG since then. @michael-n-cooper can we get this repo shifted over to the ARIA WG.

CC @jnurthen @joanmarie