W3C

- DRAFT -

AGWG Teleconference

26 Sep 2023

Attendees

Present
Chuck, Laura_Carlson, ShawnT, Francis_Storr, dan_bjorge, DanielHE, GreggVan, Frankie, Ben_Tillyer, alastairc, bruce_bailey, scotto, jon_avila, giacomo-petri, dj, Wilco, mbgower, bri, Raf, Makoto, sarahhorton, kevin, tburtin, Rain, jeanne, JaeunJemmaKu, kirkwood_, ljoakley, kirkwood, GN, AWK, Jennie, knights, Detlev, shadi, Poornima
Regrets
ToddL
Chair
alastairc
Scribe
dj

Contents


<alastairc> chair?

i can scribe

<scribe> scribe: dj

<alastairc> Don't join a break-out room yet, we'll explain the setup today.

kevin: i will stay in the main breakout room

Announcements (including sub-groups)

<AWK> +AWK

alastairc: announcements:
... 2 new subgroups starting
... 1: aid navigation
... 2: control semantics
... each run for 8 weeks, similar to TPAC
... more info coming in email
... announcement 2: final WCAG 2.2 hoops are out the door
... no exact date, but hopefully next week
... question?

Sub-group breakouts

alastairc: moving on
... we did many guidelines at TPAC, but some still need refining
... we want to get them ready for pull requests
... [today] we're going to just chug through them, like at TPAC

<alastairc> Audio and Video https://docs.google.com/document/d/1Hjp8lzf54h7dCsFQP5xqj0pZgWBSQJuOIK_FV36zIb0/edit

alastairc: we'll be doing 4 today

<alastairc> Consistent design: https://docs.google.com/document/d/1kwv_nyiYfeYIhsFeyd3GblhYbquQktFzBsI0rxBD1OQ/edit#heading=h.mjgzi6tjo9ev

<alastairc> Flexible view https://docs.google.com/document/d/1d0RpZh4dqcSWOGsbxQ6Xdo_Lp6OMh3_8J-Z9Ttbm1Co/edit#heading=h.spr6hfitvd9m

<alastairc> Structured content https://docs.google.com/document/d/1EAQZ1Bt8FAzWU90ZDM1rP9nxiQj_fxuX4pV4rBx65nw/edit#heading=h.spr6hfitvd9m

alastairc: select a breakout room to join (not yet though)
... scratchpad document for each guideline
... go to # Outcomes
... copy the template, and make the description and etcetera for each outcome
... fill out research, say 'needs more research', or say working logic
... lori?

ljoakley: should we redo the work from TPAC?

alastairc: no, use that work and refine it
... and package it up so research, user needs, and test are with each outcome

Chuck: Timings & Interruptions did this yesterday
... we found that description is probably same as TPAC
... short name is ~3 word name for outcome

alastairc: when you go into the groups, someone should copy & paste the template
... we want the original groups to do this because they know the outcomes best, and so we can all get these done really quickly
... if you're in one group, join that
... if you're in 2, pick one
... if you weren't in any, pick one
... does everyone understand?

bruce_bailey: each google doc is one guideline?

alastairc: yes
... step 1: "here's one outcome [name of outcome]"
... copy it up top in appropriate format
... discuss whether this is as good as you can make it right now

mbgower: the order of # User Need and # Test vary across google docs

alastairc: yes; please follow the order on this on [on screen] though

<Zakim> Chuck, you wanted to say we will reconvene in main room at <tbd>

Chuck: we should reconvene at 12:20 in main room regardless of progress

alastairc: that will give us about an hour

<Zakim> bruce_bailey, you wanted to ask if Flexible Views is presently missing Relevant Research section ?

alastairc: we might just close the breakout rooms, which could be distruptive

bruce_bailey: one of the scratchpads doesn't have the research section
... Flexible Views

alastairc: hopefully someone who was in that group can find it
... that's a good example of why we want to package it better

Chuck: 1. I agree. 2. If we don't have research, just note that

alastairc: any more questions?

<Chuck> NOTE: Scribing has ended, subgroups will perform the exercise.

<Detlev> I'll pick flexible views

consistent design

<ShawnT> I'll take Structured Content

<alastairc> q/

<Zakim> bruce_bailey, you wanted to say alternatives group had some difficulty discerning between "research" and resources.

<Zakim> alastairc, you wanted to comment on resources vs research and to

<Zakim> Chuck, you wanted to say that it was easier having been involved in the process from the start through to this point

<Detlev> is this format your idea of using the calls in the future?

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes manually created (not a transcript), formatted by David Booth's scribe.perl version 1.200 (CVS log)
$Date: 2023/09/26 16:34:06 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision VERSION of 2020-12-31
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Default Present: Chuck, Laura_Carlson, ShawnT, Francis_Storr, dan_bjorge, DanielHE, GreggVan, Frankie, Ben_Tillyer, alastairc, bruce_bailey, scotto, jon_avila, giacomo-petri, dj, Wilco, mbgower, bri, Raf, Makoto, sarahhorton, kevin, tburtin, Rain, jeanne, JaeunJemmaKu, kirkwood_, ljoakley, kirkwood, GN, AWK, Jennie, knights, Detlev, shadi, Poornima
Present: Chuck, Laura_Carlson, ShawnT, Francis_Storr, dan_bjorge, DanielHE, GreggVan, Frankie, Ben_Tillyer, alastairc, bruce_bailey, scotto, jon_avila, giacomo-petri, dj, Wilco, mbgower, bri, Raf, Makoto, sarahhorton, kevin, tburtin, Rain, jeanne, JaeunJemmaKu, kirkwood_, ljoakley, kirkwood, GN, AWK, Jennie, knights, Detlev, shadi, Poornima
Regrets: ToddL
Found Scribe: dj
Inferring ScribeNick: dj

WARNING: No date found!  Assuming today.  (Hint: Specify
the W3C IRC log URL, and the date will be determined from that.)
Or specify the date like this:
<dbooth> Date: 12 Sep 2002

People with action items: 

WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)


[End of scribe.perl diagnostic output]