The visible table remains intact while its accessible reading order breaks.
Enterprise creators need dependable downloads, while the post-processing pipeline must absorb changing Chromium output.
Who you’d be doing this for
“Our report looked fine in the review, then accessibility told us the numbers were being read out of order.”
Elif Erdogan · Enterprise Content Manager
Prepares recurring internal reports in the editor for a company with accessibility requirements.
What is at stake
Complex-table PDFs look correct but screen readers announce cells in the wrong sequence. You must weigh a resilient post-processing rule against pinning the Chromium change for this release.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- visible fidelity vs accessible reading order
- rapid containment vs resilient post-processing
- Chromium upgrades vs export stability
- enterprise deadlines vs regression coverage
Why Canva
Chromium-based exports turn editor designs into downloadable files used across enterprise content workflows.
Written with these in mind
Not your kind of problem? 35 more at Canva, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.