W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > October to December 2014

Re: Opinions on accessible time formatting

From: Steve Faulkner <faulkner.steve@gmail.com>
Date: Sat, 8 Nov 2014 16:19:57 +0000
Message-ID: <CA+ri+VnMA-8Qy3XkXOoMT4T7bQJ52_Fy=ZerJASx-BomsYgANg@mail.gmail.com>
To: Andy Keyworth <akeyworth@tbase.com>
Cc: WAI Interest Group <w3c-wai-ig@w3.org>
Somewhat related, HTML5 has a <time> element [1] (content is limited to
various kinds of dates, times, time-zone offsets, and durations)


Maybe this could be used to identify times/dates etc to AT, so at least
they could parse the contents knowing that its a date/time.

[1] http://www.w3.org/TR/html/text-level-semantics.html#the-time-element

--

Regards

SteveF
HTML 5.1 <http://www.w3.org/html/wg/drafts/html/master/>

On 4 November 2014 15:07, Andy Keyworth <akeyworth@tbase.com> wrote:

> Hi,
>
> I'm hoping I can get some advice on how expressions of time can be
> accessibly formatted on web pages.
>
> For example, is 11:00 a.m. or 2:00 p.m. considered (generally) acceptable,
> or would 11:00 am or 2:00 pm (without periods between letters) be
> preferable? Is another format better?
>
> Thank you,
>
> Andy Keyworth
> Senior Web Accessibility Specialist
> T-Base Communications
> Phone: 613-236-0866 | Toll free: 1-800-563-0668 x 1256
> www.tbase.com | Ogdensburg, NY | Ottawa, ON
> ALL TOUCH POINTS. ALL ACCESS METHODS. ALL FORMATS.TM
>
> This email may contain information that is privileged and confidential. If
> you have received this communication in error, please delete this email
> message immediately.
>
>
>
>
>
Received on Saturday, 8 November 2014 16:21:04 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 13 October 2015 16:21:53 UTC