Add accessibility tests and fixes for the create wizard step components (forms, errors, focus)

[1nonlypiece]

📌 Description

The create-wizard step components — CreateCommitmentStepSelectType.tsx,
CreateCommitmentStepConfigure.tsx, and CreateCommitmentStepReview.tsx — drive
a multi-step form but lack accessibility-focused tests. Form labelling, error
association, and focus management on step changes are critical for keyboard and
screen-reader users.

🎯 Requirements and Context

• Verify each input has an associated label and aria-describedby for errors.
• Verify focus moves to the first error or step heading on navigation.
• Verify aria-invalid toggles with validation.
• Confirm the review step exposes editable section links accessibly.

🛠️ Suggested Execution

1. Fork the repo and create a branch

git checkout -b test/create-wizard-a11y

2. Implement changes

• Add src/components/CreateCommitmentStepSelectType.test.tsx,
  CreateCommitmentStepReview.test.tsx, and an a11y-focused suite for the
  configure step with Vitest + RTL; apply minimal a11y fixes uncovered by tests.
• Add docs/accessibility/CREATE_WIZARD_A11Y.md documenting requirements met.
• Validate keyboard-only completion of the wizard.

3. Test and commit

• Run pnpm test.
• Cover edge cases: validation errors, focus-on-error, editing from review,
  back navigation focus.

Example commit message

test: accessibility coverage and fixes for create wizard steps

✅ Guidelines

• Minimum 95% test coverage on the step components.
• Clear, reviewer-friendly documentation.
• Timeframe: 96 hours.

🏷️ Labels

type-testing · type-security · area-frontend · MAYBE REWARDED ·
GRANTFOX OSS · OFFICIAL CAMPAIGN

💬 Community & Support

• Join the CommitLabs contributor Discord to coordinate and get unblocked fast:
  https://discord.gg/WV7tdYkJk
• Introduce yourself before starting so we can avoid duplicate work and pair you
  with a reviewer. Maintainers triage actively and review fast.

[MJ-RWA]

@MJ-RWA has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

I’d like to work on this issue. I have experience documenting smart contract deployment and configuration workflows, particularly where contributors must coordinate multiple contracts, roles, and on-chain configuration steps.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @MJ-RWA to this issue.

[ZuLu0890]

@ZuLu0890 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

I would love to work on this within few hours

ℹ️ Repo Maintainers: To accept this application, review their application or assign @ZuLu0890 to this issue.

[GBOYEE]

I'd like to work on this.

Approach:

• I'll write the test cases and ensure they pass with full coverage
• Verify with existing tests + add new ones if needed

Estimated effort: ~1-2 hours. PR incoming shortly.

[GBOYEE]

I'd like to work on this.

Approach:

• I'll write the test cases and ensure they pass with full coverage
• Verify with existing tests + add new ones if needed

Estimated effort: ~1-2 hours. PR incoming shortly.

[GBOYEE]

I'd like to work on this issue.

My Approach

• Analyze the root cause of: ##
• Implement a clean, tested fix
• Follow existing code patterns and conventions

Files Likely Modified

• TBD after analysis

Timeline

• Estimated completion: 15-30 minutes
• PR will be submitted with tests and documentation

Closes #651