scribe+

TPAC debrief

shawn: anything to share?

kevin: Feedback on success at TPAC. For WCAG 3 we are starting a dialog with some of the browser vendors. We met with all 4 major browsers.
... We've got names of people to continue conversations in quarterly meetings.
... We've got support for their involvement.

<Zakim> bruce_bailey, you wanted to say I loved TPAC JJ's session on defining views

<kevin> +1 to JJ's session... really good exploration

bruce: Wanted to highlight JJ's breakout session on mobile

<kevin> https://www.w3.org/2024/09/TPAC/breakouts.html#b-366284c0-35c5-416f-9b40-b76e43c49da5

<bruce_bailey> https://github.com/w3c/tpac2024-breakouts/issues/46

Link above is to JJ's session description

bruce: AG has to have this on their radar as this touches on WCAG 3, WCAG2ICT, as well as mobile

kevin: Agrees that it touches on WCAG 3 and what's a unit to be tested.
... looking at a hierarchy for testable "units" and what word to use that isn't used in other contexts.

bruce: Chuck was there and discussed connection/concerns with WCAG2ICT.

shawn: There's an open survey to provide input / feedback on TPAC. Open to in-person and remote participants.

<shawn> https://www.w3.org/2002/09/wbs/35125/tpac202409/

Survey link above...

upcoming publications and work to share

shawn: Contrats that WCAG2ICT goes out tomorrow, 8 October!

<lisa> congratulations!

kevin: WCAG 3 is looking to do another publication. Won't be in October, but we are getting closer - hopefully early November.
... will work with Shawn on communications. Need to get it done before the moratorium.

Bruce: How quickly will the press release go out on WCAG2ICT?

Shawn: We don't do an official press release, but will have it in WAI news and social media.
... it will be available tomorrow as the publication is made public.
... group reviewed the messaging for the WCAG2ICT announcement.
... Are the links to the updated/published WCAG2ICT doc ready for publication on the WAI website pages?

daniel: Yes, all is ready to go.

<shawn> previou email said "We expect this document will impact future ICT standards worldwide."

bruce: Would like to see that we talk about the importance of WCAG2ICT to 508 and the EN 301 549. We say it in the document, but could say it in the announcement.

shawn: Open to that, need to work on exact verbiage.

maryjo: Perhaps say something like, "Similar to the 2013 WCAG2ICT Note, we expect the newly published note to have an impact on future ICT standards worldwide."

Daniel: Maybe not mention the 2013 version specifically, but mention the "previous version"

Other

<lisa> GitHub issue #325 - Phil Jenkins’

<lisa> https://github.com/w3c/coga/issues/325

lisa: Had a question regarding the above linked issue, there was a content usable question about usage of AT and what is done in support of AT.

Was wondering if there needs to be a unified approach. Should we talk about it in this group first?

<kevin> +1 to having a collective perspective on this

shawn: Yes, would like to add that to next meeting's agenda

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)

Succeeded: s/perspectiveonthis/perspective on this/
Default Present: lisa, kevin, shawn, Daniel, maryjom, bruce_bailey
Present: lisa, kevin, shawn, Daniel, maryjom, bruce_bailey
No ScribeNick specified.  Guessing ScribeNick: maryjom
Inferring Scribes: maryjom

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.)