Initial review of policy permissions

I reviewed the latest editor’s draft of the  Policy Permissions spec ( ) for accessibility concerns. From the abstract, "This specification defines a mechanism that allows developers to selectively enable and disable use of various browser features and APIs”. I have no concerns with the mechanism of specifying the policy.  I do have some concerns with the actual policies that are referenced in an associated document, Policy Controlled Features (https://github.com/w3c/webappsec-permissions-policy/blob/main/features.md <https://github.com/w3c/webappsec-permissions-policy/blob/main/features.md>).  

On reviewing this list a few jump out at me for accessibility implications:
ambient-light-sensor
autoplay
display-capture
execution-while-not-rendered
execution-while-out-of-viewport
microphone
navigation-override
usb
To be honest, I did not read the spec associated with each of these items. At the very least I believe that there should be an accessibility statement in one of the documents that there must be consideration that features that are used by people with disabilities should not be turned off without consideration of the implications. Web pages that turn off these policies should have some mechanism for the user to request a bypass. Although, this is a tricky issue since some may be security risks and a major discussion point of the Policy Permissions specification concerned security. 

I could use some help diving into this issue further and it is worthy of discussion within our larger group. 


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