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

Re: Opinions on accessible time formatting

From: <accessys@smart.net>
Date: Fri, 7 Nov 2014 19:44:52 -0500 (EST)
To: chaals@yandex-team.ru
cc: Emmanuelle Gutiérrez y Restrepo <coordina@sidar.org>, "'Mattes, Kurt X1'" <kurt.x1.mattes@chase.com>, "'Andy Keyworth'" <akeyworth@tbase.com>, "'WAI Interest Group'" <w3c-wai-ig@w3.org>
Message-ID: <Pine.LNX.4.60.1411071942310.24349@cygnus.smart.net>

but this is the way a computer (normally) sorts things so if cronological 
order or date time order is important this would be the way to do it.

Bob

On Sat, 8 Nov 2014 chaals@yandex-team.ru wrote:

> Date: Sat, 08 Nov 2014 01:30:27 +0100
> From: chaals@yandex-team.ru
> To: "[utf-8] Emmanuelle Gutiérrez y Restrepo" <coordina@sidar.org>,
>     "'Mattes, Kurt X1'" <kurt.x1.mattes@chase.com>,
>     'Andy Keyworth' <akeyworth@tbase.com>,
>     'WAI Interest Group' <w3c-wai-ig@w3.org>
> Subject: Re: Opinions on accessible time formatting
> Resent-Date: Sat, 08 Nov 2014 00:31:01 +0000
> Resent-From: w3c-wai-ig@w3.org
> 
> 07.11.2014, 19:37, "Emmanuelle Gutiérrez y Restrepo" <coordina@sidar.org>:
>> I think that the most "accesible" is the international format: yyyy/mm/dd,
>> for example: 2014/11/07
>>
>> This can be understood by any person in any language.
>>
>> And for the hours the 24 hours format: 23:00
>
> This is fine for *most of the world*.
>
> Unfortunately Americans are especially unlikely to understand either of these formats. Like telling them someone is 150cm tall - they just don't know what that means.
>
> Or like telling most of the world that someone is 6 feet 4 and weighs 16 stone.
>
> It turns out not to be directly accessible to people.
>
>> See the ISO 8601 "Data elements and interchange formats — Information
>> interchange — Representation of dates and times"
>
> The problem is that people don't have browsers that can pick up measurements and translate them to things the user will actually understand.
>
> Sounds like a useful thing for schema.org to help with, actually.
>
> cheers
>
>> Regards,
>>
>> Emmanuelle Gutiérrez y Restrepo
>> Patrono y Directora General
>> Fundación Sidar - Acceso Universal
>> Email: coordina@sidar.org
>> Personal: Emmanuelle@sidar.org
>> Web: http://sidar.org
>>
>> -----Mensaje original-----
>> De: Mattes, Kurt X1 [mailto:Kurt.X1.Mattes@chase.com]
>> Enviado el: viernes, 07 de noviembre de 2014 15:50
>> Para: chaals@yandex-team.ru; Andy Keyworth; 'WAI Interest Group'
>> Asunto: RE: Opinions on accessible time formatting
>>
>> Agree with Chaals and only add that consistency in the way it is presented
>> is an important part of comprehending any information that is commonly
>> presented in various ways.
>>
>> Thanks,
>> Kurt Mattes
>> VP - Electronic Communications Accessibility Team | JPMorgan Chase & Company
>>
>> -----Original Message-----
>> From: chaals@yandex-team.ru [mailto:chaals@yandex-team.ru]
>> Sent: Friday, November 07, 2014 7:00 AM
>> To: Andy Keyworth; 'WAI Interest Group'
>> Subject: Re: Opinions on accessible time formatting
>>
>> OK, I'll bite
>>
>> 04.11.2014, 16:12, "Andy Keyworth" <akeyworth@tbase.com>:
>>>  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?
>>
>> As far as I know, these are pretty much equal in reality.
>>
>> (Note that date formats are different. You do a lot better for most people
>> using DD Month YYYY, e.g. 12 November 2014 than any shorthand. But I doubt
>> that is news).
>>
>> cheers
>>>  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.
>>
>> --
>> Charles McCathie Nevile - web standards - CTO Office, Yandex
>> chaals@yandex-team.ru - - - Find more at http://yandex.com
>>
>> This transmission may contain information that is privileged, confidential,
>> legally privileged, and/or exempt from disclosure under applicable law.  If
>> you are not the intended recipient, you are hereby notified that any
>> disclosure, copying, distribution, or use of the information contained
>> herein (including any reliance thereon) is STRICTLY PROHIBITED.  Although
>> this transmission and any attachments are believed to be free of any virus
>> or other defect that might affect any computer system into which it is
>> received and opened, it is the responsibility of the recipient to ensure
>> that it is virus free and no responsibility is accepted by JPMorgan Chase &
>> Co., its subsidiaries and affiliates, as applicable, for any loss or damage
>> arising in any way from its use.  If you received this transmission in
>> error, please immediately contact the sender and destroy the material in its
>> entirety, whether in electronic or hard copy format. Thank you.
>
> --
> Charles McCathie Nevile - web standards - CTO Office, Yandex
> chaals@yandex-team.ru - - - Find more at http://yandex.com
>
Received on Saturday, 8 November 2014 01:01:42 UTC

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