Forwarded message 1
Hi Chris, All:
A few quick responses just from me below ...
Chris Needham writes:
> Hi Matthew,
>
> Thank you, that's really helpful. And also thank you to you and Janina and Jason for joining our meeting today.
Happy for the opportunity. Thanks!
>
> We didn't talk too much about the upcoming things in our group. Here are a few thoughts:
>
> * HDR colour support for video, so the ability to render a wider range of colours and brightness. Support for HDR in HTML canvas is being proposed in the Color on the Web Community Group. What additional accessibility considerations does HDR video and graphics bring?
>
> * Apple's Dim Flashing Lights, which uses timed metadata to indicate regions of a video that include flashing lights, so that the player can respond by adjusting their brightness if needed. https://github.com/w3c/webvtt/issues/512
If I understand, a similar approach was prototyped at MIT and
demonstrated to our former WAI Director, Judy Brewer. It's an
outstanding approach which APA (and especially RQTF) have previously
discussed and fully support for flash mitigation. As you know, for some
people flashing at specific intervals can literally be life-threatening.
>
> * Use of canvas based rendering for TV user interfaces. HTML is commonly used today, but some (e.g., Comcast with LightningJS) are moving towards canvas based rendering instead of HTML, to improve UI animation performance. Is there a way to access the platform's accessibility features directly without having to use HTML?
This sounds very thorny. Animation alone is a thorny issue and
disruptive to many a11y use cases. Via CSS we've developed approaches to
mitigate. However, swapping in bitmapped, and dropping HTML seems literally
to require recreation of the entire a11y support architecture. To do so
simply for snappier animation seems a questionable value proposition to
me.
>
> * The Media Working Group has just started working on the Audio Session API, which allows websites to have some control over how audio from multiple elements is mixed, such as multiple elements in a page, or across pages in different browser tabs, or with audio from the host operating system. An example use case is transient notification sounds vs longer music or speech audio playback.
>
> * Next generation audio codecs, Dolby AC-4 and MPEG-H. There's no browser support for these yet, and most development is in the TV industry outside of the web, so this is an exploratory area. These codecs support user controllable dialog enhancement, and different audio components a single bitstream e.g., multiple languages, audio description, or commentary vs stadium noise at a sports event: https://www.w3.org/2022/09/15-me-minutes.html#t08
This appears to support some of what's described in MAUR 1.0 already,
which contains suggestions such as "clean audio" and such as sending
description to a second screen device. So, if it's being assembled from
individual elements and synchronized, we might be looking for options
related to output routing of various components.
>
> * More generally, another exploratory area is object based media, which includes ideas such as branching narratives and additional content overlaid on video. An example, accessibility features sometimes are currently "burned in" to video, such as a sign language interpreter, could this be delivered as separate components that are composited in the client, rather than as separate rendered video streams? There's more detail in this Ofcom report: https://www.ofcom.org.uk/__data/assets/pdf_file/0026/223973/Object-based-media-report.pdf
The burned in caption should be historic at this point! We would like to
think so, anyway. There's also quite a bit about this in MAUR 1.0, and
we can look to say more in 2.0. I expect we'd be more interested in
routing to specific output devices and/or location and size of SL
windows.
>
> Many thanks,
Likewise!
Janina
>
> Chris
>
> -----Original Message-----
> From: Matthew Atkinson <matkinson@tpgi.com>
> Sent: 07 July 2023 19:14
> To: Chris Needham <chris.needham@bbc.co.uk>; Nigel Megitt <nigel.megitt@bbc.co.uk>
> Cc: Gary Katsevman <gkatsevman@brightcove.com>; APA Chairs <group-apa-chairs@w3.org>; Paul Grenier <pgrenier@gmail.com>; Ali, Irfan <Irfan.Ali@blackrock.com>
> Subject: Re: Request for meeting with APA and MEIG at TPAC
>
> Hi Chris, Nigel, all,
>
> Apologies for my slow reply. Janina's the expert on most of these, but she's in the process of moving, and is out at the moment, so I will do my best to describe them in a bit more detail. We will be happy to provide more clarification on the 11th if that works for you too. Here is a bit more info on each...
>
> // Needs we have identified for markup in chapter titles (this relates to AAC/symbols primarily)
>
> This relates to chapter titles in media such as video (and audio). We're doing work that will help people who need to use symbols in order to understand content (either exclusively symbols, or symbols alongside prose). We'd like to ensure that chapter titles could be marked up richly, to support this need.
>
> // Interlinear publications
>
> This relates largely to written publications in which there are multiple logical "tracks" of information being presented in synch. So it could include passages from ancient texts, with have modern translations alongside, or it may include musical scores with additional information being presented alongside (e.g. lyrics or other information).
>
> // Specialised handling/rendering of embedded media (like MusicXML)
>
> UAs have got really good at displaying some things, but there are some types of media where a specialist rendering would be more suitable to people with particular access needs, and that is what we are getting at here. There may be a lack of information in the accessibility tree, due to specialised formats being used (again, we think musical notation is a good example here).
>
> I think the other three are probably the ones where you have far more experience with respect to the mechanics, than us (do let me know if you need any more info, though!); they were:
>
> * Multiple tracks of sign language
> * SSML in DAPT and HTML
> * Media Accessibility User Requirements
>
> For the last one, we have several ideas for updating the MAUR (some touched on above, and I think our Research Questions TF ("RQTF") group has several more, and Jason will be joining to touch on those on Tuesday).
>
> Hope this helps; please let me know if any further clarification is needed, and I hope I have conveyed our angle on these correctly.
>
> Best regards,
>
>
> Matthew
> --
> Matthew Tylee Atkinson (he/him)
> --
> Principal Accessibility Engineer
> TPG Interactive
> https://www.tpgi.com
> A Vispero Company
> https://www.vispero.com
> --
> This message is intended to be confidential and may be legally privileged. It is intended solely for the addressee. If you are not the intended recipient, please delete this message from your system and notify us immediately.
> Any disclosure, copying, distribution or action taken or omitted to be taken by an unintended recipient in reliance on this message is prohibited and may be unlawful.
>
>
>
>
> On 30/06/2023, 17:29, "Chris Needham" <chris.needham@bbc.co.uk <mailto:chris.needham@bbc.co.uk>> wrote:
>
>
> CAUTION: This email originated outside Vispero. Do not click links, open attachments or forward unless you recognize the sender.
>
>
>
>
> Hi Matthew, Nigel, all,
>
>
> So far I think we have the following as potential agenda items in the APA + MEIG + TTWG meeting:
>
>
> * Needs we have identified for markup in chapter titles (this relates to AAC/symbols primarily)
> * Interlinear publications
> * Specialised handling/rendering of embedded media (like MusicXML)
> * Multiple tracks of sign language
> * SSML in DAPT and HTML
> * Media Accessibility User Requirements (we also have a MEIG meeting on this on 11 July)
>
>
> I'd like to have a bit more context for each of these, so that we can attract the right people to the meeting. A couple of the topics I'm not too familiar with, e.g., the chapter title markup, and interlinear publications - does this have a connection to audio/video or timed text?
>
>
> Many thanks,
>
>
> Chris
>
>
>
>
> -----Original Message-----
> From: Matthew Atkinson <matkinson@tpgi.com <mailto:matkinson@tpgi.com>>
> Sent: 30 June 2023 16:37
> To: Nigel Megitt <nigel.megitt@bbc.co.uk <mailto:nigel.megitt@bbc.co.uk>>
> Cc: Gary Katsevman <gkatsevman@brightcove.com <mailto:gkatsevman@brightcove.com>>; Chris Needham <chris.needham@bbc.co.uk <mailto:chris.needham@bbc.co.uk>>; APA Chairs <group-apa-chairs@w3.org <mailto:group-apa-chairs@w3.org>>; Paul Grenier <pgrenier@gmail.com <mailto:pgrenier@gmail.com>>; Ali, Irfan <Irfan.Ali@blackrock.com <mailto:Irfan.Ali@blackrock.com>>
> Subject: Re: Request for meeting with APA and MEIG at TPAC
>
>
> Hi Nigel, Gary, Chris,
>
>
> I've CC'd Janina (APA co-chair) and Roy (our staff contact) (I thought I had last time; oops!), as well as Paul and Irfan, who chair the Spoken Presentation TF, as you raised the topic of SSML.
>
>
> APA and MEIG have a slot timetabled from 1430 to 1630 on Thursday (agenda on our wiki [1]); we hope you'll be able to join us for at least some of that. If it's looking tricky due to travel, please let us know. I don't think SSML is on our agenda with MEIG, so it may be that we could have a smaller meeting about that earlier in the week, if MEIG is OK with that. Thanks for the heads up on your upcoming HR request.
>
>
> Please let us know if the Thursday slot may work for you, and if anything changes regarding logistics for you; we'll do our best to be flexible.
>
>
> Best regards,
>
>
>
>
> Matthew
>
>
> [1] https://www.w3.org/WAI/APA/wiki/Meetings/TPAC_2023#MEIG_.2B_Timed_Text_.282_hours.29 <https://www.w3.org/WAI/APA/wiki/Meetings/TPAC_2023#MEIG_.2B_Timed_Text_.282_hours.29>
> --
> Matthew Tylee Atkinson (he/him)
> --
> Principal Accessibility Engineer
> TPG Interactive
> https://www.tpgi.com <https://www.tpgi.com> A Vispero Company https://www.vispero.com <https://www.vispero.com>
> --
> This message is intended to be confidential and may be legally privileged. It is intended solely for the addressee. If you are not the intended recipient, please delete this message from your system and notify us immediately.
> Any disclosure, copying, distribution or action taken or omitted to be taken by an unintended recipient in reliance on this message is prohibited and may be unlawful.
>
>
>
>
>
>
>
>
> On 30/06/2023, 16:20, "Nigel Megitt" <nigel.megitt@bbc.co.uk <mailto:nigel.megitt@bbc.co.uk> <mailto:nigel.megitt@bbc.co.uk <mailto:nigel.megitt@bbc.co.uk>>> wrote:
>
>
>
>
> CAUTION: This email originated outside Vispero. Do not click links, open attachments or forward unless you recognize the sender.
>
>
>
>
>
>
>
>
> Hi Matthew,
>
>
>
>
> CC+ Gary, co-chair TTWG and Chris, chair MEIG
>
>
>
>
> Apologies, I meant to get in touch after last week's TTWG call as promised. Yes, we'd be happy to have a joint meeting with the MEIG and APA. We may be able to make it on the Thursday; I'm not certain yet what my travel schedule will be, but can try to work around this.
>
>
>
>
> TTWG is meeting on the Tuesday already.
>
>
>
>
> Relevant TTWG meeting minutes: https://www.w3.org/2023/06/22-tt-minutes.html#t06 <https://www.w3.org/2023/06/22-tt-minutes.html#t06> <https://www.w3.org/2023/06/22-tt-minutes.html#t06> <https://www.w3.org/2023/06/22-tt-minutes.html#t06>>
>
>
>
>
> Can we add SSML in HTML to the agenda too? We have a parallel problem with DAPT in which we want to embed SSML but the document structure is not a neat fit for "just" including SSML vocabulary directly. It's https://github.com/w3c/dapt/issues/121 <https://github.com/w3c/dapt/issues/121> <https://github.com/w3c/dapt/issues/121> <https://github.com/w3c/dapt/issues/121>> - and I noticed that APA has been working on it in the context of HTML.
>
>
>
>
> I am intending soon (maybe early next week) to send a Horizontal Review request to APA for DAPT, so we may want to include that on the agenda too if there is anything to discuss; or we could make that a separate joint meeting with just TTWG and APA, any time on the Tuesday.
>
>
>
>
> Kind regards,
>
>
>
>
> Nigel
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> On 30/06/2023, 15:47, "Matthew Atkinson" <matkinson@tpgi.com <mailto:matkinson@tpgi.com> <mailto:matkinson@tpgi.com <mailto:matkinson@tpgi.com>> <mailto:matkinson@tpgi.com <mailto:matkinson@tpgi.com> <mailto:matkinson@tpgi.com <mailto:matkinson@tpgi.com>>>> wrote:
>
>
>
>
>
>
>
>
> Hi Nigel, all,
>
>
>
>
>
>
>
>
> We were just wondering if you had any updates on Timed Text's attendance (or not) of TPAC on the Thursday and Friday? If you're definitely not going to be present on the Thursday, might you have time to meet earlier in the week? (APA has a room for all of Monday, Tuesday, and Thursday.)
>
>
>
>
>
>
>
>
> Best regards,
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Matthew
> --
> Matthew Tylee Atkinson (he/him)
> --
> Principal Accessibility Engineer
> TPG Interactive
> https://www.tpgi.com <https://www.tpgi.com> <https://www.tpgi.com> <https://www.tpgi.com>> <https://www.tpgi.com> <https://www.tpgi.com>> <https://www.tpgi.com>> <https://www.tpgi.com&gt;>> A Vispero Company https://www.vispero.com <https://www.vispero.com> <https://www.vispero.com> <https://www.vispero.com>> <https://www.vispero.com> <https://www.vispero.com>> <https://www.vispero.com>> <https://www.vispero.com&gt;>>
> --
> This message is intended to be confidential and may be legally privileged. It is intended solely for the addressee. If you are not the intended recipient, please delete this message from your system and notify us immediately.
> Any disclosure, copying, distribution or action taken or omitted to be taken by an unintended recipient in reliance on this message is prohibited and may be unlawful.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> On 21/06/2023, 17:35, "Matthew Atkinson" <matkinson@tpgi.com <mailto:matkinson@tpgi.com> <mailto:matkinson@tpgi.com <mailto:matkinson@tpgi.com>> <mailto:matkinson@tpgi.com <mailto:matkinson@tpgi.com> <mailto:matkinson@tpgi.com <mailto:matkinson@tpgi.com>>> <mailto:matkinson@tpgi.com <mailto:matkinson@tpgi.com> <mailto:matkinson@tpgi.com <mailto:matkinson@tpgi.com>> <mailto:matkinson@tpgi.com <mailto:matkinson@tpgi.com> <mailto:matkinson@tpgi.com <mailto:matkinson@tpgi.com>>>>> wrote:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Thanks Nigel, and acknowledged regarding IBC; we'll await news following your WG call tomorrow.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Best regards,
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Matthew
> --
> Matthew Tylee Atkinson (he/him)
> --
> Principal Accessibility Engineer
> TPG Interactive
> https://www.tpgi.com <https://www.tpgi.com> <https://www.tpgi.com> <https://www.tpgi.com>> <https://www.tpgi.com> <https://www.tpgi.com>> <https://www.tpgi.com>> <https://www.tpgi.com&gt;>> <https://www.tpgi.com> <https://www.tpgi.com>> <https://www.tpgi.com>> <https://www.tpgi.com&gt;>> <https://www.tpgi.com>> <https://www.tpgi.com&gt;>> <https://www.tpgi.com&gt;>> <https://www.tpgi.com&amp;gt;&gt;>>
> A Vispero Company
> https://www.vispero.com <https://www.vispero.com> <https://www.vispero.com> <https://www.vispero.com>> <https://www.vispero.com> <https://www.vispero.com>> <https://www.vispero.com>> <https://www.vispero.com&gt;>> <https://www.vispero.com> <https://www.vispero.com>> <https://www.vispero.com>> <https://www.vispero.com&gt;>> <https://www.vispero.com>> <https://www.vispero.com&gt;>> <https://www.vispero.com&gt;>> <https://www.vispero.com&amp;gt;&gt;>>
> --
> This message is intended to be confidential and may be legally privileged. It is intended solely for the addressee. If you are not the intended recipient, please delete this message from your system and notify us immediately.
> Any disclosure, copying, distribution or action taken or omitted to be taken by an unintended recipient in reliance on this message is prohibited and may be unlawful.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> On 21/06/2023, 12:21, "Nigel Megitt" <nigel.megitt@bbc.co.uk <mailto:nigel.megitt@bbc.co.uk> <mailto:nigel.megitt@bbc.co.uk <mailto:nigel.megitt@bbc.co.uk>> <mailto:nigel.megitt@bbc.co.uk <mailto:nigel.megitt@bbc.co.uk> <mailto:nigel.megitt@bbc.co.uk <mailto:nigel.megitt@bbc.co.uk>>> <mailto:nigel.megitt@bbc.co.uk <mailto:nigel.megitt@bbc.co.uk> <mailto:nigel.megitt@bbc.co.uk <mailto:nigel.megitt@bbc.co.uk>> <mailto:nigel.megitt@bbc.co.uk <mailto:nigel.megitt@bbc.co.uk> <mailto:nigel.megitt@bbc.co.uk <mailto:nigel.megitt@bbc.co.uk>>>> <mailto:nigel.megitt@bbc.co.uk <mailto:nigel.megitt@bbc.co.uk> <mailto:nigel.megitt@bbc.co.uk <mailto:nigel.megitt@bbc.co.uk>> <mailto:nigel.megitt@bbc.co.uk <mailto:nigel.megitt@bbc.co.uk> <mailto:nigel.megitt@bbc.co.uk <mailto:nigel.megitt@bbc.co.uk>>> <mailto:nigel.megitt@bbc.co.uk <mailto:nigel.megitt@bbc.co.uk> <mailto:nigel.megitt@bbc.co.uk <mailto:nigel.megitt@bbc.co.uk>> <mailto:nigel.megitt@bbc.co.uk <mailto:nigel.megitt@bbc.co.uk> <mailto:nigel.megitt@bbc.co.uk <mailto:nigel.megitt@bbc.co.uk>>>>>> wrote:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> CAUTION: This email originated outside Vispero. Do not click links, open attachments or forward unless you recognize the sender.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Hi Matthew and Janina,
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Thank you for this. I cannot yet commit to any meetings on Thursday or Friday, and the same issue may affect other TTWG members: there is a large media-related exhibition and conference called IBC that begins on the Friday of TPAC week, but in Amsterdam, and people travelling there may leave Seville on the Thursday. I do not yet know which of TPAC and IBC I will be attending, but have been working on the assumption that I will attend IBC.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Aside from the scheduling issue I would be happy to support a joint meeting, and will raise it in our TPAC planning agenda item in our TTWG call tomorrow.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Kind regards,
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Nigel
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> On 21/06/2023, 12:07, "Matthew Atkinson" <matkinson@tpgi.com <mailto:matkinson@tpgi.com> <mailto:matkinson@tpgi.com <mailto:matkinson@tpgi.com>> <mailto:matkinson@tpgi.com <mailto:matkinson@tpgi.com> <mailto:matkinson@tpgi.com <mailto:matkinson@tpgi.com>>> <mailto:matkinson@tpgi.com <mailto:matkinson@tpgi.com> <mailto:matkinson@tpgi.com <mailto:matkinson@tpgi.com>> <mailto:matkinson@tpgi.com <mailto:matkinson@tpgi.com> <mailto:matkinson@tpgi.com <mailto:matkinson@tpgi.com>>>> <mailto:matkinson@tpgi.com <mailto:matkinson@tpgi.com> <mailto:matkinson@tpgi.com <mailto:matkinson@tpgi.com>> <mailto:matkinson@tpgi.com <mailto:matkinson@tpgi.com> <mailto:matkinson@tpgi.com <mailto:matkinson@tpgi.com>>> <mailto:matkinson@tpgi.com <mailto:matkinson@tpgi.com> <mailto:matkinson@tpgi.com <mailto:matkinson@tpgi.com>> <mailto:matkinson@tpgi.com <mailto:matkinson@tpgi.com> <mailto:matkinson@tpgi.com <mailto:matkinson@tpgi.com>>>>> <mailto:matkinson@tpgi.com <mailto:matkinson@tpgi.com> <mailto:matkinson@tpgi.com <mailto:matkinson@tpgi.com>> <mailto:matkinson@tpgi.com <mailto:matkinson@tpgi.com> <mailto:matkinson@tpgi.com <mailto:matkinson@tpgi.com>>> <mailto:matkinson@tpgi.com <mailto:matkinson@tpgi.com> <mailto:matkinson@tpgi.com <mailto:matkinson@tpgi.com>> <mailto:matkinson@tpgi.com <mailto:matkinson@tpgi.com> <mailto:matkinson@tpgi.com <mailto:matkinson@tpgi.com>>>> <mailto:matkinson@tpgi.com <mailto:matkinson@tpgi.com> <mailto:matkinson@tpgi.com <mailto:matkinson@tpgi.com>> <mailto:matkinson@tpgi.com <mailto:matkinson@tpgi.com> <mailto:matkinson@tpgi.com <mailto:matkinson@tpgi.com>>> <mailto:matkinson@tpgi.com <mailto:matkinson@tpgi.com> <mailto:matkinson@tpgi.com <mailto:matkinson@tpgi.com>> <mailto:matkinson@tpgi.com <mailto:matkinson@tpgi.com> <mailto:matkinson@tpgi.com <mailto:matkinson@tpgi.com>>>>>>> wrote:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Hi Nigel, Gary, Atsushi,
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> I hope this finds you well. We in APA would very-much like to meet with you at TPAC. There are a few things that relate to both timed text and MEIG work, as well as our own, so we aim to schedule a joint meeting with all three of our groups. Here's a very rough agenda, on which we'd be happy to elaborate:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> * Needs we have identified for markup in chapter titles (this relates to AAC/symbols primarily).
> * Interlinear publications.
> * Specialised handling/rendering of embedded media (like MusicXML).
> * Multiple tracks of sign language.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> (Depending on conversations during the week, we might also invite MNX, the Musical Notation CG.)
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> We and MEIG have a slot on Thursday, from 1430 to 1630 - might you be available during that time also?
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Best regards,
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Matthew & Janina
> --
> Matthew Tylee Atkinson (he/him)
> --
> Principal Accessibility Engineer
> TPG Interactive
> https://www.tpgi.com <https://www.tpgi.com> <https://www.tpgi.com> <https://www.tpgi.com>> <https://www.tpgi.com> <https://www.tpgi.com>> <https://www.tpgi.com>> <https://www.tpgi.com&gt;>> <https://www.tpgi.com> <https://www.tpgi.com>> <https://www.tpgi.com>> <https://www.tpgi.com&gt;>> <https://www.tpgi.com>> <https://www.tpgi.com&gt;>> <https://www.tpgi.com&gt;>> <https://www.tpgi.com&amp;gt;&gt;>> <https://www.tpgi.com> <https://www.tpgi.com>> <https://www.tpgi.com>> <https://www.tpgi.com&gt;>> <https://www.tpgi.com>> <https://www.tpgi.com&gt;>> <https://www.tpgi.com&gt;>> <https://www.tpgi.com&amp;gt;&gt;>> <https://www.tpgi.com>> <https://www.tpgi.com&gt;>> <https://www.tpgi.com&gt;>> <https://www.tpgi.com&amp;gt;&gt;>> <https://www.tpgi.com&gt;>> <https://www.tpgi.com&amp;gt;&gt;>> <https://www.tpgi.com&amp;gt;&gt;>> <https://www.tpgi.com&amp;amp;gt;&amp;gt;&gt;>> <https://www.tpgi.com> <https://www.tpgi.com>> <https://www.tpgi.com>> <https://www.tpgi.com&gt;>> <https://www.tpgi.com>> <https://www.tpgi.com&gt;>> <https://www.tpgi.com&gt;>> <https://www.tpgi.com&amp;gt;&gt;>> <https://www.tpgi.com>> <https://www.tpgi.com&gt;>> <https://www.tpgi.com&gt;>> <https://www.tpgi.com&amp;gt;&gt;>> <https://www.tpgi.com&gt;>> <https://www.tpgi.com&amp;gt;&gt;>> <https://www.tpgi.com&amp;gt;&gt;>> <https://www.tpgi.com&amp;amp;gt;&amp;gt;&gt;>> <https://www.tpgi.com>> <https://www.tpgi.com&gt;>> <https://www.tpgi.com&gt;>> <https://www.tpgi.com&amp;gt;&gt;>> <https://www.tpgi.com&gt;>> <https://www.tpgi.com&amp;gt;&gt;>> <https://www.tpgi.com&amp;gt;&gt;>> <https://www.tpgi.com&amp;amp;gt;&amp;gt;&gt;>> <https://www.tpgi.com&gt;>> <https://www.tpgi.com&amp;gt;&gt;>> <https://www.tpgi.com&amp;gt;&gt;>> <https://www.tpgi.com&amp;amp;gt;&amp;gt;&gt;>> <https://www.tpgi.com&amp;gt;&gt;>> <https://www.tpgi.com&amp;amp;gt;&amp;gt;&gt;>> <https://www.tpgi.com&amp;amp;gt;&amp;gt;&gt;>> <https://www.tpgi.com&amp;amp;amp;gt;&amp;amp;gt;&amp;gt;&gt;>>
> A Vispero Company
> https://www.vispero.com <https://www.vispero.com> <https://www.vispero.com> <https://www.vispero.com>> <https://www.vispero.com> <https://www.vispero.com>> <https://www.vispero.com>> <https://www.vispero.com&gt;>> <https://www.vispero.com> <https://www.vispero.com>> <https://www.vispero.com>> <https://www.vispero.com&gt;>> <https://www.vispero.com>> <https://www.vispero.com&gt;>> <https://www.vispero.com&gt;>> <https://www.vispero.com&amp;gt;&gt;>> <https://www.vispero.com> <https://www.vispero.com>> <https://www.vispero.com>> <https://www.vispero.com&gt;>> <https://www.vispero.com>> <https://www.vispero.com&gt;>> <https://www.vispero.com&gt;>> <https://www.vispero.com&amp;gt;&gt;>> <https://www.vispero.com>> <https://www.vispero.com&gt;>> <https://www.vispero.com&gt;>> <https://www.vispero.com&amp;gt;&gt;>> <https://www.vispero.com&gt;>> <https://www.vispero.com&amp;gt;&gt;>> <https://www.vispero.com&amp;gt;&gt;>> <https://www.vispero.com&amp;amp;gt;&amp;gt;&gt;>> <https://www.vispero.com> <https://www.vispero.com>> <https://www.vispero.com>> <https://www.vispero.com&gt;>> <https://www.vispero.com>> <https://www.vispero.com&gt;>> <https://www.vispero.com&gt;>> <https://www.vispero.com&amp;gt;&gt;>> <https://www.vispero.com>> <https://www.vispero.com&gt;>> <https://www.vispero.com&gt;>> <https://www.vispero.com&amp;gt;&gt;>> <https://www.vispero.com&gt;>> <https://www.vispero.com&amp;gt;&gt;>> <https://www.vispero.com&amp;gt;&gt;>> <https://www.vispero.com&amp;amp;gt;&amp;gt;&gt;>> <https://www.vispero.com>> <https://www.vispero.com&gt;>> <https://www.vispero.com&gt;>> <https://www.vispero.com&amp;gt;&gt;>> <https://www.vispero.com&gt;>> <https://www.vispero.com&amp;gt;&gt;>> <https://www.vispero.com&amp;gt;&gt;>> <https://www.vispero.com&amp;amp;gt;&amp;gt;&gt;>> <https://www.vispero.com&gt;>> <https://www.vispero.com&amp;gt;&gt;>> <https://www.vispero.com&amp;gt;&gt;>> <https://www.vispero.com&amp;amp;gt;&amp;gt;&gt;>> <https://www.vispero.com&amp;gt;&gt;>> <https://www.vispero.com&amp;amp;gt;&amp;gt;&gt;>> <https://www.vispero.com&amp;amp;gt;&amp;gt;&gt;>> <https://www.vispero.com&amp;amp;amp;gt;&amp;amp;gt;&amp;gt;&gt;>>
> --
> This message is intended to be confidential and may be legally privileged. It is intended solely for the addressee. If you are not the intended recipient, please delete this message from your system and notify us immediately.
> Any disclosure, copying, distribution or action taken or omitted to be taken by an unintended recipient in reliance on this message is prohibited and may be unlawful.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
--
Janina Sajka (she/her/hers)
Accessibility Consultant https://linkedin.com/in/jsajka
The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Co-Chair, Accessible Platform Architectures http://www.w3.org/wai/apa
Linux Foundation Fellow
https://www.linuxfoundation.org/board-of-directors-2/