Joint meeting with APA at TPAC

TAG has confirmed the meeting to discuss the APA Pronunciation Task Force issues on Friday, Oct 16, 15:00-16:00 UTC (11:00am - 12:00 EDT)<https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.timeanddate.com%2Fworldclock%2Ffixedtime.html%3Fiso%3D20201016T15%26p1%3D1440%26ah%3D1&data=04%7C01%7Ciali%40ets.org%7C80c5188208ef4a177b7008d8712c3077%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637383781893493866%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=aoDYvp0ktxx%2F860%2Bv5z6gyZTZXH1b8vDX3vm%2FOPtNXY%3D&reserved=0>

We will use the standard APA meeting zoom. Details can be found at https://www.w3.org/2017/08/telecon-info_apa-tpac<https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2F2017%2F08%2Ftelecon-info_apa-tpac&data=04%7C01%7Ciali%40ets.org%7C80c5188208ef4a177b7008d8712c3077%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637383781893503823%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=uYBwqBfXKxhtnAe5k%2Fbij0MVPFECKPVrXzYwcyuUpJM%3D&reserved=0>.

Details about our topic is found in this issue:  https://github.com/w3ctag/meetings/issues/46<https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3ctag%2Fmeetings%2Fissues%2F46&data=04%7C01%7Ciali%40ets.org%7C80c5188208ef4a177b7008d8712c3077%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637383781893503823%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=s7FBPI8vTFum0IHYcdotFuk4n9TTmfsMS%2FJf%2FuxCJCs%3D&reserved=0>

We look forward to discussing this with those who can attend.

Agenda :

  *   Group: APA Pronunciation Task Force
  *   Topic: Discussion of two proposed implementations for Pronunciation FPWD(details in comments below)
  *   Specification URL: [spec url]
  *   Explainer (containing user needs and example code)¹: https://w3c.github.io/pronunciation/explainer

  *   GitHub issues (if you prefer feedback filed there): [url]




On Oct 6, 2020, at 4:49 PM, Becky Gibson <becky@knowbility.org<mailto:becky@knowbility.org>> wrote:

Hi,
I’m just following up to confirm that I did create two separate meeting requests to discuss Personalization and Pronunciation issues with the TAG.  We would also like to invite the WICG chairs and other interested parties to attend. Is there any progress on scheduling these meetings or additional items that are needed from APA?

Personalization request for Thursday, October 15, 14:00-15:00 UTC and proposed agenda: https://github.com/w3ctag/meetings/issues/45<https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3ctag%2Fmeetings%2Fissues%2F45&data=04%7C01%7Ciali%40ets.org%7C80c5188208ef4a177b7008d8712c3077%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637383781893513782%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=fSyW6wtCpp3Qxgdfk6joZPXXQKuzRePSLp5aMH0RwI4%3D&reserved=0>

Pronunciation request for Friday, October 16 at 3:00–4:00 UTC and proposed agenda: https://github.com/w3ctag/meetings/issues/46<https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3ctag%2Fmeetings%2Fissues%2F46&data=04%7C01%7Ciali%40ets.org%7C80c5188208ef4a177b7008d8712c3077%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637383781893513782%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=N6EzMvZa7JsfelbLE6vKNQ5i6CWwfnN0aA60hk1Xbi0%3D&reserved=0>

thanks,
Becky
co-chair with Janina Sajka of APA



On Sep 23, 2020, at 1:15 PM, Becky Gibson <becky@knowbility.org<mailto:becky@knowbility.org>> wrote:

Hi, Dan,

Thanks for the update. I am happy to create an issue requesting time with the TAG at TPAC.  The issues for Personalization and Pronunciation are different and may required varied skill or interest levels. Should I request two separate meetings or stick to just one?

To briefly recap the issues (see full details and links with more information in the thread below).

The personalization task force needs a reserved attribute prefix to replace
data- which we used during development and
prototype implementation per Sec. 3.2.6.6 of the HTML specification. We
believe this is a simple request, but we want to address any concerns up
front.

Pronunciation is considering two different approaches.
1) request a new attribute (similar to personalization) to suite accessibility needs
2) an SSML approach that is more widely applicable across the industry
We’d like guidance on whether to pursue the second approach which would require negotiation with WHATWG to admit a subset of SSML into the HTML specification.

