Change board background

Change the background of the Sprint Planning board to a neutral light-gray before Monday so the board is readable on phones. Verify the contrast on mobile, confirm the change with the design lead, and roll back if any key labels become hard to read.

Before I change the Sprint Planning board background, make it easy for the design lead to sign off. Present a quick comparison: current background, proposed light-gray, and the worst-case phone screenshot. Highlight any label or sticker legibility issues and call out cards where colored labels will clash so they can approve or request tweaks fast.

I just changed the Sprint Planning board background and QA reports that colored labels and checklist items are hard to read on Android phones. I’m worried developers will miss tasks at the sprint start. I don’t know whether to revert immediately or adjust label colors. What should I do now to restore clarity without delaying the planning meeting, and how should I tell the team what happened?

We keep making aesthetic board changes—backgrounds, stickers, themes—that occasionally make boards unreadable on teammates’ devices or for colorblind users. I want one enforceable habit to avoid these regressions. What checklist or approval step should we add before visual changes go live so accessibility and phone readability are always preserved?