W3C home > Mailing lists > Public > public-webappsec@w3.org > July 2021

Re: [permissions-policy] Accessibility concerns

From: Daniel Veditz <dveditz@mozilla.com>
Date: Wed, 30 Jun 2021 17:13:47 -0700
Message-ID: <CADYDTCBkHHpnFDPjojEvciKPDFOfGJfV229Tnpf-9Xv0ns5huA@mail.gmail.com>
To: Becky Gibson <gibson.becky@gmail.com>
Cc: WebAppSec WG <public-webappsec@w3.org>, W3C WAI Accessible Platform Architectures <public-apa@w3.org>
There's a link to the GitHub issue tracker right below the "feedback" line;
issues are perfectly fine. Especially if they have an issue-like resolution
tag which makes them sound more like a task.

The Permissions described in the spec apply to web documents and
applications, not the user agent nor any extensions or assistive technology
installed locally. They are a way for a document to declare a technical
enforcement to allow or disallow the use of certain features in their own
site's code that they would otherwise do through local code-review rules or
developer guidelines. If an adaptive feature is blocked by Permission
Policy it is little different from a site choosing not to use it in the
first place. Wouldn't the problem be with the site authors and not this
specification?

The default and inherited values for the various policies are not specified
by the Permission Policy spec but come from the individual specs that
define those features. Those specs are linked from the companion registry
https://github.com/w3c/webappsec-permissions-policy/blob/main/features.md

On Wed, Jun 30, 2021 at 2:23 PM Becky Gibson <gibson.becky@gmail.com> wrote:

> 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 policies. 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.
>
> Have you taken that this into consideration when drafting this
> specification?
>
> (Normally I would file an issue in your github respository and label it
> with a11y-needs-resolution but your spec requested feedback via this
> mechanism.)
>
>
> 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
>
>
>
Received on Thursday, 1 July 2021 00:14:27 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 1 July 2021 00:14:28 UTC