The Recurring Problem
Across Cisco and Everfox, accessibility and localization had to survive the entire publishing path. A source file could be semantically correct and still produce an inaccessible PDF or HTML page if a transform discarded meaning, generated the wrong navigation, or handled a table poorly. The final output, not the intention in the source, determined what a reader encountered.
Global output introduced a related set of constraints. A layout that behaved well in English could fail with right-to-left text, CJK typography, complex scripts, text expansion, or translated navigation. Accessibility and localization therefore belonged in the source model and transformation pipeline, not in separate cleanup projects at the end.
Where Systems Fail
The system needed to preserve meaning while changing formats. Alternative text, table descriptions, headings, navigation, reading order, generated labels, and page structures behaved differently across HTML and PDF. Authors also needed a practical way to supply the required information before publication. A checker could report a missing description, but it could not know what the image meant in context or invent the correct explanation.
Formatter choice created another tradeoff. Lower-cost tools could handle simpler output, but multilingual typography placed harder requirements on shaping, direction, and layout. The publishing stack had to be evaluated against the languages and accessibility behavior it actually needed to support.
How I Approach It
I added accessibility information such as alternative text and table descriptions to the structured source models, then reinforced those requirements with authoring controls and prompts. Writers encountered the decision while they still understood the content, instead of weeks later when a final output failed a check and the original context had faded.
XSLT and XSL-FO carried the semantics into tagged PDF and HTML. The transformation logic preserved reading order, heading and table structure, alternative text, bookmarks, and accessible navigation, while custom XSL-FO controlled page masters, headers and footers, keeps, tables, generated text, numbering, conditional layouts, branding, and global output. Antenna House Formatter was used where multilingual typography requirements exceeded what lower-cost alternatives could support reliably.
Automated checks were only one part of validation. I tested PDF and HTML with Section 508 tools and manually with JAWS, Windows Narrator, and Android TalkBack. PDF tagging, reading order, bookmarks, table structures, contrast, structural behavior, zoom and reflow, and publishing across more than 50 languages—including right-to-left, complex-script, and CJK requirements—were part of the test surface. This work verified whether translated content rendered and functioned correctly. It did not validate the linguistic accuracy of the translations. A passing build could establish that required checks ran, but human review still had to determine whether the result was understandable and usable.
What This Approach Makes Possible
Accessibility became a property of the publishing system rather than a remediation step. Source models captured the necessary information, authoring prompts and controls exposed it early, transforms preserved it, and test plans verified the final behavior.
The same architecture supported global publishing at scale. Reuse, variables, and conditional-content strategies limited unnecessary localization changes, while formatter evaluation prevented the toolchain from promising language support it could not render reliably. The content architecture accounted for accessibility and internationalization together.
The Principle
Accessible output depends on content modeling, transformation engineering, tool selection, authoring support, and testing. I treated Section 508 requirements, semantic source, tagged output, assistive technology, XSLT and XSL-FO, and RTL and CJK publishing as connected design constraints throughout the system.
