Merge pull request #2813 from w3c/charles-edits

reidmore-online · web-flow · commit 596a1a593e1f · 2025-10-20T11:23:56.000-04:00
fixed out of date links missing ] and empty li.
diff --git a/wg-notes/fxl-a11y/index.html b/wg-notes/fxl-a11y/index.html
@@ -51,7 +51,7 @@
 	</head>
 <body data-include-format="markdown">
     <section id="abstract">
-        <p>An accessible fixed layout EPUB file is one that meets the accessibility requirements of the Web Content Accessibility Guidelines 2.x level AA [[wcag2]] and EPUB Accessibility 1.1 [[epub-a11y-11].This document, Fixed Layout Challenges and Best Practices, outlines the goals for EPUB accessible fixed layout ebooks while acknowledging the challenges unique to the fixed layout format.</p>
+        <p>An accessible fixed layout EPUB file is one that meets the accessibility requirements of the Web Content Accessibility Guidelines 2.x level AA [[wcag2]] and EPUB Accessibility 1.1 [[epub-a11y-11]].This document, Fixed Layout Challenges and Best Practices, outlines the goals for EPUB accessible fixed layout ebooks while acknowledging the challenges unique to the fixed layout format.</p>
     </section>
 
     <section id="sotd"></section>
@@ -884,7 +884,7 @@ <h3>Reading system accessibility requirements</h3>
             <section id="rs-a11y-requirements-metadata">
                 <h4>Display the accessibility metadata</h4>
 
-                <p>A reading system should provide information on accessibility metadata provided by the EPUB file in the OPF. Guidance for key information and proposed wordings are provided by the W3C Publishing Community Group Accessibility taskforce report: <a href="https://www.w3.org/2021/09/UX-Guide-metadata-1.0/principles/">User Experience Guide for Displaying Accessibility Metadata</a>.</p>
+                <p>A reading system should provide information on accessibility metadata provided by the EPUB file in the OPF. Guidance for key information and proposed wordings are provided by the W3C Publishing Community Group Accessibility taskforce report: <a href="https://www.w3.org/publishing/a11y/metadata-display-guide/guidelines/">Accessibility Metadata Display Guide for Digital Publications</a>.</p>
             </section>
 
             <section id="rs-a11y-requirements-at">
@@ -980,12 +980,10 @@ <h3>Alternative rendering methods</h3>
 
             <p>Alternative rendering methods for ebook content are methods of rendering beyond the visual, specifically auditory and tactile rendering (i.e., screen reader output or braille). While fixed layout formatting is often used to represent highly visual content, not all reading systems support visual display, and when visual display is available, screen sizes may be limited. Therefore, many reading systems might avoid supporting fixed layout content due to concerns about a poor reading experience. In addition to concerns about rendering, it must also be considered that many users face difficulties consuming and navigating complex fixed layout content. Alternative rendering methods should be considered as a replacement or addition to fixed layout rendering.</p>
 
-            <p>If the fixed layout publication does not conform to the recommendations made in this document, or WCAG [[wcag2]], providing alternate renderings of the content may result in an unusable or poor reading experience. Content that is not formatted in conformance with WCAG may result in output that has an incorrect reading order, broken sentences, or choppy pronounciation. The user should be informed if the content does not have accessibility metadata that would provide clarity on whether alternate renderings are supported, such as <code>dcterms:conformsTo</code> with a value for WCAG, or metadata values that conform to properties like <a href="https://w3c.github.io/publ-a11y/UX-Guide-Metadata/draft/principles/#supports-nonvisual-reading">Supports nonvisual reading</a> from the <a href="https://w3c.github.io/publ-a11y/UX-Guide-Metadata/draft/principles/">User Experience Guide for Displaying Accessibility Metadata</a>.</p>
+            <p>If the fixed layout publication does not conform to the recommendations made in this document, or WCAG [[wcag2]], providing alternate renderings of the content may result in an unusable or poor reading experience. Content that is not formatted in conformance with WCAG may result in output that has an incorrect reading order, broken sentences, or choppy pronounciation. The user should be informed if the content does not have accessibility metadata that would provide clarity on whether alternate renderings are supported, such as <code>dcterms:conformsTo</code> with a value for WCAG, or metadata values that conform to properties like <a href="https://w3c.github.io/publ-a11y/UX-Guide-Metadata/draft/principles/#supports-nonvisual-reading">Supports nonvisual reading</a> from the <a href="https://www.w3.org/publishing/a11y/metadata-display-guide/guidelines/">Accessibility Metadata Display Guide for Digital Publications</a>.</p>
 
             <p>Fixed layout publications that do conform to the recommendations in this document and WCAG 2 will likely be compatible with any alternate rendering features that may be built into reading systems.</p>
 
-            <p class="ednote">The <a href="https://w3c.github.io/publ-a11y/UX-Guide-Metadata/draft/principles/">User Experience Guide for Displaying Accessibility Metadata</a> is currently a draft document and is subject to change.</p>
-
             <p>There are ongoing discussions about transforming visual publications into reflowable textual content for complete AA compliance. While these are not in production yet, by creating our fixed layout with logical reading order, full image descriptions, and good semantics and structure where possible we are preparing our files in the best way for these future developments.</p>
 
             <aside class="issue" title="Open issues regarding alternative rendering">
@@ -1031,7 +1029,6 @@ <h2>Acknowledgements</h2>
             <li>Susan Neuhaus, (NeuStudio)</li>
             <li>Rachel Osolen, (NNELS)</li>
             <li>Gregorio Pellegrino, (Fondazione LIA)</li>
-            <li></li>
         </ul>
     </section>
 </body>
