W3C home > Mailing lists > Public > public-apa@w3.org > June 2021

Re: Review and discussion of permissions and permissions policy

From: Lionel Wolberger <lionel@userway.org>
Date: Wed, 30 Jun 2021 09:10:57 +0300
Message-ID: <CAHOHNHcvyVSLFj9SPFWHSn4RocstQ6AtywKZ5YnuAEPjXrpdJA@mail.gmail.com>
To: Becky Gibson <gibson.becky@gmail.com>
Cc: W3C WAI Accessible Platform Architectures <public-apa@w3.org>
Everything's here. Editing for clarity, and commenting inline:


The Accessible Platform Architetures (APA) <<<Typo

We are concerned that users may rely on some of the features (
https://github.com/w3c/webappsec-permissions-policy/blob/main/features.md)
controlled via these policies to obtain full access to a site.

<<< I suggest rearranging the clauses for clarity

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.

>>> I suggest being a bit more verbose, in the interest of educating the
reader

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 or >>> and/or their >>> necessary
adaptations.

Have you taken that >>> this*>>>>  into consideration when drafting this
specification?
 * I have to grab my Eats Shoots and Leaves to justify why I think "this"
is more correct than "that"


On Wed, Jun 30, 2021 at 01:28 Becky Gibson <gibson.becky@gmail.com> wrote:

> I reviewed the Permissions (https://www.w3.org/TR/permissions/) and the
> Permissions Policy  (https://w3c.github.io/webappsec-permissions-policy/) specifications.
> I don’t believe we have concers with Permissions as this specification
> provides an infrastructure for interacting with browser permissions and
> notification of changes to permissions. Regarding Permissions Policy, I
> believe we agreed that we would like to ask for clarification about the
> accessibility implications of author removal of particular features. I’ve
> drafted the following statement for review by the group. It could use some
> additional word-smithing.
>
> 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 may rely on some of the features (
> https://github.com/w3c/webappsec-permissions-policy/blob/main/features.md)
> controlled via these policies to obtain full access to a site. For example,
> access to an ambient-light-sensor to normalize brightness or contrast. Or
> reliance on various media capture features necessary for proper functioning
> of assistive technology or necessary adaptations. Have you taken that into
> consideration when drafting this specification? Can you provide guidance
> for implementors with respect to accessibility considerations or possible
> overrides for accommodation?
>
>
>
>
>
> Becky Gibson
> https://www.linkedin.com/in/beckygibsona11y/
>
> The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
> Co-Chair, Accessible Platform Architectures http://www.w3.org/wai/apa
>
>
> --


Lionel Wolberger
COO, UserWay Inc.
lionel@userway.org
UserWay.org <http://userway.org/>
<https://userway.org>[image: text]
Received on Wednesday, 30 June 2021 06:11:21 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:23:08 UTC