Re: Agenda: APA Weekly Teleconference; Wednesday 20, January 17:00 UTC

Hello all,

You can find the minutes on the web at https://www.w3.org/2021/01/20-apa-minutes.html and they’re repeated below in text form for convenience.

Best regards,


Matthew

  – DRAFT –
Accessible Platform Architectures Working Group Teleconference


20 January 2021

IRC log. <https://www.w3.org/2021/01/20-apa-irc>


    Attendees

Present
    becky, Ela, IanPouncey, Jonny_James, JPaton, Léonie (tink),
    Matthew_Atkinson, paul_grenier
Regrets
    Amy Carney, Gottfried Zimmerman, Janina Sajka
Chair
    becky
Scribe
    Matthew_Atkinson


    Contents

1. Agenda Review & Announcements <#t01>
2. APA Rechartering Begins
    -https://raw.githack.com/w3c/apa/charter-2021/charter.html <#t02>
3. Task Force Updates <#t03>
4. FAST Progress <#t04>
5. New Charters Review
    https://github.com/w3c/strategy/issues?q=is%3Aissue+is%3Aopen+label%3A%22Horizontal+review+requested%22%22

    <#t05>
6. new on TR http://www.w3.org/TR/tr-status-drafts.html <#t06>
7. CSS Checkin (Amy) https://github.com/w3c/css-a11y/issues <#t07>
8. Actions Checkin (Specs)
    https://www.w3.org/WAI/APA/track/actions/open <#t08>
9. Horizontal Review Issues Tracker
    https://w3c.github.io/horizontal-issue-tracker/?repo=w3c/a11y-review

    <#t09>
10. Other Business <#t10>


    Meeting minutes


      Agenda Review & Announcements

Becky: RQTF is having a joint meeting with Web of Things next wednesday
at 9am ET.

<MichaelC> https://github.com/w3c/personalXR

<https://github.com/w3c/personalXR>

<MichaelC> Personalization demo repo <https://github.com/w3c/personalXR>


      APA Rechartering Begins
      -https://raw.githack.com/w3c/apa/charter-2021/charter.html

      <https://raw.githack.com/w3c/apa/charter-2021/charter.html>

Becky: Some Personalization and Pronunciation info has been added.
Please review (before next week).


      Task Force Updates

Becky: Personalization didn't meet (public holiday); getting ready for CR.

Paul: Pronunciation: Making progress on draft towards FPWD. Seeking
partners/implementors to demonstrate the case. Need browsers' help to
provide the needed info in the accessibility tree.


      FAST Progress


      New Charters Review
     https://github.com/w3c/strategy/issues?q=is%3Aissue+is%3Aopen+label%3A%22Horizontal+review+requested%22%22

      <https://github.com/w3c/strategy/issues?q=is%3Aissue+is%3Aopen+label%3A%22Horizontal+review+requested%22%22>

<MichaelC> PROPOSED Pointer Events Working Group Charter
<https://w3c.github.io/charter-drafts/pe-2020.html>

Michael: We should comment that IndieUI is closed

Becky & MIchael: Looks good to go.

Léonie: Will check with Patrick and confirm.

<MichaelC> PROPOSED Service Workers Working Group Charter
<https://w3c.github.io/charter-drafts/sw-2020.html>

Michael & Becky: this seems like a low-level API. (We don't need to be
listed as a liaison.)

Becky: We'll get to review specs as they emerge.


      new on TR http://www.w3.org/TR/tr-status-drafts.html

      <http://www.w3.org/TR/tr-status-drafts.html>

Michael: There are some from Internationalization that we are aware of
and do not need to review.

<MichaelC> CSS Cascading and Inheritance Level 5
<https://www.w3.org/TR/css-cascade-5/>

<MichaelC> Arabic and Persian Gap Analysis
<https://www.w3.org/TR/alreq-gap/>

<MichaelC> The Responsible Use of Spatial Data
<https://www.w3.org/TR/responsible-use-spatial/>

Ian: We don't need to review CSS Cascading and Inheritance Level 5

Michael: Anything relevant in spatial data?

Becky: Could it be used to particularly identify a disability/assistive
technology?

Michael: There are existing sections on privacy/ethics that seem to
cover this. We know about beacons used as assistive tech; seem to be
covered by the above.

Becky: Sounds OK. [no objections from group]]


      CSS Checkin (Amy) https://github.com/w3c/css-a11y/issues

      <https://github.com/w3c/css-a11y/issues>

Becky: Amy sent regrets but posted to the list.

<becky> Box Model Module Level 3 (https://www.w3.org/TR/css-box-3/

<https://www.w3.org/TR/css-box-3/> appears to have no issues. There have
only been a few additions since CSS2:

<becky> Adapting the prose slightly to account for vertical writing modes.

<becky> Cross-linking to relevant concepts in [css-break-3] and
[css-backgrounds-3].

<becky> Defining the non-applicability of margin, padding and their
longhands to ruby base containers and ruby annotation containers(at risk).

<becky> Providing a centralized common definition of keywords that
reference the various box edges for use in properties defined outside
this spec (e.g. background-clip) to avoid repetition (and the resulting
inevitable synchronization errors).

Ian: Nothing APA-specific here.


      Actions Checkin (Specs)
      https://www.w3.org/WAI/APA/track/actions/open

      <https://www.w3.org/WAI/APA/track/actions/open>

<Zakim> tink, you wanted to update on the Pointer Events charter.

Léonie: Update, checked with Patrick and no APA-specific concerns in the
Pointer Events charter.


      Horizontal Review Issues Tracker
      https://w3c.github.io/horizontal-issue-tracker/?repo=w3c/a11y-review

      <https://w3c.github.io/horizontal-issue-tracker/?repo=w3c/a11y-review>

<MichaelC> Consider specifying heuristics for when <ul> represents a
list <https://github.com/whatwg/html/issues/6218>

Léonie: This arose due to changes in VoiceOver's heuristics that removed
list semantics in some circumstances (e.g. lists of one item). The
question is should this be standardized as a browser heuristic. It is a
relatively contentious issue. (Personal view: hearing there's a list of
one item is not damaging. This is not harmful like layout tables are.)

Michael: Should we keep this as an issue that APA is tracking?

Léonie: It's worth following. There isn't much public data on this yet.

Michael: By default, the next time we'll see this issue is when it's
concluded and proposed to be closed.

--
Matthew Tylee Atkinson
--
Senior Accessibility Engineer
The Paciello Group
https://www.paciellogroup.com

A Vispero Company
https://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.