Agenda for F2F

[minorninth]

Web A11y API F2F

May 11 - 12, 2016 Google San Francisco 345 Spear St, San Francisco, CA 94105

Goal

Reach enough consensus to "go public" as either a working group or incubator group.

Day 1: Wednesday, May 11th, 2016

9:00 Meet at 345 Spear St, SF, 4th floor lobby, get badges, walk to meeting room. Continental breakfast and coffee will be in the meeting room.

9:30 Introductions

IRC channel: #web-a11y-api on irc.freenode.net Can use webchat.freenode.net to connect.

9:45 Demo of web accessibility API in Chrome

10:15 Brainstorming

• Concerns with technical details of current draft spec
• Title of spec and name of JS object
• Featured use cases
• Criteria for 1.0 inclusion

11:30 Breakouts

• Group 1: Technical spec, code snippets
• Group 2: Working group organization, criteria for inclusion, text of public announcement

12:30 Lunch @ Google

2:00 Breakouts

3:30 Summary of breakouts

4:30 Break / free time

6:00 Optional social dinner out (location TBD)

Day 2: Thursday May 12th, 2016

9:30-10:15: Basic and aspirational use cases

• Basic: must be supported in V1
• Aspirational: must not be ruled out from future revisions

10:15-11:00 Breakouts

11:00-11:20: Break

11:20-12:30: Review API

• Name of API
• Name of object
• Line by line consensus

12:30: Lunch @ Google

2:00: Next steps

• Action items
• Whether to go public (yes / no)
• Spec editors
• Title of spec and name of JS object
• Featured use cases
• Criteria for 1.0 inclusion
• Text of public announcement

3:30 Adjourn

[minorninth]

For brainstorming:

• What to return as roles for objects that don't have an ARIA equivalent, like

  , , or

  ? A generic role like "group", or "-internal-paragraph" or something like that?

[minorninth]

For final vote: Incubator group Y/N

[minorninth]

Meeting notes / minutes?

[minorninth]

Can we fix :before, :after generated content

[minorninth]

Talk about things like element needing more customization for web developers, so they're not forced to reinvent the wheel - BUT - being web developers will always push the boundaries, so this low-level accessibility API is needed so that accessibility isn't left behind as people innovate

alice commented 8 years ago

Use cases?

alice commented 8 years ago

Whether to go public Not immediately.

Where to go public (eventually) WICG

Spec editors See spec draft.

Title of spec and name of JS object

• Accessibility Object Model
• AccessibleNode

Featured use cases See https://github.com/a11y-api/a11y-api/wiki/Use-cases

Criteria for 1.0 inclusion AI: James (chat w @cyns) Implementation interest from two implementors (browser vendors)

Text of public announcement TBD

Action items

• Scoping Wiki page (editor-only access) - @cookiecrook
  • 1.0
  • philosophical
  • provide a use case with sample code
• Gating criteria for going public - @cookiecrook
  • Privacy
  • IDL draft with ~consensus
  • Scoping criteria
• Share draft spec with trusted advisors - everyone
  • Test implementations
  • Send patch and binary to group - @minorninth
• Trim down IDL as discussed - @minorninth @asurkov ?
• Create a list @minorninth
  • private Google group
• Define privacy permissions?
• Text of public announcement - TBD
  • First thing to be available publicly

Open questions Security and privacy Events Additive behaviours Whether to include poorly implemented ARIA concepts e.g. aria-owns

Next steps AIs Next teleconference: May 27 - progress check-in. Set deadlines for review of work - silence implies assent.

• © Githubissues.
• Githubissues is a development platform for aggregating issues.

[alice]

Use cases?

[alice]

Whether to go public Not immediately.

Where to go public (eventually) WICG

Spec editors See spec draft.

Title of spec and name of JS object

• Accessibility Object Model
• AccessibleNode

Featured use cases See https://github.com/a11y-api/a11y-api/wiki/Use-cases

Criteria for 1.0 inclusion AI: James (chat w @cyns) Implementation interest from two implementors (browser vendors)

Text of public announcement TBD

Action items

• Scoping Wiki page (editor-only access) - @cookiecrook
  • 1.0
  • philosophical
  • provide a use case with sample code
• Gating criteria for going public - @cookiecrook
  • Privacy
  • IDL draft with ~consensus
  • Scoping criteria
• Share draft spec with trusted advisors - everyone
  • Test implementations
  • Send patch and binary to group - @minorninth
• Trim down IDL as discussed - @minorninth @asurkov ?
• Create a list @minorninth
  • private Google group
• Define privacy permissions?
• Text of public announcement - TBD
  • First thing to be available publicly

Open questions Security and privacy Events Additive behaviours Whether to include poorly implemented ARIA concepts e.g. aria-owns

Next steps AIs Next teleconference: May 27 - progress check-in. Set deadlines for review of work - silence implies assent.