Re: ARIA TPAC Meeting to discuss Javascript Accessibility API

Echoing Dominic's response here:

If you have general questions, a reply to the thread is sufficient, or compile the list for an ARIA or TPAC follow-up.

If you have specific technical concerns or edits, use the GitHub issue list. Please scan the existing issues (only a few dozen at the moment) to see if your comment has been raised already.

If you have a proposed feature or enhancement request, please read the inclusion criteria for the 1.0 release. 
http://a11y-api.github.io/a11y-api/spec/#inclusion


> On Aug 29, 2016, at 11:04 PM, Dominic Mazzoni <dmazzoni@google.com> wrote:
> 
> Stefan,
> 
> Everyone who contributed is on this email so your'e welcome to raise any questions and caveats here, alternative please file a bug on GitHub: https://github.com/a11y-api/a11y-api/issues <https://github.com/a11y-api/a11y-api/issues>
> 
> Also, please see the explainer <https://github.com/a11y-api/a11y-api/blob/master/explainer.md> we're in the process of writing - it wasn't linked from the main spec last week so you may not have seen it, but it may help to answer many questions about why we've designed it the way we have.
> 
> - Dominic
> 
> 
> On Mon, Aug 29, 2016 at 11:00 PM Schnabel, Stefan <stefan.schnabel@sap.com <mailto:stefan.schnabel@sap.com>> wrote:
> Hi James,
> 
> we'd like to give some feedback for http://a11y-api.github.io/a11y-api/spec/ <http://a11y-api.github.io/a11y-api/spec/> since we feel it offers very much but has some caveats and raises also questions.
> 
> What is the appropriate place for this?
> 
> Best Regards
> Stefan
> 
> Sent from my iPad
> 
> On 30.08.2016, at 06:16, James Craig <jcraig@apple.com <mailto:jcraig@apple.com>> wrote:
> 
>> Hi Rich (copying the other AOM contributors and Dave Singer),
>> 
>> If by "Java Script Accessibility API", you mean the work-in-progress Accessibility Object Model spec <http://a11y-api.github.io/a11y-api/spec/>, can we move the discussion to ARIA's TPAC agenda for Thursday? 
>> 
>> I'll be attending the Web Platform meetings on Monday the 19th (for Web Components) and Friday the 23rd (for HTML, Platform Tests, etc). CSS on Tuesday the 20th. I proposed a Technical Plenary breakout on Wednesday the 21st to discuss AOM.
>> 
>> Dominic works for a member org, so he can register as an observer to any group with the Chair's permission. No need to join the Working Group unless he wants to for other reasons. I believe Alice Boxhall from Google is planning to attend TPAC as well.
>> 
>> I addressed some of the AOM concerns you raised in this GitHub comment:
>> https://github.com/w3c/webcomponents/issues/553#issuecomment-243314488 <https://github.com/w3c/webcomponents/issues/553#issuecomment-243314488>
>> 
>> From that and other threads it seems like there is a lot of confusion regarding AOM. Some of it would be addressed by reading the spec, contribution documents, and my comments on the GitHub thread above. I'm also happy to give a summary in one of the ARIA calls before TPAC if you like. This week is probably too soon, as we're waiting to hear back from Cynthia and Bogdan on Microsoft's continued involvement. Once Dominic has sent the spec contribution to the WICG list, all feedback is welcome.
>> 
>> Cheers,
>> James Craig
>> 
>> 
>>> On Aug 29, 2016, at 11:45 AM, Rich Schwerdtfeger <richschwer@gmail.com <mailto:richschwer@gmail.com>> wrote:
>>> 
>>> Hi Dominic,
>>> 
>>> I wanted to make you aware of a discussion we will be having at TPAC regarding extensibility, web components, ARIA and a Java Script Accessibility API. We will be discussing your API work on Friday: https://www.w3.org/WAI/ARIA/wiki/Meetings/TPAC_2016 <https://www.w3.org/WAI/ARIA/wiki/Meetings/TPAC_2016>. We would love to have you there at TPAC. I think you would need to join either the Web Platforms working group or the ARIA working group to attend. 
>>> 
>>> Chris, you are most welcome to come and you have done such great work on webkit accessibility. I am working for the ARIA Working Group to meet with Web components earlier in the week.
>>> 
>>> Best,
>>> Rich
>>> 
>>> 
>>> Rich Schwerdtfeger
>>> 
>>> 
>>