Skip to content

Preserving document semantics when rendering to HTML #628

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
palemieux merged 3 commits into from
Jan 12, 2026
Merged

Preserving document semantics when rendering to HTML #628

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
d1b3c90
Preserving document semantics when rendering to HTML
palemieux Dec 19, 2025
f41c689
Merge branch 'main' into issues/0626-font-variant-a11y
palemieux Jan 7, 2026
7522f2f
Address comments
palemieux Jan 12, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 16 additions & 1 deletion imsc1/spec/ttml-ww-profiles.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3679,7 +3679,7 @@ <h2>Forced content</h2>
</section>

<section class='appendix' id='wcag-maur-applications'>
<h2>WCAG and MAUR Considerations</h2>
<h2>Accessibility Considerations</h2>

<section class='appendix' id='wcag-applications'>
<h3>WCAG Considerations</h3>
Expand Down Expand Up @@ -3714,6 +3714,20 @@ <h4>Success Criteria 3.1.1 Language of Page and 3.1.2 Language of Parts</h4>
<a data-cite="ttml2#content-attribute-xml-lang"><code>xml:lang</code></a>.</p>
</section>

<section id='mapping-to-html' class="appendix informative">
<h4>Success Criterion 1.3.1 Info and Relationships</h4>

<p>Success Criterion <a data-cite="!WCAG22#linfo-and-relationships">1.3.1</a> at [[!WCAG22]] is intended to ensure that
information and relationships that are implied by visual or auditory formatting are preserved when the presentation format
changes.</p>

<p>As an example in the context of this specification, implementations should, when rendering a <a>Document Instance</a>
to [[HTML]] with [[CSS]] styling, ensure that the resultant [[HTML]] document can be understood by assistive technologies
even when a user style sheet is substituted for the style sheet provided by the author. For instance, when rendering
<code>tts:fontVariant</code>, the use of CSS <code>vertical-align</code> property alone might not be sufficient for
assistive technology to identify that the glyphs concerned are superscript or subscript.</p>
</section>

</section>

<section id='maur-applications' class="appendix informative">
Expand All @@ -3727,6 +3741,7 @@ <h3>MAUR Considerations</h3>
vision impairment who also requires caption support might be able to request that all captions are displayed in the lower
third of the screen with a large font, altering in the process the layout and styling specified by the author.</p>
</section>

</section>

<section id='sample-instance' class="appendix informative">
Expand Down