W3C home > Mailing lists > Public > public-cognitive-a11y-tf@w3.org > October 2016

Re: 3.3.2 Labels or Instructions (change) feedback

From: Thad C <inclusivethinking@gmail.com>
Date: Thu, 6 Oct 2016 09:59:53 -0700
Message-ID: <CAOh2y+8ARZzn-u+jmaX-5hn+WdKeGu-7YkY6vmLbB-zjjuO8yw@mail.gmail.com>
To: "lisa. seeman" <lisa.seeman@zoho.com>
Cc: public-cognitive-a11y-tf <public-cognitive-a11y-tf@w3.org>
Ok thanks for the feedback. I can revise as soon as Friday or Saturday.

Best,
Thaddeus

On Oct 6, 2016 9:48 AM, "lisa.seeman" <lisa.seeman@zoho.com> wrote:

> Hi Thad
>
> Thanks for all the hard work. Some more feedback on the labels SC.
>
>
> The benefits section MUST explain why this is essential to some users.
>
>
> The following are not benefits but techniques:
>
>
> "This can include:
>
>    - Require as little information as possible. Make it visually clear
>    what information is required
>    - Provide instructions
>    - Give additional hints and pointers to users to give context.
>    - Calendars and dates
>       - Use terms that describe the present past and future days rather
>       than just using numbers or dates. By using terminology such as
>       *today*, *tomorrow* or *travel now* in the appropriate language for
>       the locale, the user has a clear understanding of the timeliness of the
>       event, booking or occasion.
>       - Display long form of *dates* with punctuation, e.g., June 1st,
>       2015 or 1st June, 2015. This offers a clear understanding of the date.
>       Punctuation helps the text to speech API read the date in a way that is
>       easier to follow.
>       - When using numbers for time - check use of appropriate
>       punctuation between numbers when providing times as these may be read
>       inappropriately by text to speech engines.
>    - Temperature
>       - Allow reading of long form temperature. Reading the values long
>       form rather than using figures is helpful in for the same reasons outlined
>       in the dates and calendar section.
>       - Reinforce with non-numerical values, e.g., Very Cold, Cold, Cool,
>       Mild, Warm, Hot, Very Hot. These are subjective values and may not always
>       be helpful especially when dealing with weather and ambient temperature
>       (due to reasons such as variances in regional average temperature - what is
>       considered hot in UK is considered cool in India or Thailand). It may be
>       possible to use look up tables and JSON to query relative average
>       temperature based upon locale and adjust temperature ranges accordingly.
>
>
> please also reread the instructions and my past feedback
>
> thanks so much and all the best
>
> Lisa Seeman
>
> LinkedIn <http://il.linkedin.com/in/lisaseeman/>, Twitter
> <https://twitter.com/SeemanLisa>
>
>
>
Received on Thursday, 6 October 2016 17:01:31 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 6 October 2016 17:01:32 UTC