WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Best Practice - representing time/date info

for

From: wolfgang.berndorfer
Date: Mar 26, 2020 4:11AM

It also depends on the general settings for how SR or speech should announce numbers.

If I told my SR to announce each number it will have effect on telephone numbers, dates and time. Don't know of any configuration especially for date and time. So AT developers have to be addressed.

But the question for best practice still is relevant for understanding and UX. The MM-DD-YYYY model is confusing for me as German speaking, where DD-MM-YYYY is common. So I'd prefer *March 25, 2020* to inform me about the month. 03/25/2020 may still be understandable (but don't make me think!). 08/09/2020 already could easily be misinterpreted by somebody, who is used to understand DD-MM-YYYY.

Wolfgang

-----Ursprüngliche Nachricht-----
Von: WebAIM-Forum < <EMAIL REMOVED> > Im Auftrag von Murphy, Sean
Gesendet: Mittwoch, 25. März 2020 23:09
An: WebAIM Discussion List < <EMAIL REMOVED> >
Betreff: Re: [WebAIM] Best Practice - representing time/date info

It depends on the screen reader. You are only using one screen reader as your example case. VoiceOver from memory does not have any specific settings for handling dates or time formats. Jaws does and I believe NVDA does. Also you need to think of country base if this is a web site. If it is a document, then using the USA format as you described is fine due to the origin of the document.

If you want to remove the dependency of date formats. Use Mar 25, 2020 and the screen reader will announce the date correctly. Time is still dependent on the screen reader. Most users I suspect will be used to how their screen reader announces dates and time.

I hope this helps.

Sean