<JF> scribe: Matthew_Atkinson
Janina: we are presently
collecting agenda items, and discussions with other groupos
that are also meeting at TPAC.
... e.g. we'd like to meet with CSS.
... aiming to arrange the meetings by late June/early July.
Skeleton agenda will be posted soon.
<Irfan_Ali> https://github.com/w3c/pronunciation/wiki
Irfan: timeline has been added to
the Wiki (link above).
... any questions/concerns/approval of the timeline?
Specific link to timeline (at the bottom of the page): https://github.com/w3c/pronunciation/wiki#timeline
Irfan: proposing to make date for user-scenarios doc to August (from July), so all are August.
JF: notes clarification on the year may be good to include, also perhaps nominate a specific date in August.
Michael: moratorium for TPAC is
expected to be the week of TPAC.
... suggests call for consensus should be approved by
2019-09-02, which means initiating it in the last week of
August at the very latest.
JF: propose 2019-08-21. (Seems generally accepted.)
Michael: need to ensure that no edits are needed after that date.
JF: Review of final deliverables proposed for the 2019-08-09, allowing for the following week for review, so the CFC can be published on 2019-08-21.
"Review" above is staff contact review (early August)
<JF> Timeline: Pronunciation TF forwards "complete" document to MC and Roy by August 9th W/O Aug 12 - 16: review by staff contacts Issue CfC on Aug. 21st - close on Aug 28 Assuming positive: forwards to PLH W/O Sept 2 Presume publish: Sept 10
<JF> +1 to timeline
Janina: looking to publish next review draft of CAPTCHA document on 2019-05-28.
Zakim item 3
Janina: looking to publish next
review draft of CAPTCHA document on 2019-05-28.
... got a lot of substantive comments during the last round of
reviews.
Michael: CSS lists needs to be discussed.
Janina: Need to talk with Ian Pouncey.
Michael: Content negotiation by profile - taken to Personalisation.
Janina: It was taken back to them and they found it to be orthogonal.
JF: disagrees; will respond on-list.
Michael: both of these are being left as assigned spec reviews.
<MichaelC> close action-2192
<trackbot> Closed action-2192.
<JF> scribe: JF
MA: met with RQTF group0 - provided a lot of feedback and requests for clarifications
some things came up and may link to external resources (i.e FAST, MAUR, others))
<janina> http://www.w3.org/TR/media-accessibility-reqs/
MA: Game Accessibility guidelines also hjas great info, including Best Practices and some guidelines
i.e option to re-map controller input, or provide means to adjust or qugment when quick reaction times are required
much of this is based upon design decisions
<janina> RQTF conversation today is here:
<janina> https://lists.w3.org/Archives/Public/public-rqtf/2019May/0007.html
lots of really good examples already
Ian Hamilton has been quite involved there
Still have some additional edits and clarifications to make, to ensure this understandable to a non-a11y audience
"awareness" will be a big issue
however feedback from RQTF was generally positive
<Matthew_Atkinson> Game Accessibility Guidelines: http://gameaccessibilityguidelines.com/
MA: will surface a few examples:
one was, when we use accronyms, they need to be expanded
<Matthew_Atkinson> This could be a good summary of CVAA? https://www.fcc.gov/consumers/guides/21st-century-communications-and-video-accessibility-act-cvaa
MA: may also provide more than just expanded accronyms, also provide linsk to resources
additional question about how specialist input devices work? would they emulate traditional controllers, or would they be fully customizable?
May leave this as an open question for now
Jason noted however there may be some privacy concerns
MA: we've discussed this in various ways previously - hot topic
but there are +'s and -'s.. everyone seems to have an opinion (and there may be opposing opinions) but a very important question to follow up on
JS: any further input? this is due Friday
MA: one final positive thing... Steve (noble)> gave really good examples of edu games for kids, that used HTML5
and showed some filtering options (i.e. filter out bg music so students can focus mbetter on content)
MA: because it is already focused on content design, it remains open to a11y adaptation
JS: any furtehr comments?
would like that APA point to it as well (example of good work happening at APA)
[discussion on how to promote this internally]
MC: after the workshop, we may be able to create a pointer to that page
MA: had a question about acknowledgments
will acknowledge Ian Hamilton, APA and RQTF
question whether to indicate specific names
that are linked/participate at the W3C
JS: anything else?
JS: may have to defer this for a while
JS: no other items
zakim clear agenda
zakim: clear agenda
<Matthew_Atkinson> trackbot, end meeting
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/Sept 11/Sept 10/ Succeeded: s/dioscussion/discussion/ Default Present: Becka11y, Irfan_Ali, Matthew_Atkinson, MichaelC, JF, janina Present: Becka11y Irfan_Ali Matthew_Atkinson MichaelC JF janina Found Scribe: Matthew_Atkinson Inferring ScribeNick: Matthew_Atkinson Found Scribe: JF Inferring ScribeNick: JF Scribes: Matthew_Atkinson, JF ScribeNicks: Matthew_Atkinson, JF Found Date: 08 May 2019 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.)[End of scribe.perl diagnostic output]