<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED DUPLICATE - Export slides as single HTML only shows text, no images" href="https://bugs.documentfoundation.org/show_bug.cgi?id=143181#c7">Comment # 7</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED DUPLICATE - Export slides as single HTML only shows text, no images" href="https://bugs.documentfoundation.org/show_bug.cgi?id=143181">bug 143181</a> from <a class="email" href="mailto:stephane.guillou@member.fsf.org" title="stragu <stephane.guillou@member.fsf.org>"> stragu</a> <pre>(In reply to V Stuart Foote from <a href="show_bug.cgi?id=143181#c6">comment #6</a>) > Observed behavior with no image of slides with the legacy HTML export dialog > is valid. But the entire HTML export should have been removed as in dupe. > PDF is the valid means of distributing ODF documents and presentations. > > Currently if images were embedded they would likely be base64 encoded PNG > bitmap--but done as an SVG could be browser rendered, but <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED WONTFIX - HTML EXPORT: Please integrate impress.js / bespoke.js in html Export or at least add key navigation" href="show_bug.cgi?id=100498">bug 100498</a> quashed > that. > > The HTML 4.0.1 Transitional based filter needs to go completely. > > Something else, HTML 5 and ARIA content that is WCAG 2.1 compliant--probably > SVG graphic based, would be a nice enhancement but it belongs in an > extension. > > This, adding base64 encoded bitmap images to HTML 4 markup, is a clear => WF > > *** This bug has been marked as a duplicate of <a class="bz_bug_link bz_status_NEW " title="NEW - Drop html export wizard" href="show_bug.cgi?id=105303">bug 105303</a> *** Thanks, Stuart. Just one thought: if HTML is to disappear as an option, and given that PDF gets a lot of criticism accessibility-wise, what would then remain for an accessible export? A third-party extension that might not ever be created? I am very new to how features are judged to belong to features or core, but I don't think an accessible SVG (or whatever else accessible format) export should be an optional extension that might or might not exist. Am I missing something?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>