Meeting minutes
TPAC scheduling
janina: not sure if schedule is posted yet.
becky: will look that up
janina: two hours later than this call for Monday the 25th for second meeting with COGA. is it possible?
Lionel_Wolberger: TPAC COGA and personalization at noon NYC time the 25th?
<Matthew_Atkinson> Noon EST WFM
janina: introducing what we do to COGA. don't need all present.
becky: no schedule yet
janina: TPAC is next week. presume no meeting on the 18th.
janina: resume regular meetings on November 1
Lionel_Wolberger: meeting with Silver? waiting and watch the e-mail list for updates
<Lionel_Wolberger_> Personalizing the Web for Better Accessibility
Lionel_Wolberger: that's the meeting requested for Mon, Tues, or Thurs. 18th, 19th, 21st
janina: we need to get cleared on our materials. who's chairing? Lionel, Sharon, Janina?
becky: facilitator could do both
Lionel_Wolberger: once time is set we will find chair. Sharon or Lionel. Chair TBD
Lionel_Wolberger: second of Janina's question. are we taking questions in the midst of the presentation?
Matthew_Atkinson: open to either (at the end or during)
janina: only caution taking during. responsible to manage time of questions so that you can get to the end of the presentation. want to ensure getting through the whole deck
Matthew_Atkinson: will monitor. will park questions until the end if they are larger
Progress on the Personalization deck for TPAC
Lionel_Wolberger: progress on the deck? thanks for all your work so far
Matthew_Atkinson: coming together nicely. trying to keep it short and simple. some figures need updating. should be close to wrapping up after meeting with Lisa tomorrow.
Matthew_Atkinson: testing the right-to-left (RTL). would be nice to have code sample. will ask Lisa about a good sample sentence
CharlesL: can we get link to slide deck, please? want to check from low vision point-of-view
<Matthew_Atkinson> https://
<Matthew_Atkinson> Preview URL is: https://
CharlesL: Janina do you know how closed captioning will work? concern about blocking content
janina: good point. will be manually done, not relying on auto-captioning
CharlesL: captioning obscuring content. had to investigate a previous presentation with W3C
Matthew_Atkinson: shouldn't be much of a concern but there are a couple of slides which could be affected. will review and consider this. really good catch, Charles
Lionel_Wolberger: feedback on presentation: I find it useful to show sample code (e.g. data-simplification). another slide that explains the attribute and its values. next slide is demo for eCommerce
Lionel_Wolberger: this is where I mentioned migraines and it really got the point across during the demo.
Lionel_Wolberger: author would mark up the personalization option in the demo. going through the demo really helps with the storytelling aspect.
Lionel_Wolberger: talked about how I have been presenting
Matthew_Atkinson: liked the ideas. will consider adding more technical information.
Matthew_Atkinson: there are three demos that show different user journeys so they cover a nice range
janina: underscore the value of the sample code. W3C is very technical and the code would help the impact. good for emphasis. highlight the curb cut
CharlesL: just wanted to say "wow" Lionel. great presentation style. need, solution, code samples. also want to emphasize relevance of code samples. demos are great!
janina: should be publishing slide deck after TPAC
Matthew_Atkinson: slides should be published, yes. will be available
Symbols & i18n LTR/RTL Update (Follow-up on i18n issue #144 actions Lionel, Matt, Charles)
<Matthew_Atkinson> URL for the email Lionel is summarizing: https://
Lionel_Wolberger: completed action. wrote summary to e-mails. information learned: consulted an expert in RTL languages. there are no LTR or RTL issues. exactly as John said but now we have expert backup. 1:1 ratio of words to symbols
Matthew_Atkinson: did some basic testing. haven't put code samples in. when flipped into RTL everything gets flipped. images come first just as LTR. positioning is exactly opposite which seems to be correct
Matthew_Atkinson: we need to be careful with where the symbol is located. depending on positioning, that probably could be affected by changing writing direction
Matthew_Atkinson: potential issues with top-down. will do more investigation
CharlesL: thought there were some symbols for groups of words. is that not the case?
Lionel_Wolberger: some symbols can capture multiple words. symbol boards the expert showed me were one or two symbols per word. expert said that symbols exist in isolation. they are not combined.
Lionel_Wolberger: don't put two symbols together. separate symbols
<Zakim> janina, you wanted to offer vocabulary to describe rtl -- retrograde
janina: "retrograde" as the term for things being the same LTR as RTL
janina: don't want to be caught up in Bliss' nomenclature and process
Lionel_Wolberger: what people need are recipes and procedures according to expert.
<Matthew_Atkinson> I think this may be the site Lionel referred to: https://
<janina> +1 to Lionel's suggestions
Lionel_Wolberger: exciting conversation. recommended recipe. thought it could in combination with simplification
Matthew_Atkinson: concerned about some messages. we need to be clear about the use case so that we can capture as wide an audience as possible initially
Lionel_Wolberger: finding other symbols more useful than Bliss'
janina: recipe is a great word. we want to support all use cases and mechanisms
<Lionel_Wolberger_> ARASAAC
<Lionel_Wolberger_> https://
Lionel_Wolberger: this is a symbol set from the global symbols site
Lionel_Wolberger: proposing using recipe instead of Alice in Wonderland. which recipe should we pick?
janina: why not just use cup of tea as it has been around for a long time
Lionel_Wolberger: maybe too simple. how about salsa?
Lionel_Wolberger: Charles please get recipe to Matthew and involve Steve Lee
CharlesL: will find and send forward
Matthew_Atkinson: be mindful of licensing. ARASAAC seems to be creative commons and non-commercial. should be fine for W3C but may be an issue later
Lionel_Wolberger: still some unanswered questions but have enough to mark up new content