ARIA Editors -- 06 Apr 2016

<scribe> scribe: MichaelC

Finishing current round of publications

Graphics roles

Timeline for next round of publications

pseudo-LC of ARIA in June?

(ordinary WD but feature complete, for review before CR)

still need to close password, combobox, ...

waiting on some feedback before publishing because worries of being asked to reverse course after publication otherwise

could put in editorial notes about ¨at risk¨ things in the pseudo-LC

think we could do pseudo-LC of *spec* in June

Core-AAM could be ready then if AAPI group is diligent

the deadline may help

accname may be hard to do by then

may be ok for those core mappings to be slightly later than spec pseudo-lc

practices want to finalize in time frame of spec PR

no worries in terms of spec timeline

what about the other aams?

RESOLUTION: ARIA 1.1 pseudo-LC in June, Core and AccName to follow a little after, everything else on its own timeline

would like graphics to proceed

work on timelnies for graphics and dpub modules in the tfs

Pubfixes pull request https://github.com/w3c/aria/pull/301

<clown> UIA + MSAA, also known as UIA Express

Core-AAM has an API referenced with partial implementation

which we pulled from Core

impacts testing of Core

maybe that´s a technical question for group on priority

(question if it has practical value enough to justify testing and spec effort)

<clown> https://www.w3.org/WAI/PF/testharness/testreport?testsuite_id=2

<clown> https://www.w3.org/WAI/PF/testharness/testreport?testsuite_id=1

need to sort more about that in another caucus

===

https://github.com/w3c/aria/pull/301"

any concerns about processing this?

note has conflicts now (didn´t orignally), need to process carefully

MC to process the pull request

Impact of TR style redesign

Respec does most of it

any issues we need to look at?

MC had troubles, but mostly when respec was broken

note in the AAMs the limited width column doesn´t accommodate the tables

when there´s another redesign round, will ping the editors to review

<ShaneM> is there a link to a recent heartbeat on TR space?

APG has a style conflict that needs to be fixed in our own style

<MichielBijl> https://www.w3.org/TR/wai-aria-practices-1.1/

<ShaneM> MichielBijl: thanks

related to a min-width, delete in apg css

questions about heading levels, which are respec issues, but need clarity on what the right path is

not consensus among respec maintainers about right way to handle

<tzviya> the roles are <dl>

could make them not headings, have script turn them into headings, or just make them <h4>

Central scripts repository https://www.w3.org/scripts/

<scribe> ACTION: Joseph to check if jquery version change has broken anything, W3C version is 1.11 and we were using 1.9 [recorded in http://www.w3.org/2016/04/06-aria-editors-minutes.html#action01]

<trackbot> Created ACTION-2045 - Check if jquery version change has broken anything, w3c version is 1.11 and we were using 1.9 [on Joseph Scheuhammer - due 2016-04-13].

note that jquery.details is still our own copy

see if we should add that to the central scripts repository

someone wanted a respec / aria JS fix for something but I can t remember what

nothing dredged up...

Repository split

<ShaneM> I thought we were doing it after the last heartbeat

issues on handling pull requests

<joanie> We said after 2.0 I thought.

<ShaneM> yay!

<joanie> I mean after 1.1

a few prefer to do after 1.1 done

maybe do just for APG and see how it goes

<ShaneM> I FIGURED IT OUT! It was headings that don't go into the ToC.

may need to sort cross references etc.

will check in on how it goes as input to making the bigger split

Next meeting

next meeting is April 20 at 1:00 pm Boston time

regrets from Tzviya

ARIA Editors

06 Apr 2016

Attendees

Contents