Contact Form: improve accessibility

[jeherve]

There are different ways we could work on improving the usability and accessibility of the contact form feature. Let's take a closer look at the different issues:

Tasks

Preview Give feedback

1. Contact Form: accessibility issues for checkbox and radio groups #16685
   Good For Community [Feature] Contact Form [Focus] Accessibility [Plugin] Jetpack [Pri] Normal [Type] Bug +6
   
2. Jetpack Form Block: A11Y - ARIA input field doesn't have accessible text #30762
   Triaged User Report [Block] Contact Form [Feature] Contact Form [Focus] Accessibility [Plugin] Jetpack [Pri] Normal [Type] Bug +8
   
3. Subscriptions / Contact Form: improve accessibility of validation errors #14155
   [Feature] Contact Form [Feature] Subscriptions [Focus] Accessibility [Pri] Normal [Type] Enhancement +5
   
4. Enhancement: validate Contact Form fields as user types #34281
   [Block] Contact Form [Feature] Contact Form [Focus] Accessibility [Plugin] Jetpack [Status] In Progress [Type] Enhancement +6
   
5. Contact Form: dropdown error message is not accessible #34253
   Triaged [Block] Contact Form [Focus] Accessibility [Package] Forms [Plugin] Jetpack [Pri] Normal [Status] Priority Review Triggered [Type] Bug +8
   
6. Enhancement: identify Contact Forms as regions by screen readers #34282
   [Block] Contact Form [Feature] Contact Form [Focus] Accessibility [Plugin] Jetpack [Type] Enhancement +5
   
7. Enhancement: add loading state to Contact Form on submitting #34283
   [Block] Contact Form [Feature] Contact Form [Focus] Accessibility [Plugin] Jetpack [Type] Enhancement +5
   
8. Contact Form: required Multiple Choice field can be submitted empty #34235
   Triaged [Block] Contact Form [Feature] Contact Form [Plugin] Jetpack [Pri] Normal [Type] Bug +6
   
9. Contact Form: improved design of Checkbox field #34272
   [Block] Contact Form [Feature] Contact Form [Focus] Accessibility [Package] Forms [Tests] Includes Tests +5
   
10. Contact Form: fix styling issues for Outlined and Animated styles #34277
    [Block] Contact Form [Feature] Contact Form [Package] Forms +3
    
11. Contact Form: datepicker is not accessible to keyboard users #34501
    Triaged [Feature] Contact Form [Focus] Accessibility [Plugin] Jetpack [Pri] Low [Type] Bug +6
    
12. Enhancement: Contact Form assets are not minified #34280
    [Block] Contact Form [Feature] Contact Form [Plugin] Jetpack [Status] In Progress [Type] Enhancement +5
    
13. Enhancement: [Contact Form] Write tests for accessible-form.js #34502
    [Feature] Contact Form [Focus] Accessibility [Plugin] Jetpack [Type] Enhancement +4
    
14. Enhancement: [Contact Form] Add accessible name to forms #34504
    [Feature] Contact Form [Focus] Accessibility [Plugin] Jetpack [Type] Enhancement +4
    
15. Contact Form: add missing textdomain #34577
    [Feature] Contact Form [Package] Forms [Pri] Normal [Status] Needs Author Reply [Type] Bug +5
    

Lower priority: improvements in the classic editor

Preview Give feedback

1. Contact Form: A11Y - (required) label doesn't have enough contrast ratio with default opacity setting #31203
   Triaged [Block] Contact Form [Feature] Contact Form [Focus] Accessibility [Platform] Atomic [Platform] Simple [Plugin] Jetpack [Pri] Normal [Type] Bug +9
   
2. [Accessibility] Contact Form Edit and Close options are not found in screen reader. #25027
   Customer Report Good For Community Triaged [Feature] Contact Form [Focus] Accessibility [Plugin] Jetpack [Pri] Low [Type] Bug +8
3. Contact Form: Screen Reader/Keyboard Users Can't Edit a Form #12574
   Customer Report Good For Community Triaged [Feature] Contact Form [Focus] Accessibility [Pri] Low [Status] Stale [Type] Bug +8
4. Contact Form: Checkbox cannot be marked as required from inline block menu #34279
   Triaged [Block] Contact Form [Feature] Contact Form [Plugin] Jetpack [Pri] Low [Type] Bug +6
   

---

Related discussion: p1698591039559549-slack-C0299DMPG
PT: pf5801-87-p2

[chrisbliss18]

Extended the due date because we added some additional tasks.

[github-actions]

This issue has been marked as stale. This happened because:

• It has been inactive for the past 6 months.
• It hasn’t been labeled `[Pri] BLOCKER`, `[Pri] High`, `[Type] Feature Request`, `[Type] Enhancement`, `[Type] Janitorial`, `Good For Community`, `[Type] Good First Bug`, etc.

No further action is needed. But it's worth checking if this ticket has clear reproduction steps and it is still reproducible. Feel free to close this issue if you think it's not valid anymore — if you do, please add a brief explanation.

[davemart-in]

This feels more like a roll up issue than an individual issue that needs to be on The One Board for an engineer to pick up. Removing it from The One Board.

[simison]

I'll mark this as done and move the two remaining sub-issues to be bugs to be sorted.