The question right now is should I request two separate meetings with TAG at TPAC or just one?

thanks,
-becky




On Sep 23, 2020, at 3:39 AM, Daniel Appelquist <dan@torgo.com<mailto:dan@torgo.com>> wrote:

Hi Becky -

[Adding Hadley, Alice and Rossen who are assigned to our review issue on Personalzation Semantics https://github.com/w3ctag/design-reviews/issues/476<https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3ctag%2Fdesign-reviews%2Fissues%2F476&data=04%7C01%7Ciali%40ets.org%7C80c5188208ef4a177b7008d8712c3077%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637383781893523743%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=cHJJTKO0jgrkXGIcozzbYxZw7a8hP12egati96D%2BrBI%3D&reserved=0>.]

We might have a potential issue with that time.  We're due to discuss this issue in one of our breakouts of our virtual f2f (https://github.com/w3ctag/meetings/tree/gh-pages/2020/09-europe<https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3ctag%2Fmeetings%2Ftree%2Fgh-pages%2F2020%2F09-europe&data=04%7C01%7Ciali%40ets.org%7C80c5188208ef4a177b7008d8712c3077%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637383781893523743%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=AJkfiZbZfuYULnW3xW4OvwS%2F3kZ4B69FZH%2B0u2A6P2g%3D&reserved=0>) on Thursday. We're going to try to do some more work on this issue within the TAG and then get back to you with a preferred way forward if that's OK. Expect an email on Friday. In the mean time, can I ask you to please file an issue here: https://github.com/w3ctag/meetings/issues/new/choose<https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3ctag%2Fmeetings%2Fissues%2Fnew%2Fchoose&data=04%7C01%7Ciali%40ets.org%7C80c5188208ef4a177b7008d8712c3077%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637383781893523743%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=bm8YYG%2BN8mf9Uq4J936GiAUhVP%2Ftqv7WcwP0jlM0RcM%3D&reserved=0> for requesting some TPAC time with the TAG so we can better track this?

Thanks,
Dan



‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Tuesday, 22 September 2020 19:24, Becky Gibson <becky@knowbility.org<mailto:becky@knowbility.org>> wrote:

Hi, Chris, All,

As co-chair I am following up to coordinate a meeting time for all interested in pursuing the below issues.  I realize that the HTML WG is not meeting at TPAC but I have not removed anyone from this email thread.

To get things started I will propose a joint meeting with APA and interested parties on

Friday, October 16 at 3:00–4:00 UTC (11:00–12:00 EDT).

Please propose another time that may better suit your and other potential participant needs. Also, please inform us if there are others who we should invite directly.  We have posted the current schedule of APA joint meetings  on the TPAC Group Meetings Page (https://www.w3.org/wiki/TPAC/2020/GroupMeetings<https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2Fwiki%2FTPAC%2F2020%2FGroupMeetings&data=04%7C01%7Ciali%40ets.org%7C80c5188208ef4a177b7008d8712c3077%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637383781893533695%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=KfExFFWrawNOSttUQxtXjy58ibWWyFRSnOwCBJ8pXSc%3D&reserved=0>).

thanks,
Becky & Janina

On Sep 18, 2020, at 1:50 PM, Janina Sajka <janina@rednote.net<mailto:janina@rednote.net>> wrote:

Hi Chris, All:

Herewith my promissed explanation about the guidance APA is seeking
during TPAC. I believe it's appropriate for us to engage both relevant
WICG and TAG, but also anyone else we know might have a direct interest
in the two APA specifications described below. We thank you in advance
for your help on that, and your willingness to meet.

APA hjas two normative specifications emerging from two APA Task Forces
each of which needs a different level of specific guidance from the
wider community. Also, it is our understanding that normative specs
should also be vetted through WICG these days.

We should have videos posted providing 3-minute introductions to each of
these two specs sometime next week.

Critically, each of our specifications also needs something specific
from the WHAT-WG, and we want to solicit our W3C colleagues guidance
before approaching WHAT with a formal github issue, though we are also
cc'ing and inviting Anne van Kesteren who has liaised with APA
faithfully concerning a11y issues at WHAT.

Describing each specification separately ...

***Personalization TF***

We have one module (from what is expected to be a short series of
probably 3 modules) just about ready for CR. The specification describes an ARIA-type semantic overlay
that will facilitate web use by people with various cognitive and
learning disabilities not previously served directly by assistive
technology.

One key user group who will benefit from this overlay markup is persons
who don't do well with written text but rather rely on a long
established communication approach known in accessibility as
"Augmentative and alternative communication (AAC)." AAC users tend to be
schooled from their earliest years to a particular, proprietary AAC
vocabulary. AAC users in a different educational jurisdiction will have
been schooled to a different vocabulary. Unfortunately, these
vocabularies are mutually unintelligible. Among other things it does,
our specification will facilitate automated translation among
them--greatly expanding communication for quite a few people who could
not communicate with each other before.

What we need from WHAT: We need an reserved attribute prefix to replace
data- which we used during development and
prototype implementation per Sec. 3.2.6.6 of the HTML specification. We
believe this is a simple request, but we want to address any concerns up
front.

The Explainer we've prepared for the TAG is here:

https://github.com/w3c/personalization-semantics/wiki/Explainer-for-Personalization-Semantics<https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fpersonalization-semantics%2Fwiki%2FExplainer-for-Personalization-Semantics&data=04%7C01%7Ciali%40ets.org%7C80c5188208ef4a177b7008d8712c3077%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637383781893533695%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=xnnZCKoC1jVXiZcI8DL8SgAA1ir6hKCuCsgvOvhpd2I%3D&reserved=0>

***Pronunciation TF***

Screen reader users, as well as "read aloud" assistive technology users
(such as persons living with dyslexia) have long put up with some pretty
horrendous pronunciation from text to speech (TTS) engines. This becomes
more than simply annoying, however, in circumstances such as timed
academic test taking (such as the LSAT that is used in law school
applications).

We are now on the verge of writing a specification for First Public
Working Draft (FPWD) publication specifying an approach to close this
gap for accessibility.

However, we need to decide between two candidate approaches.

1.) We have at least one candidate approach that will serve
accessibility requirements well. This could be the end of the story.

2.) However, it seems to us there's need of an approach that's more
widely applicable across the industry now that we've moved into an era
of voice computing with major platforms like Amazon's Alexa, Apple's
Siri, Google's Assistant, and Microsoft's cortana. Our forthcoming video
will illustrate an SSML based approach we believe could work for us and
the wider industry.

