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

I think this is missing: "In content implemented using markup languages, "

I looked over the notes again and we have: 
Purpose of controls: In content implemented using mark-up languages, the conventional name of common controls can be programmatically determined.(AA)


(The next version was  


Purpose of controls: In content implemented using mark-up languages, conventional controls can be programmatically determined. - let me know if you want to revert to that)

All the best

Lisa Seeman

LinkedIn, Twitter





---- On Sun, 23 Jul 2017 13:30:13 +0300 lisa.seeman<lisa.seeman@zoho.com> wrote ---- 

I am fine with this. I will update the SC wording now.

(Sorry it so late Andrew but the call took us close to Sabbath so i could not update it before)

All the best

Lisa Seeman

LinkedIn, Twitter





---- On Fri, 21 Jul 2017 22:56:49 +0300 David MacDonald<david100@sympatico.ca> wrote ---- 

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
 
CanAdapt Solutions Inc.
Tel:  613.235.4902
LinkedIn 

twitter.com/davidmacd
GitHub
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






 
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 help is available for non-conventional controls  (this would included having a explanation)









All the best

Lisa Seeman

LinkedIn, Twitter













-- 
John Foliot


Principal Accessibility Strategist

Deque Systems Inc.

john.foliot@deque.com



Advancing the mission of digital accessibility and inclusion