You need to deliver a visible new feature in a week on a legacy frontend with no automated tests and known accessibility issues. Stakeholders expect it shipped quickly. How do you balance delivery speed, code quality, and accessibility? Describe the prioritization and the concrete steps you would take before and after release.

I'd treat this like triage: ship a usable, accessible core experience fast, then iterate. First 24 hours I'd align with the PM and designer to cut scope to a minimal viable interaction that delivers the visible value and identify the top 3 accessibility blockers (keyboard focus, labels, color contrast) that account for ~70% of reported issues. I’d implement the feature behind a feature flag, add a small CI smoke test (~10–15 minutes) for the critical path, and run a manual accessibility checklist with one QA and one designer — that’s how we shipped a similar feature in 6 days at my last company with a 3-person team. After release I’d monitor errors and user metrics, unflag when stable, then schedule automated unit/visual tests and a full a11y audit to reduce regressions by ~30% over the next sprint.