Brief a coding agent to fix accessibility problems on a page

Goal: Fix the accessibility findings below on {{page}}, so that people using a keyboard or a screen reader can {{user_task}}, meeting {{standard}} for these findings.

Context:
- Files for the page, as far as I know: {{files}} (for example src/pages/checkout/ and its components)
- Audit findings (tool or auditor, rule, element, description):
"""
{{findings}}
"""
- UI framework and component library: {{framework}}
- Where colors are defined, if the project uses design tokens: {{tokens_file}}
- Automated accessibility check command: {{a11y_command}}
- Test command: {{test_command}}

Constraints:
- Use native HTML first: button for actions, a for links, label for inputs, headings in order, and landmarks such as main and nav. Add ARIA only when no native element fits, and then follow the WAI-ARIA Authoring Practices pattern for that widget.
- Every form field has a visible label tied to it, and each error message is linked to its field with aria-describedby.
- Keep focus visible: do not remove outlines without a visible replacement. Keep the tab order in the visual order and do not use a positive tabindex. Dialogs move focus inside when they open, keep it there, close on Escape and return focus to the control that opened them.
- Fix color contrast (4.5:1 for normal text, 3:1 for large text and interface parts, under WCAG AA) in the design tokens, not with one-off colors. If a fix changes a brand color, stop and show me the before and after values first.
- For images, write alt text only from content I give, and use alt="" for decorative images. Where you cannot tell what an image shows, write [ALT NEEDED] and list it.
- Do not change the visual design beyond what the fixes need. Do not disable or suppress rules in the accessibility checker. Do not touch {{off_limits}}.

Done when:
- {{a11y_command}} reports no violations on the page for the rules in the findings.
- A keyboard test (for example in tests/a11y/, with Playwright) passes: from the top of the page, Tab reaches every interactive element in visual order with a visible focus indicator, Enter or Space activates each control, and any dialog opens, holds focus, closes on Escape and returns focus.
- {{test_command}} passes.

Verify: run the checks and tests, read the output and iterate until they pass. Then report a table with the columns Finding, Fix, File, Verified by (automated check, keyboard test, or needs a person), plus the commands you ran with the last 20 lines of their output. Automated checks find only part of the problems, so also list what still needs a person to test with a screen reader.