Authoring with accessible web documents in mind.

Authoring with accessible web documents in mind.

The case for web documents.

• Most accessible.
• Most flexible.
• Most sustainable.

Do one thing and do it well

• Word etc.
• LaTeX etc.
• Markdown etc.

It doesn't matter which as long as you do a good job with it.

Keep it simple, stupid.

• Native content -- stay in your tool
• Simple layout -- do less, get more
• Convert early, convert often

Get from here to there

1. Word => pandoc
2. LaTeX => pandoc, latexml (also: tex4ht, plastex, tralics)
3. Markdown => dozens, e.g., pandoc, Writage (MS Word plugin)

Getting started with Pandoc

• Web demo
• Simple example usage:: pandoc --self-contained -s example.docx -t html -o example.html.
• Complex example: pandoc -s -S --toc -c pandoc.css -A footer.html example.tex -o example.html
• Example docx

Getting started with latexml

Jump in: latexml doc.tex | latexmlpost --dest=doc.html

• Web demo
• Example files
• Manual
• Advanced: authoring a "binding"(package)

Getting started with Markdown

# I'm a top-level heading
I'm a paragraph followed by a list.
* item 1
* item 2
![alt text](link/to/image)

• Quick start: StackEdit (web-based editor)
• Google "markdown editor" (460,000 hits)

Checking results

1. Learn to use a screenreader (NVDA, VoiceOver, Orca)
2. Learn automated tools (tota11y, aXe, ChromeLens) and their limitations.

Have
fun!