Skip to content

Add example section for visual markup explanation to G96 #5073

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

Open
CharlesBelov wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Add example section for visual markup explanation to G96 #5073

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1b34fdf
Add example section for visual markup explanation
CharlesBelov Apr 16, 2026
a940a87
Merge branch 'main' into patch-1
patrickhlauke Apr 28, 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
6 changes: 5 additions & 1 deletion techniques/general/G96.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -93,6 +93,10 @@ <h4>The <abbr title="Cascading Style Sheets">CSS</abbr></h4>
}</code></pre>
</section>
</section>
<section class="example">
<h3>Visual markup with semantic meaning has explicit text explaining the meaning</h3>
<p>A redline document designates deleted text with strikethrough and added text with double underline. Deletions are preceded by the text "[begin deletion]" and followed by the text "[end deletion]. Additions are preceded by the text "[begin addition]" and followed by the text "[end addition].</p>

@patrickhlauke patrickhlauke Apr 28, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

shouldn't additions/deletions use <ins> and <del> ? or are you concerned about whether or not AT currently announce/expose these?

@CharlesBelov CharlesBelov May 5, 2026 •
edited
Loading

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@patrickhlauke I do have concerns about whether <ins> and <del> are read by screen readers, an area I don't have expertise in, but the main issue is with publishing the document to the web as a PDF, which my understanding is that WCAG covers.

If I use track changes in Word to track insertions and deletions, when it is saved as PDF, the deleted text is removed as is the markup that there has been an addition. There doesn't appear to be any option in Word to Save to PDF with the tracked changes intact.

If I print, the tracked changes are there. But printing to PDF does not produce accessibility tags.

In the case of my agency, the San Francisco Municipal Transportation Agency, we don't use track changes to create these PDF files. Instead, we apply strikethrough to deleted content and a particular font and underscores to inserted text.

There is the further complication that additions and deletions can - admittedly rarely - be done by both the SFMTA Board and by the Board of Supervisors of the City and County of San Francisco. In such cases, we have two different deletion styles and two different insertion styles, something which <ins> and <del> can't handle semantically.

None of this markup makes it from Word to PDF tags when saving as PDF. Our only available workaround is to explicitly show the additions and deletions as verbiage in a conforming alternative document.

</section>
</section>
<section id="tests">
<h2>Tests</h2>
Expand All @@ -117,4 +121,4 @@ <h2>Related Techniques</h2>
<h2>Resources</h2>
</section>
</body>
</html>
</html>