<janina> scribe: janina

Scribe, rrsagent, agenda, next meeting date

jb: Proposing November 21 not too good for u.S. folks, it's Thanksgiving

<Judy> NEXT MEETING: WEDNESDAY DECEMBER 5

Personalization and low vision user needs--does scope need to be expanded? (Jim)

ESO & ISO Update (George)

gk: Should wait for TS

General TPAC debrief

jb: Reminding evweryone to respond to the TPAC survey

gk: Appreciated guidance provided during TPAC Plenary re Knowledge Domain
... Guidance was use semantically rich information, and use components for presenting info

<Judy> Here is the survey link: https://www.w3.org/2002/09/wbs/35125/tpac2018-feedback-light/

<Judy> JB: Please try the survey link

Jean: Good au conversations with numerous individuals

<Brent> Just enjoyed the ability to conduct cross-team meetings.

<Judy> Janina: Personalization, good discussion, moving to next steps.

<Judy> Janina: Pronunciation, new work proposed by Mark Hakkinen, ETS, important to have accurate pronunciation especially during student assessments

<Judy> ...new markup for TTS engines, to increase pronunciation accuracy

<Judy> Here is the survey link: https://www.w3.org/2002/09/wbs/35125/tpac2018-feedback-light/ again...

<Judy> janina: also note the concerns expressed on synchronization, Marisa wrote up problems with existing mechanisms

<Judy> george: very well received...

<tzviya> https://github.com/w3c/sync-media-pub/blob/master/manifest-exts.md#1-sync-mediachapter1json minutes from PWG sync media session

EPub & ISO Update

gk: Have heard concerns moving epub a11y under iso
... This would be work originally in IDPF/W3C, now a W3C note, and now a work item under ISO
... A call monday coming to discuss the concerns
... Concerns coming from Apple

jb: Believe some of the issue has to do with how it got raised with ISO

ts: I set up the call to try to get us all communicating
... Hoping to sort things out

jb: Anything further on this?

Personalization and low vision user needs--does scope need to be expanded?

ja: Noticed recent APA Personalization pubs didn't address low vision
... Concerned with Personalization scope will encompass low vision
... Want to ask whether or where lv fits

Leverage existing W3C markup technologies to produce new specifications or additions to existing specifications which support content personalization for

various identified accessibility requirements;

mc: Also Personalization deliberately divided into modules to help focus work.
... It's expected we will add modules

jb: Wondering whether our Personalization doc should up front quote the 4 wcag principles

mc: A mod to the Explainer would be appropriate, if that doc isn't clear on this point

jb: Reminded of the common situation: "While you're doing your thing, could you also include ..."
... Asks JA whether there might be folks who could help add use cases and technical approaches

ja: Noting that css style sheets going away, and wondering how to pick up progress

bk: Noting testing in the testing content book

mc: Notes Personalization moved from ARIA to APA because we expect different strategies for different folks

<George> Knowledge Domain George minuting

Knowledge Domain update and next steps (Janina)

<George> JS: Headlines and next steps

<Judy> scribe: George

JS: A lot happened specific for math and general for others.

<janina> http://lists.w3.org/Archives/Public/public-apa/2018Nov/0002.html

Publishing brought it up and a breakout happened.

<tzviya> https://github.com/w3ctag/design-reviews/issues/313

JS posting links.

<Judy> agenda order is 5, 9, 6, 7, 8

Knowledge domain is what one should search for and get good information.

These are all grouped together.

Outcomes, yes we should do something.

Probably a community group to get organized.

ARIA Charter update

<janina> jb: Notes numerous side conversations concerning acceptable possible edits to the ARIA charter

<janina> jd: Noting that conversations continue ... but we seem to be making progress

Upcoming publications & announcements

<janina> Brent: Business Case for Digital Accessibility about to be published by EO

<janina> Brett: Also a pub on having an accessibility statement -- and a tool to draft

<janina> jb: Notes this was one of EO's earliest docs, now updated!

<janina> mc: Updated ARIA 1.2, and other WDs coming out Friday or Monday

<janina> jb: Asks about announcements for EO docs?

<janina> Brent: Yes

Any WG or TF updates or infoshare?

This is scribe.perl Revision: 1.154  of Date: 2018/09/25 16:35:56  
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/brett/Brent/
Default Present: janina, Joanmarie, Kathy, kimpatch, Brent, tzviya
Present: janina Joanmarie Kathy kimpatch Brent tzviya
Found Scribe: janina
Inferring ScribeNick: janina
Found Scribe: George
Inferring ScribeNick: George
Scribes: janina, George
ScribeNicks: janina, George
Found Date: 07 Nov 2018
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


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