<becky> regrets, John Foliot, Gottfried Zimmermann, Fredrik Fischer, David Fazio, Paul Grenier, Amy Carney, Neil Soiffert
<scribe> scribe: janina
<MichaelC> https://github.com/w3c/apa/tree/wai-site
<becky> https://github.com/w3c/apa/tree/wai-site
<MichaelC> https://github.com/w3c/strategy/issues/274
Decision is no need to review WoT IG
mc: Accessibility Review, Tracker is what we should call it ...
... Nothing new ...
... Two issues waiting to close, but not ready; One Amy and one we decided to keep open
... 6 specs ...
<MichaelC> https://www.w3.org/TR/epub-a11y-eaa-mapping/
mc: Epub for EU A11y Mapping
... Claims they meet
bg: Suggests no need
[agreement]
<MichaelC> https://www.w3.org/TR/miniapp-manifest/
mc: Mini App Manifest
... previously looked at spec, this is registry of supplamentary members
bg: Notes that image labels are optional
mc: we should cross check
... Believe we got them to agree "authors should" ...
bg: will look
<MichaelC> https://www.w3.org/TR/did-cbor-representation/
mc: Plain CBOR ...
lw: Worth taking a look
bg: Do we really need?
lw: On second look, no need
[agreement]
<MichaelC> https://www.w3.org/TR/webnn/
mc: If we come up with use cases, it would help their model, but not top priority
jo: Agrees with janina to ask RQTF
<scribe> ACTION: IanPouncey: to review https://www.w3.org/TR/webnn/ [recorded in http://www.w3.org/2021/06/30-apa-minutes#action01]
<trackbot> Error finding 'IanPouncey'. You can review and register nicknames at <https://www.w3.org/WAI/APA/track/users>.
<MichaelC> ACTION: IanPouncey to review https://www.w3.org/TR/webnn/ [recorded in http://www.w3.org/2021/06/30-apa-minutes#action02]
<trackbot> Error finding 'IanPouncey'. You can review and register nicknames at <https://www.w3.org/WAI/APA/track/users>.
<MichaelC> ACTION: pouncey to review https://www.w3.org/TR/webnn/ [recorded in http://www.w3.org/2021/06/30-apa-minutes#action03]
<trackbot> Created ACTION-2296 - Review https://www.w3.org/tr/webnn/ [on Ian Pouncey - due 2021-07-07].
<MichaelC> action-2296: https://www.w3.org/WAI/APA/wiki/Web_Neural_Network_API
<trackbot> Notes added to action-2296 Review https://www.w3.org/tr/webnn/.
<MichaelC> https://www.w3.org/WAI/APA/wiki/CSS_Counter_Styles_Level_3
<MichaelC> https://www.w3.org/WAI/APA/wiki/Performance_Timeline_Level_2
mc: Performance Timeline requested review; we declined 5 years ago; what about now?
agreement we have no need
mc: CSS Counter Styles
[discussion ...]
ip: what's exposed is actually very limited
lw: as long as they're not changing that there is a list, and what's in it
bg: can add algo to transform that describes how to read out ...
ip: more api level
no need
<becky> https://lists.w3.org/Archives/Public/public-apa/2021Jun/0035.html
bg: Moving to Permissions Policy
... not concern with permission itself ...
... but we need clarification re author removal of various features that may affect a11y
... if one follows the features .... wasn't sure if e.g. normalize contrast might be turned off, or media capture features that might be at related
lw: edited only for readability -- but bg's examples very good
bg: will file the question and we'll keep our block while we await their review
<becky> https://www.w3.org/TR/permissions/
bg: we don't care that permissions provides the mechanism; but we do care that perm policy may block something a11y needs
lw: feel free to ask my rewrite of any ...
bg: into para, please!
janina: still need to post CfC on media hints -- will go to 14 July
<Lionel_Wolberger> Lionel gives an edited version back to Becky
<Lionel_Wolberger> The Accessible Platform Architetures (APA) working group has reviewed the latest working draft of the Permissions policy specification (https://w3c.github.io/webappsec-permissions-policy/) and we have some concerns. We are concerned that users, to assure their full, barrier-free access to a site. may rely on some of the features (https://github.com/w3c/webappsec-permissions-policy/blob/main/features.md) controlled via these pol[CUT]
janina: remind janina for i18n comment on sign lang
<Lionel_Wolberger> Lionel tries again
<Lionel_Wolberger> The Accessible Platform Architetures (APA) working group has reviewed the latest working draft of the Permissions policy specification (https://w3c.github.io/webappsec-permissions-policy/) and we have some concerns.
<Lionel_Wolberger> We are concerned that users, to assure their full, barrier-free access to a site. may rely on some of the features (https://github.com/w3c/webappsec-permissions-policy/blob/main/features.md) controlled via these policies.
<Lionel_Wolberger> For example, a user with vision limitations may rely upon access to an ambient-light-sensor to normalize brightness or contrast. Or a user may rely upon various media capture features necessary for proper functioning of assistive technology and/or their necessary adaptations.
<Lionel_Wolberger> Have you taken that this into consideration when drafting this specification?
<Lionel_Wolberger> Lionel is done
janina: Aceion-2259?
action-2259?
<trackbot> action-2259 -- Janina Sajka to Work with jf on review of media session standard https://www.w3.org/tr/mediasession/ -- due 2020-06-03 -- OPEN
<trackbot> https://www.w3.org/WAI/APA/track/actions/2259
jo: has ...
action-2269?
<trackbot> action-2269 -- Joshue O Connor to Review web of things profile https://www.w3.org/tr/wot-profile/ -- due 2020-12-09 -- OPEN
<trackbot> https://www.w3.org/WAI/APA/track/actions/2269
also ...
action-2274?
<trackbot> action-2274 -- Joshue O Connor to Review webxr layers api level 1 -- due 2020-12-16 -- OPEN
<trackbot> https://www.w3.org/WAI/APA/track/actions/2274
mc: are we filing comment?
jo: should I follow through to immersive ...
<Joshue108> Here are my review notes
<Joshue108> https://lists.w3.org/Archives/Public/public-apa/2021May/0040.html
jo: will take to rqtf for resolution pre CfC