An app needs readable names, reachable actions and errors that people can correct. A color change alone cannot explain a failed form. Keep the invalid draft and associate the error with the field or control that needs attention. Keyboard and assistive focus need testing in the actual app.
The local tasks check accessible-name formulas, ordinary tab stops and a responsive width calculation. Those properties are useful evidence but do not prove that every phone layout works. A real narrow-viewport check also needs unclipped content, usable targets and a sensible focus path. The exercises make that boundary explicit instead of treating one computed width as a complete accessibility audit.