Re: Alastair, Jan, Jason , myself and John have an updated version of

In looking at Jason's proposal, I think it's more accurate.

****

The conventional name of every conventional user interface component can be
programmatically determined.

****

Otherwise, it might be interpreted to mean the exact same thing as 4.1.2
which requires already that every component be programmatically
determinable...



Cheers,
David MacDonald



*Can**Adapt* *Solutions Inc.*

Tel:  613.235.4902

LinkedIn
<http://www.linkedin.com/in/davidmacdonald100>

twitter.com/davidmacd

GitHub <https://github.com/DavidMacDonald>

www.Can-Adapt.com <http://www.can-adapt.com/>



*  Adapting the web to all users*
*            Including those with disabilities*

If you are not the intended recipient, please review our privacy policy
<http://www.davidmacd.com/disclaimer.html>

On Fri, Jul 21, 2017 at 2:18 PM, John Foliot <john.foliot@deque.com> wrote:

> With the following draft definition added:
>
> Draft list of Conventional Controls:
> (note: we may be able to whittle this list down a bit - for a larger group
> discussion)
>
> *Form inputs: *
>
>    - name (corresponds to both first and family),
>    - first name,
>    - family name,
>    - initial,
>    - phone (corresponds to a user phone number),
>    - cell phone,
>    - address 1,
>    - city,
>    - state,
>    - country,
>    - post code,
>    - credit card,
>    - credit card security code,
>    - dates: expiry date, birth date, today's date, date start, date end
>    - calendar data: day, *month, *year,
>
>
> *Buttons or controls (content editing):*
>
>    - compose,
>    - delete,
>    - next,
>    - previous,
>    - submit,
>    - undo,
>    - cancel,
>    - buy,
>    - add label,
>    - move,
>    - view,
>    - save,
>    - send,
>    - received,
>    - sent,
>    - edit,
>    - reply,
>    - forward,
>    - my profile,
>    - upload,
>    - close,
>    - more,
>    - calendar,
>    - entry,
>    - expand,
>    - unexpanded,
>    - open,
>    - new,
>    - print,
>    - settings,
>    - mode,
>    - higher,
>    - lower.
>
>
> *Buttons or controls (navigation): *
>
>    - home,
>    - contact us,
>    - our phone,
>    - our email,
>    - site map,
>    - help,
>    - about us,
>    - terms,
>    - tools,
>    - comment,
>    - language,
>    - sign in,
>    - sign up,
>    - product,
>    - services,
>    - social,
>    - post,
>    - contact us,
>    - help,
>    - chat help,
>
>
> On Fri, Jul 21, 2017 at 11:20 AM, lisa.seeman <lisa.seeman@zoho.com>
> wrote:
>
>> Hi Folks
>>
>> Alastair, Jan, Jason and John have an updated version  of personlization
>> support
>>
>> At AA
>>
>> Purpose of controls: In content implemented using mark-up languages,
>> conventional controls can be programmatically determined. (AA)
>>
>>
>> At AAA
>> we would like
>>
>> In content implemented using markup languages, the function and context
>> information of controls and regions can be programmatically determined
>> using a publicly available vocabulary.
>>
>>
>> also
>> Upgrade and change 3.3.5 to AA -  Context-sensitive hel
>> <https://www.w3.org/TR/UNDERSTANDING-WCAG20/minimize-error-context-help.html#context-sensitivehelpdef>p is
>> available for non-conventional controls  (this would included having a
>> explanation)
>>
>>
>>
>>
>>
>> All the best
>>
>> Lisa Seeman
>>
>> LinkedIn <http://il.linkedin.com/in/lisaseeman/>, Twitter
>> <https://twitter.com/SeemanLisa>
>>
>>
>>
>
>
> --
> John Foliot
> Principal Accessibility Strategist
> Deque Systems Inc.
> john.foliot@deque.com
>
> Advancing the mission of digital accessibility and inclusion
>