Rather than treating every issue as equally urgent, a roadmap groups fixes into phases, usually starting with the highest-severity barriers that fully block a task for disabled users, followed by broader remediation, and finally process changes like design system updates and staff training that prevent new issues from being introduced.
A realistic roadmap also accounts for an organization’s actual development capacity and release cycle, since an ambitious plan that ignores resourcing tends to stall, while a roadmap built around real sprints and ownership is far more likely to actually get executed.