– DRAFT –
ARIA Authoring Practices Task Force

Meeting frequency, roadmap, and agenda planning

<Jemma> Discuss agenda planning strategy:

<Jemma> How to ensure meetings help move most important work forward

<Jemma> When to make time to discuss how to work better, improve task force health, etc.

<Jemma> How to better balance between detailed discussions of design and code vs prioritization and coordination of work

<Jemma> Discuss priorities:

<Jemma> Quality of current content vs new content

<Jemma> PR burndown

<Jemma> Issue burndown

<Jemma> Redesign and aria-at data integration

<Jemma> Ways of increasing velocity:

<Jemma> Growing membership (possibly through community group)

<Jemma> Improving how we work

<Jemma> Contracted contributors (Bocoup)

<Jemma> car: would you ask bocoup to review some of issue?

<Jemma> mck: example can be opininated.. consensus driven is important for taskforce.

<Jemma> mck: we should not contract out core missions

<Jemma> jongund: how about managing "mobile compatibility" for example?

<Jemma> car: we can say like

<Jemma> ....

<Jemma> mck: we may need to work others like EO

<Jemma> mck: I am proposing 2/15 kick off meeting with bocoup, 90min meeeting

<Jemma> meetingn on Feb 16

<Jemma> mck:Matt discusss the idea of converting TF to community group

<Jemma> car: slider example has challenge because there is missing API.

<Jemma> siri: all examples should work for mobile.

<siri> They are using <input type="range"...>

<siri> https://getbootstrap.com/docs/4.1/components/forms/

<Jemma> jon: any documentation for mobile support?

<Jemma> mck: there is mobile support under "important notes" for each example.

<Jemma> car: my proposal is to add red and visibvle note - the example which is problematic for mobile.

<siri> +1

<Jemma> jon: we need to figure out what we are going to do common problems for the slider example like a separate meeting.

<Jemma> car: it can be like ARIA deep dive meeting.

<Jemma> mck: I am open to that idea - small group discussion to resolve the pending issues.

<Jemma> and come back to APG to get approval.

<Jemma> mck: how do we operationalize that?

<Jemma> jon: I am willing to recruite people and invite them to example discussion.

<Jemma> ... I can be charge of that particular work.

<siri> +1

<Jemma> mck: can name be the focus group or name of example group?

<Jemma> r

Resolution: Jon will lead the focus group meeting for each APG example.

<Jemma> Mck: Matt will send out 90min meeting annoucement with Bocoup

PR burndown

<Jemma> https://github.com/w3c/aria-practices/pull/1699

mck: need people to look at this PR. Seems good to me. External people are waiting on it.

<Jemma> jon and carmacleod will reivew issue 1699 before the final merge.

<Jemma> mck: it will be great to be done before this week so that I can merge

mck: will merge with 2 approving reviews

jongund: Question: for a spinbutton, which is similar to slider, it was ok to use buttons on mobile. But not ok to use on slider?

mck: since we're going to go in the direction of using html inputs, etc, soon, why don't we just start now?

mck: create a separate example, keep the warning notes, show how to use html range input?

mck: document how we're using it?

jemma: is that beyond scope of apg?

jongund: it won't show up in the list of examples because no use of aria, but we can force that...

mck: thing is, we are planning to increase our scope

mck: need to be careful about "different groups giving different guidance for the same things"

mck: but since we are going to consolidate, maybe that's ok

mck: or maybe we're just getting ahead of ourselves?

<Jemma> jemma: my concern is that each taskforce explain the same point differently and users have a burden of cross checking which one is correct one.

<Jemma> that is why APG is focusing on APG first, rather than html examples

<Jemma> mck: navigation tree view was merged

<jongund> https://raw.githack.com/w3c/aria-practices/update-menubar-nav/examples/menubar/menubar-navigation.html

https://github.com/w3c/aria-practices/pull/1612

mck: there are some conflicts

mck: some of the wording around high contrast, focus staying on menubar

mck: I think we can get this one done this week

jemma: I think 1614 is ready for review

https://github.com/w3c/aria-practices/pull/1614

<Jemma> summary of meeting

mck: Moving to weekly meetings, next call is Feb 2

<Jemma> 1) going weekly meeting

<Jemma> 2)slider example meeting

<Jemma> 3) kick off meeting on feb/26