WebAIM - Web Accessibility In Mind

E-mail List Archives

for

From: Zhang Bo
Date: Jul 23, 2025 3:38PM

Hi all,

I’m exploring how WCAG 3.2.2 (On Input) applies to the native HTML <input type="date">, and I’d appreciate your thoughts.

The Understanding Success Criterion 3.2.2: On Input<https://www.w3.org/WAI/WCAG22/Understanding/on-input> page includes an example where focus automatically moves from one phone number field to the next (area code → prefix → line number). That behavior requires clear communication to users to meet the guideline.

I’ve noticed that some browsers implement similar behavior with native <input type="date"> elements—automatically advancing focus from month to day to year as the user types. This isn’t something developers typically script; it’s built-in browser behavior.

Would this kind of auto-advancing within a single input be considered a change of context that needs to be communicated to the user? Or is it generally considered acceptable since it's confined to one control?

Curious if anyone’s seen this flagged in audits or addressed it in practice.

Thanks in advance for your insights!
Bo Zhang
she, her, hers
Associate Accessibility Analyst
User Experience Center

HCA Healthcare
1 Park Plaza, Nashville
HCAhealthcare.com<https://hcahealthcare.com/> | Connect With Us<http://hcahealthcare.com/about/connect-with-us.dot>;