– DRAFT –
Accessible Platform Architectures Working Group Teleconference

Agenda Review & Announcements

WAI leadership transition

matatk: WAI changes in progress, Judy moving on.
… MichaelC our staff contact is assuming a bigger role in WAI and will update us further in future
… see the Blog for more details
… Janina returns next week.

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

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

ElementInternals's ARIAMixin

<Roy> - issue: https://github.com/whatwg/html/issues/8442

<Roy> - tracking: https://github.com/w3c/a11y-review/issues/142

[mediaqueries] Suggestion: "prefers-pointer-location"

<Roy> - issue: https://github.com/w3c/csswg-drafts/issues/7872

<Roy> - tracking: https://github.com/w3c/a11y-review/issues/141

Lionel_Wolberger: This relates to i18n and LTR/RTL issues

matatk: I18n is tracking

Lionel_Wolberger: Handedness, right and/or left, has rarely come up as a digital accessibility issue. This seems to be a first
… are there other handedness issues?

matatk: This did come up in XR

PaulG: The location of the controls on the page does seem significant

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

Portable Network Graphics (PNG) Specification (Third Edition)

<Roy> - spec: https://www.w3.org/TR/png-3/

<Roy> - tracking: https://www.w3.org/WAI/APA/wiki/Portable_Network_Graphics_(PNG)_Specification_(Third_Edition)

<Roy> - Self review: https://github.com/w3c/a11y-request/issues/42

matatk: PNG did come up as prior art, as a method of incorporating meta-data, when we were looking at SVG native

CSS View Transitions Module Level 1

<Roy> - spec: https://www.w3.org/TR/css-view-transitions-1/

<Roy> - tracking: https://www.w3.org/WAI/APA/wiki/CSS_View_Transitions_Module_Level_1

matatk: This is the spec behind the new Chrome page transitions feature
… pages move from one to another, without an obvious page load
… reminding APA members, we have many CSS specs to review

Lionel_Wolberger: Since there is a page transition involved, we would need to pay close attention to the way the new page is experienced by a screen reader user

PaulG: The spec is mostly visual involving a screenshot (not certain): but I recall it is purely visual, and should not affect the underlying semantics that screen readers rely upon

Fazio: COGA is concerned with the doorway effect, regarding memory compartmentalization & boundary markers.
… suddenly changing a page can trigger the Doorway Effect, so this spec may aid people who are sensitive to that effect

<Fazio> Good to minimize doorway effect and help cognitive accessibility

Fazio: to minimize doorway effect and help cognitive accessibility

ACTION: Paul Review CSS View Transitions

<trackbot> Created ACTION-2331 - Review css view transitions [on Paul Grenier - due 2022-11-09].

<Roy> https://www.w3.org/WAI/APA/wiki/CSS_View_Transitions_Module_Level_1

Scroll-linked Animations

<Roy> - spec: https://www.w3.org/TR/scroll-animations-1/

<Roy> - tracking: https://www.w3.org/WAI/APA/wiki/Scroll-linked_Animations

matatk: We likely want to ensure that this conforms with 'prefers reduced motion'

PaulG: This type of scroll may have originated with the Infographics trend of a while ago, where scrolling advanced the (animated) on-screen story
… This technology is not new, just enabling what happened before via JavaScript, can now happen by scrolling
… all accessibility considerations such as parallax effect (a background moving faster than a foreground) which have adverse effect on people with vestibular disorders
… will still apply when scroll controls the animation

matatk: Agree. And CSS has its own accessibility considerations section

matatk: The overall trend of migrating things that were previously scripted, into the CSS world

PaulG: This may improve things for developers, as scripting can cause elements to not be present in the DOM and AX tree
… while with this CSS method the elements would be present

Dangling Spec Review Cleanup: https://www.w3.org/WAI/APA/wiki/Category:Spec_Review_Assigned

<matatk> Also: https://www.w3.org/WAI/APA/wiki/Category:Spec_Review_Active

matatk: Reminding APA members, you don't need to be an expert in the spec, you just to have an eye for the A11Y potential issues.
… You can always ask questions of the spec author
… we would like to focus on the Web of Things architecture

WoT Architecture 1.1

<matatk> URL: https://www.w3.org/WAI/APA/wiki/Web_of_Things_(WoT)_Architecture

<Roy> https://www.w3.org/WAI/APA/wiki/Web_of_Things_(WoT)_Architecture_1.1

<Roy> - TR: https://www.w3.org/TR/wot-architecture11/

<Roy> - issue: https://github.com/w3c/wot-architecture/issues/796

<Roy> - tracking: https://www.w3.org/WAI/APA/wiki/Web_of_Things_(WoT)_Architecture_1.1

<Roy> - ping: Horizontal Review for CR

<matatk> TPAC conversation: https://www.w3.org/WAI/APA/wiki/Meetings/TPAC_2022#Web_of_Things_Accessibility

WebXR Augmented Reality Module - Level 1

<matatk> URL: https://www.w3.org/WAI/APA/wiki/WebXR_Augmented_Reality_Module_-_Level_1

matatk: The TPAC meeting aligned our vocabulary with them very well, e.g., they accepted the 'middleware' term
… WebXR CG and WG are aware of XAUR, so this just needs a quick looking over

Spec Tracking Wiki Reminder https://www.w3.org/WAI/APA/wiki/Category:Spec_Review

CSS Update (Paul) https://github.com/w3c/css-a11y/issues

PaulG: No updates, nothing stands out as needing APA attention

Task Force & Deliverables Updates

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

<matatk> To check your own actions: https://www.w3.org/2005/06/tracker/users/my

Other Business

<Roy> https://www.w3.org/2022/09/06-wot-minutes.html#t12

be done

matatk: Next week Janina is chair, thanks everyone for attending!@

rrsagent make minutes