Re: [w3c/picture-in-picture] Who is responsible for the user interface for PiP? (#179)

APA folks,
Here is my draft response to a request for more information about providing an Accessibility statement within the Picture in Picture specification (https://www.w3.org/TR/2020/WD-picture-in-picture-20200130/ <https://www.w3.org/TR/2020/WD-picture-in-picture-20200130/>).  I wanted the group to review before officially responding.

thanks,
-becky



You can view the Payment Request API (https://www.w3.org/TR/payment-request/ <https://www.w3.org/TR/payment-request/>) for an example accessibility statement. 

The Screen Orientation API working draft includes a section on interaction with WCAG 2.1 (https://www.w3.org/TR/screen-orientation/#interaction-with-web-content-accessibility-guidelines <https://www.w3.org/TR/screen-orientation/#interaction-with-web-content-accessibility-guidelines>). 

Here is an example of a statement that was drafted for the Push API specification:

Accessibility Considerations (Informative)

Push API features introduce a number of needs for a "Do Not Disturb"
functionality in various web applications, whether accessed via mobile
device or desktop browser. This functionality should be addressed by the
Web Notifications specification. Web Notifications currently does not
provide this feature but an issue has been filed requesting the feature:

[URI of issue available soon]

Meanwhile, until the use cases described in this issue are appropriately
addressed, implementers of this specification should be aware that
accessibility problems might be triggered by implementations of this
specification and attempt to minimize their impact.

There are a few success criteria that would apply to the user interface for picture in picture. 
2.1.1 Keyboard (https://www.w3.org/TR/WCAG21/#keyboard <https://www.w3.org/TR/WCAG21/#keyboard>) - must work with the keyboard
1.3.1 Info and Relationships (https://www.w3.org/TR/WCAG21/#info-and-relationships <https://www.w3.org/TR/WCAG21/#info-and-relationships>) - must be programmatically determinable
2.4.6 Headings and Labels (https://www.w3.org/TR/WCAG21/#headings-and-labels <https://www.w3.org/TR/WCAG21/#headings-and-labels>) - labels for the controls must be descriptive
3.3.2 Labels or Instructions (https://www.w3.org/TR/WCAG21/#labels-or-instructions <https://www.w3.org/TR/WCAG21/#labels-or-instructions>) - labels must exist




> On Jun 11, 2020, at 3:12 AM, François Beaufort <notifications@github.com> wrote:
> 
> 
> Thanks for raising this issue @becka11y <https://github.com/becka11y>!
> I'd be happy to address those in the spec. Do you have examples of other web APIs specifications that demonstrate how to meet the requirements of WCAG 2.1? Would you be able us reaching that goal?
> 
> FYI @mounirlamouri <https://github.com/mounirlamouri>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub <https://github.com/w3c/picture-in-picture/issues/179#issuecomment-642457962>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACN4C3ZTZM5GL6CZXP3VNTRWB7VRANCNFSM4MD7WJKA>.
> 




Becky Gibson | Sr. Accessibility Strategist
Knowbility.org
becky@knowbility.org