Problem/Motivation

Alpha2 has keyboard, focus, label and narrow-screen checks in Stark. Full screen-reader behavior and the site's normal administration theme were not part of that verification.

Proposed resolution

Test the six operator forms in a supported administration theme using a screen reader and keyboard-only navigation. Fix concrete findings and retain focused regression coverage.

Acceptance criteria

  • Verify labels, instructions, error association, status announcements, focus after validation/confirmation and prevention of accidental repeat actions.
  • Check inspector, preview, recovery, export, erasure and settings at narrow widths and browser zoom.
  • Record browser, screen reader and theme versions, test steps and any remaining limitations.
  • Confirm accessibility improvements preserve permission, CSRF, privacy and confirmation boundaries.

Scope and dependencies

Optional follow-up after stable release; not a blocker for #3621224: Complete the 1.0.0 stable release verification gates. Builds on #3621137: Expand integration coverage to routing, mail transport, forms and Drush; the completed original issue remains fixed.

Comments

jmcerda created an issue. See original summary.

  • e9746198 committed on 1.x 
    Issue #3621236: Verify operator form accessibility in Claro

Issue #...

  • jmcerda committed b9f509a3 on 1.x 
    Issue #3621236: Validate timeline dates without comparing exception text

  • jmcerda committed 9e2eddd6 on 1.x 
    Issue #3621236: Verify operator form accessibility in Claro

Associate...
jmcerda’s picture

jmcerda
Location Boca Raton, FL
commented
Assigned: Unassigned » jmcerda
Status: Active » Fixed

Landed on 1.x-dev. Operator forms in Claro now associate instructions with the form, announce lookup results in a named region, bind timeline and preview filter errors to fields, and mark recovery and erasure confirmation as destructive. Erasure review has Cancel. Permission, CSRF and POST-only lookups are unchanged. Live VoiceOver, NVDA and JAWS certification remains outstanding and is recorded in docs/accessibility-verification.md. This is not a stable-release gate.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.