UNPKG

epubjs

Version:

Render ePub documents in the browser, across many devices

29 lines (25 loc) 1.71 kB
<?xml version="1.0" encoding="UTF-8" ?><!DOCTYPE html><html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> <title>The Untold Story: Metadata</title> <link rel="stylesheet" type="text/css" href="css/epub.css" /> <meta name="dat-origPath" value="/html/body" /><link rel="prev" href="./ch02s03_1.html" /><link rel="next" href="./ch03_0.html" /></head><body> <p data-origPath="/html/body/section/p[15]">Once you start getting creative with your content (e.g., using extensive scripted interactivity), you should engage experts as early on in the process as you can to ensure any statement you make remains true, however.</p> <p data-origPath="/html/body/section/p[16]">The other two codes provide contact information for the person(s) in your organization, or at a trusted intermediary, who can provide additional accessibility information:</p> <pre class="screen" data-origPath="/html/body/section/pre[5]">&lt;ProductFormFeature&gt; &lt;ProductFormFeatureType&gt;09&lt;/ProductFormFeatureType&gt; &lt;ProductFormFeatureValue&gt;99&lt;/ProductFormFeatureValue&gt; &lt;ProductFormFeatureDescription&gt; accessibility-officer@example.com &lt;/ProductFormFeatureDescription&gt; &lt;/ProductFormFeature&gt;</pre> <p data-origPath="/html/body/section/p[17]">If you’re providing educational materials, for example, you’ll want to provide educators a way to be able to contact you to determine whether your content will be accessible by students with various needs that may not be specifically addressed in your compatibility testing statement or in the available metadata properties. </p> </body> </html>