Tango is committed to making our Workflow content more accessible. Below are some of the ways in which Tango and the Tango product demonstrate commitment to accessibility:
Headings are used and supported in formatting across the site
Keyboard-friendly navigation is available across the site
Accessible colors are used in every instance
Our core UI components leverage Radix-ui, which maintains high accessibility standards that we inherit
The app and site are zoomable to 200% without losing functionality.
Alt text can be added to images by following the steps at the bottom of this article
Our design systems team meets twice a month to focus on continuous improvement by auditing existing components for consistency, accessibility, and usability. This meeting sequence is a core part of how we maintain and improve upon compliance along with a twice a week design critique where designers and engineers hold each other accountable for crafting new experiences that honor WCAG principles.
Accessible exports (PDF, HTML, and Markdown)
In September 2026 we changed how Workflow exports are built so that screen readers and accessibility checkers can read them. Exports look the same as before. The changes are underneath:
Tagged PDFs: PDF exports now carry a tagged structure, so assistive technology can find headings, text, images, and the right reading order.
Consistent headings: PDF, HTML, and Markdown exports use the same heading outline. It starts at level 1 and doesn't skip levels.
Image descriptions: Screenshots in PDF exports are tagged as images with alternative text, and decorative elements are marked so screen readers skip them.
Document title and language: Exports now include a document title and language setting.
We used the YuJa Panorama accessibility checklist as our guide. If your institution scans documents with a tool like YuJa Panorama, Equidox, or Adobe Acrobat's checker, re-export any Workflow you exported before September 14, 2026. Older files don't include these improvements.



