- From: Rob Sanderson via GitHub <sysbot+gh@w3.org>
- Date: Wed, 18 May 2016 16:09:23 +0000
- To: public-annotation@w3.org
azaroth42 has just created a new issue for https://github.com/w3c/web-annotation: == Add accessibility to the model & vocab == Rob, Benjamin, Ivan reviewed the specifications, especially in conjunction with the IDPF profile of OA, and noticed that: * Accessibility is not mentioned, and is as important as i18n * There is an existing pattern from IDPF that we could use * It is the same pattern as our approved audience addition (also from IDPF) * It adds only a single new key (accessibilityFeature) * It's cross-domain -- every domain needs a11y, and different communities would likely come to different patterns without guidance. Proposal: Use schema.org/accessibilityFeature as a mechanism for expressing accessibility features of resources, including Body, Target and TextualBody. There would be no recommendation of what the values are (as they're only maintained in a wiki page). This just provides a single hook for managing the inclusion of the features. Example: ``` { "@context": "http://www.w3.org/ns/anno.jsonld", "id": "http://example.org/anno/1", "type": "Annotation", "body": { "type": "TextualBody", "value": "<span style=\"font-size: 48pt\">A Big Comment</span>", "format": "text/html", "language": "en", "accessibilityFeature": "largePrint" }, "target": { "id": "http://example.org/videos/1", "type": "Video", "accessibilityFeature": "captions" } } ``` Please view or discuss this issue at https://github.com/w3c/web-annotation/issues/231 using your GitHub account
Received on Wednesday, 18 May 2016 16:09:25 UTC