The question is whether (or not) there is interest in
pursuing a more generally applicable specification? This is what
we want to discuss with you during TPAC.

What we would need from WHAT: The more widely applicable
approach would require admitting a subset of SSML markup into
the HTML specification with the same kind of status as currently
exists for XVG and MathML.

The Pronunciation TF's Explainer (latest Editor's Draft) is here:

https://w3c.github.io/pronunciation/explainer<https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fw3c.github.io%2Fpronunciation%2Fexplainer&data=04%7C01%7Ciali%40ets.org%7C80c5188208ef4a177b7008d8712c3077%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637383781893543649%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=B88iP5OhFIjNuxqdSow5zDCrEKp7JM935pV9gSZgVEA%3D&reserved=0>

Hoping these two explanations make sense, and happy to say more
in email should that be helpful. Thanking you in advance for
your guidance on these two specs:

Janina and Becky
APA Chairs



Janina Sajka writes:
Thanks, Chris. We would very much benefit from some guidance bbeyond the
just accessibility within W3C.

Let me put together a brief explanation of what we want to discuss and
forward that later today. With that in hand perhaps you could help us
identify who we most need to set up a meeting with?

Coming your way shortly ...

Janina

Chris Wilson writes:
Hi Becky!

Sorry, this had fallen down in my inbox before. WICG itself doesn't really
meet as a group; individual incubations may schedule time to discuss
topics. My fellow co-chairs and I could join a meeting if you think that
would be helpful.

On Tue, Sep 15, 2020 at 9:42 AM Becky Gibson <becky@knowbility.org<mailto:becky@knowbility.org>> wrote:

Hi, Tess,

Yes, we are working to draft an issue for WHAT WG about our request for an
additional attribute for personalization. However, we would still like
input from the W3C on our approach for Pronunciation. There are currently
two approaches we are considering and would like more discussion with a
wider audience, including representatives from browser vendors as well as
assistive technologies. Thus, APA would still like to have a joint meeting
with at least WICG and possibly HTML.

