a11y-check-codelisted

# Accessibility check for source code Read the source code and find accessibility issues that should be prioritized for handling. Use WCAG 2.2 level AA as the guideline. ## Understand the limits of this check first What can be judged from source code is mainly **issues caused by the implementation**. The following cannot be judged: - Actual contrast ratio (when colors are determined at runtime) - Whether the focus order feels natural to the user - Layout breakage at 200% zoom or 320px width - Actual behavior of additional content shown on hover or focus - Actual screen reader announcements **Never write as though something was judged when it could not be judged.** Record check points that could not be judged in the report as "needs further verification," and generate handoff instructions for the `a11y-check-page` skill. Also, when general usability issues beyond accessibility are found, or things that cause no actual harm but violate HTML or WAI-ARIA specifications or best practices, report them too, rather than suppressing them on the grounds that "this isn't related to accessibility." ## Steps ### 1. Understand the target If a file path, glob, or directory is specified as an argument, treat that as the target. If not specified, ask the user what the target should be. Next, trace the target's imports to understand the component structure. **Follow the procedure in `references/component-tracing.md`.** Present the traced result to the user as a component tree, make t