Call for Consensus (CFC): Comments on review of Web App Manifest - Application Information Note

Colleagues: This is a Call for Consensus (CfC) to the Accessible Platform Architectures (APA) Working Group testing for agreement on an updated formal comment to Web App Manifest - Application Information Working Group Note <https://www.w3.org/TR/manifest-app-info <https://www.w3.org/TR/manifest-app-info>>.
The document was authored by The Web Applications Working group <https://www.w3.org/2019/webapps/ <https://www.w3.org/2019/webapps/>>.
An accessibility review was requested of the APA as part of our role in performing horizontal review of W3C documents for accessibility concerns.
It was reviewed by APA member Paul Grenier who proposed the following comment at https://lists.w3.org/Archives/Public/public-apa/2021Feb/0048.html <https://lists.w3.org/Archives/Public/public-apa/2021Feb/0048.html>. It has been updated below to include a link to the ARIA accessible description definition. 
On behalf of the APA working group, Paul Grenier reviewed the Web App Manifest - Application Information <https://www.w3.org/TR/manifest-app-info <https://www.w3.org/TR/manifest-app-info>> and provided the following comments:

   1. In label <https://www.w3.org/TR/manifest-app-info/#label-member <https://www.w3.org/TR/manifest-app-info/#label-member>>, this statement "For accessibility, authors are encouraged to provide a label for each screenshot." To help guide implementers, I would suggest adding a hint how this could be accomplished, "For example, most web applications could use the page title or main heading (h1) as the screenshot label."
   2. While the label acts as an accessible name, in this case a short description of the view, it might be helpful to include an accessible description <https://www.w3.org/TR/wai-aria-1.1/#dfn-accessible-description <https://www.w3.org/TR/wai-aria-1.1/#dfn-accessible-description>> supplementary information. This could be included for AT users to  uncover a full description of the screenshot. While not needed in most cases, it would be especially helpful for specialized apps or apps targeting a disabled audience. In "app stores" this could appear as a visible link to an additional description.
***Action to Take***
 
This CfC is now open for objection, comment, as well as statements of support via email. Silence will be interpreted as support, though messages of support are certainly welcome.
 
If you object to this proposed action, or have comments concerning this proposal, please respond by replying on list to this message no later than Wednesday 10, March 23:59 (Midnight) Boston Time.
 
NOTE: This Call for Consensus is being conducted in accordance with the APA Decision Policy published at: http://www.w3.org/WAI/APA/decision-policy <http://www.w3.org/WAI/APA/decision-policy>.
Becky & Janina
co-chairs APA Working Group

Becky Gibson
https://www.linkedin.com/in/beckygibsona11y/ <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 <http://www.w3.org/wai/apa>

Janina Sajka
https://linkedin.com/in/jsajka <https://linkedin.com/in/jsajka> 

Linux Foundation Fellow
Executive Chair, Accessibility Workgroup:    http://a11y.org <http://a11y.org/> 

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Co-Chair, Accessible Platform Architectures    http://www.w3.org/wai/apa <http://www.w3.org/wai/apa>