Pronunciation is considering a request for an additional attribute or to
embed a subset of SSML into HTML. We believe the benefits of adding
pronunciation hints reaches further than just accessibility and thus
warrants a wider discussion within the W3C.

thanks,
Becky & Janina
co-chairs APA

On Aug 27, 2020, at 6:01 PM, Theresa O'Connor <hober@apple.com<mailto:hober@apple.com>> wrote:

Hi Becky,

You wrote:

If the path forward is to file specific issues with WHATWG we can do
that.

Please do! That's what all W3C groups wishing to change the HTML Living
Standard (or any other WHATWG Living Standard) are encouraged to do. As
[the HTML WG charter](https://www.w3.org/2019/06/htmlwg-charter.html<https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2F2019%2F06%2Fhtmlwg-charter.html&data=04%7C01%7Ciali%40ets.org%7C80c5188208ef4a177b7008d8712c3077%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637383781893543649%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=hRp5nxGmHkc5uKGZ9ajap2gRjYOXvpFZ2%2BxGHtTfYpg%3D&reserved=0>)
says:

The community (including users, implementers, and developers) and
horizontal review groups are encouraged to contribute directly to the
WHATWG [HTML](https://github.com/whatwg/html/<https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fwhatwg%2Fhtml%2F&data=04%7C01%7Ciali%40ets.org%7C80c5188208ef4a177b7008d8712c3077%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637383781893553610%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=9XjwV0mW8Gshq7LbolfEjd5CDJhLjMvZBS0TOx7skUk%3D&reserved=0>) and
[DOM](https://github.com/whatwg/dom/<https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fwhatwg%2Fdom%2F&data=04%7C01%7Ciali%40ets.org%7C80c5188208ef4a177b7008d8712c3077%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637383781893553610%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=sfd2yOxIOmrOZzBa7QbBqPLFMFRCS6SIDZaF4qnqrSM%3D&reserved=0>) repositories; raising issues,
proposing solutions, commenting on proposed solutions, and indicating
support or otherwise for proposals. In the event that a person raising
an issue feels that the issue has not been fairly resolved by WHATWG,
the HTML Working Group may help to explain the resolution and attempts
to work with the person and the WHATWG editors to achieve consensus,
as detailed in the Group [work
mode](https://www.w3.org/2019/06/htmlwg-charter.html#workmode<https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2F2019%2F06%2Fhtmlwg-charter.html%23workmode&data=04%7C01%7Ciali%40ets.org%7C80c5188208ef4a177b7008d8712c3077%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637383781893553610%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=HILNjAqiw4X0uPvuZJ44Tu5rRfDZR0xm4cPEqQf1P2I%3D&reserved=0>).

In other words, your first stop should be the WHATWG. If directly
engaging with WHATWG doesn't go well for you, come to the HTML WG and we
can help. We're your escalation path.


Tess

Becky Gibson
Sr. Accessibility Strategist
Knowbility.org<https://nam01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fknowbility.org%2F&data=04%7C01%7Ciali%40ets.org%7C80c5188208ef4a177b7008d8712c3077%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637383781893563563%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=rSgRa8eUxemJygM09JoL7V89eBvrEpmAUegnDy710a8%3D&reserved=0>

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Co-Chair, Accessible Platform Architectures http://www.w3.org/wai/apa<https://nam01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.w3.org%2Fwai%2Fapa&data=04%7C01%7Ciali%40ets.org%7C80c5188208ef4a177b7008d8712c3077%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637383781893563563%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=LiE1f6HOovnBIkhIk2gEiXg%2FnU2ocQ4mWSYTBvSZCAw%3D&reserved=0>



--

Janina Sajka
https://linkedin.com/in/jsajka<https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flinkedin.com%2Fin%2Fjsajka&data=04%7C01%7Ciali%40ets.org%7C80c5188208ef4a177b7008d8712c3077%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637383781893573519%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=jNQhhJeDtPHzgGj178BZrzpQC6%2FGb0W%2FuYcgR4MJbVU%3D&reserved=0>

Linux Foundation Fellow
Executive Chair, Accessibility Workgroup: http://a11y.org<https://nam01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fa11y.org%2F&data=04%7C01%7Ciali%40ets.org%7C80c5188208ef4a177b7008d8712c3077%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637383781893573519%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=fKfxpD7ZVCAT73zYpT2Vq1Pr1q5jBOkyI8bc40MDcmM%3D&reserved=0>

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Co-Chair, Accessible Platform Architectures http://www.w3.org/wai/apa<https://nam01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.w3.org%2Fwai%2Fapa&data=04%7C01%7Ciali%40ets.org%7C80c5188208ef4a177b7008d8712c3077%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637383781893573519%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=G%2Fs1vMSdEK9h8%2FslUrxS%2FIp%2FewYG1B8U1T2thuLBZk0%3D&reserved=0>


--

Janina Sajka
https://linkedin.com/in/jsajka<https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flinkedin.com%2Fin%2Fjsajka&data=04%7C01%7Ciali%40ets.org%7C80c5188208ef4a177b7008d8712c3077%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637383781893583477%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=QT4r2N0qWBL4NTkAPmdRnX59gtPE6Z%2FA4ujr6AFBvHU%3D&reserved=0>

Linux Foundation Fellow
Executive Chair, Accessibility Workgroup: http://a11y.org<https://nam01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fa11y.org%2F&data=04%7C01%7Ciali%40ets.org%7C80c5188208ef4a177b7008d8712c3077%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637383781893583477%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=tFK4ba%2BLrgJiqyLKQ7BqYZqzaId4Lnvp%2FBj5ZStV4gA%3D&reserved=0>

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Co-Chair, Accessible Platform Architectures http://www.w3.org/wai/apa<https://nam01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.w3.org%2Fwai%2Fapa&data=04%7C01%7Ciali%40ets.org%7C80c5188208ef4a177b7008d8712c3077%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637383781893593433%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=9BFMftFcCna4%2FQUIXDiGIJh2TflPyoU0CN7HrwSAZtQ%3D&reserved=0>


Becky Gibson
Sr. Accessibility Strategist
Knowbility.org<https://nam01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fknowbility.org%2F&data=04%7C01%7Ciali%40ets.org%7C80c5188208ef4a177b7008d8712c3077%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637383781893593433%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=FgfhtZZdM0GsKbSvmzeXGH0nirrD20MtiB85nlCsbAw%3D&reserved=0>

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Co-Chair, Accessible Platform Architectures http://www.w3.org/wai/apa<https://nam01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.w3.org%2Fwai%2Fapa&data=04%7C01%7Ciali%40ets.org%7C80c5188208ef4a177b7008d8712c3077%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637383781893593433%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=9BFMftFcCna4%2FQUIXDiGIJh2TflPyoU0CN7HrwSAZtQ%3D&reserved=0>



Becky Gibson | Sr. Accessibility Strategist
Knowbility.org<https://nam01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fknowbility.org%2F&data=04%7C01%7Ciali%40ets.org%7C80c5188208ef4a177b7008d8712c3077%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637383781893603398%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=3vN6rWYIOcqlQmc%2FJ9Va6quvhKKEP%2BzpmZURETcRSjE%3D&reserved=0>
becky@knowbility.org<mailto:becky@knowbility.org>
Pronouns: she/her/hers





Becky Gibson | Sr. Accessibility Strategist
Knowbility.org<https://nam01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fknowbility.org%2F&data=04%7C01%7Ciali%40ets.org%7C80c5188208ef4a177b7008d8712c3077%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637383781893603398%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=3vN6rWYIOcqlQmc%2FJ9Va6quvhKKEP%2BzpmZURETcRSjE%3D&reserved=0>
becky@knowbility.org<mailto:becky@knowbility.org>
Pronouns: she/her/hers





Becky Gibson | Sr. Accessibility Strategist
Knowbility.org<https://nam01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fknowbility.org%2F&data=04%7C01%7Ciali%40ets.org%7C80c5188208ef4a177b7008d8712c3077%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C637383781893613344%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=k%2FZvHz79rWvyblr4lgk1z3DJ3ORhujW4%2BC%2Fsz8y64mM%3D&reserved=0>
becky@knowbility.org<mailto:becky@knowbility.org>
Pronouns: she/her/hers





________________________________

This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited.


Thank you for your compliance.

________________________________