w3c
include accessibility features description
HI!
It is required by law to be able to describe accessibility features of mobile applications, i. e. by European directive 2016/2102:
https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32016L2102&from=FR#d1e883-1-1
“1. […] For mobile applications, the accessibility statement shall be provided in an accessible format, using the model accessibility statement referred to in paragraph 2, and shall be available on the website of the public sector body that developed the mobile application concerned, or alongside other information available when downloading the application.”
Including at least a link to the accessibility statement will be helpful.
Thank you. Erwan
@ele-gall-ac-mineducation Interesting. So you’re envisioning this as purely a reference to the statement as a URL. Seems like we could include Privacy, Terms of Use, and others as well. Also possibly related: #2.
Perhaps a structure like this?
"legal": {
"accessibility_policy": "https://path.to/policy",
"terms_of_use": "https://path.to/policy",
"privacy_policy": "https://path.to/policy",
"license": "https://path.to/#license"
}
@diekus @jgw96 what do you think? Seems like these could be ingested into a catalog and made available to users, right? And the contents of the license element (if it’s an id reference, as is commonly the case) could even potentially be sucked into the product listing (and sanitized, naturally).
@marcoscaceres @kenchris @diekus @jgw96… any thoughts on this concept?
It would perhaps be useful in a store context, though I fear that putting this in the manifest gets into a "out of sight, out of mind" situation. As the information needs to be accessible from the app anyway (as presumedly all apps are used without requiring them to be installed from a store), and all apps are downloaded, the app should be providing links to this information from within the application itself.
For example, Github has this at the footer of every page:
