updated proposal for aria

I made the updates to the proposed syntax for aria
https://github.com/w3c/coga/blob/943ee0510a5ed91eb012492e45412b9d4f860e6b/issue-papers/links-buttons.html

Please review and make any suggestions and comments 


As it is hard to read in git hub I am coping it into this  email


Syntax for adaptable links and buttons (symbols, help and keyboard)
Sometimes users need extra support. This can include:
Symbols and graphics that they are familiar with
Tool tips
Language they understand
Less features
Separating advertisements, so they do not confuse them with native content
Keyboard short cuts
Further, having familiar terms and symbols is key to being able to use the web. However what is familiar for one user may be strange for another requiring them to learn new symbols.
Additionally, many users need LESS buttons and options. Therefore being able to cut the amount of buttons, features and links will be extremely useful.
For that we need to standardize supportive syntax and terms that can be linked to associated symbols, terms, translations and explanations for the individual use via an aria attribute or INDI UI.
For example, if an Author gives to a button a role "send" then, without any work for the author, at the user end the button could be renderer with a symbol, term, and/or tooltip that is understandable for this particular user. It could automatically imply F1 help that explains the send function in simple terms. It could be identified with a keyboard short cut that will always be used for send. In addition it could be identified as important and always rendered, or rendered as a large button.
In another usecase we would like to see interoperable symbol set codes for Non verbal people. Products for people who are non vocal often use symbols to help users communicate. These symbols are in fact peoples language. Unfortunately many of these symbols are both subject to copy write AND not interoperable. That means end-users can only use one device, and can not use apps or AT from a different company. I was thinking that if we made an open set of symbol codes for these symbol sets, then they can be interoperable. That means the end use could buy the symbols and use them across different devices or applications. They would still be proprietary but they would also be interoperable.
We therefor suggest the following syntax:
Importance
Requirement: We request a way to identify and differentiate between critical features, medium features and less important features. These need to be defined as important from a user perspective. So critical features are used by 90% of users 90% of the time (or above). High would be above 60% use. Medium features would be 20% of users use it 20% of the time . Under 20% usage would be low.
User experience:
Proposed attribute: Add new attribute called aria-importance This could be an ARIA attribute with the following settings:1 (main task such as send for an email
aria-importance= "critical" this content is essential for the key function of the page (Example: The send button for an email draft)
aria-importance= "high" this content is used frequent but still high(Example: The delete button for an email draft)
aria-importance= "med" typically not used (Example: The save and settings buttons for an email draft)
aria-importance= "low" rarely used or used by advanced users. (Example: The terms and services or the archive button for an email draft)
Explain and feedback
Requirement: Some users need additional help. we request an attribute were the author can provide additional information. This help can be rendered as a tool tip or read when the control or link is read. Most users will not want this text rendered or spoken, Other users however will need it to understand the button, link, or what just happened.
Proposed attribute:
aria-feedback and aria-explain
Examples:
aria-feedback= "your email was sent"
aria-explain= "this item costs more"
Buttons and Link Functions
Requirement:
Having familiar terms and symbols is key to being able to use the web. However what is familiar for one user may be strange for another requiring them to learn new symbols. We need enabling semantics so that symbols and text used can be ones that the user understands. This can include:
Symbols and graphics that they are familiar with
Tool tips
Language they understand
Keyboard short cuts
 
For that we need to standardize supportive syntax and terms that can be linked to associated symbols, terms, translations and explanations for the individual use via an aria attribute.
Example User experience:, if an Author gives to a button a role "send" then, without any work for the author, at the user end the button could be renderer with a symbol, term, and/or tooltip that is understandable for this particular user. It could automatically imply F1 help that explains the send function in simple terms. It could be identified with a keyboard short cut that will always be used for send. In addition it could be identified as important and always rendered, or rendered as a large button. This would enable a consistent UI experience across applications and websites.
Proposed attribute: aria-function
The following could be supported values of aria-function
aria-function value that would typically be on buttons
compose(default importance = "1")
delete
next
previous
submit (default importance = "1")
undo
cancel
add label
move
view
save
send
received
sent
edit
reply
forward
my profile
upload
close
more
calendar
add entry
expand
unexpanded
Open
new
print
settings
aria-function value that would typically be on links
home
contact us
our phone
our email
site map
help
about us
terms
tools
comment
language (English)
sign in
sign up
product
services
social (provide label - such as facebook twitter)
post
contactus
aria-function value that would typically be on text
Our phone
Our address
Our email
Chat help
Help (or in ARIA buttons)
aria-function value that would typically be on form controls and would have a user context - for example phone would relate to the user's phone
Note they can be concatenated such as aria-function="birthdate month"
first name
family name
initial
phone
cell phone
address 1
city
state
country
post code
phone
credit card
expiry
birth date
day, *month *year
expiry date
todays date
credit card code
date start
date end
Concept codes
We would like to enable interoperable symbol set codes for Non verbal people. Products for people who are non vocal often use symbols to help users communicate. These symbols are in fact peoples language. Unfortunately many of these symbols are both subject to copy write AND not interoperable. That means end-users can only use one device, and can not use apps or AT from a different company. There are open set of symbol codes for these symbol sets, that could be referenced then they can be interoperable. alternatively wordnet nodes could be referenced. If the users symbols are mapped to the same nodes then users agents will be able to load the user understandable symbol. That means the end use could buy the symbols and use them across different devices or applications. They would still be proprietary but they would also be interoperable.
User experience: AAC users will load symbols that they understand in different applications that are made by a different provider.
Proposed attribute: aria-concept
value=uri
Examples:
<img aria-concept="http//wordnet.com/node/girl" href="mygirlsy.bmp/>
Potential parts of a page
Requirement: The following could be extensions for aria landmarks or ARIA for ePub
User experience: symbols and colors could be used consistently across different content.
Nav maps can be automatically generated for people learn via keypoints or examples.
 
Examples:
 
key points
example
note
warning
step
external - for external content, such as sponsored or advertising
offers - for special offers that are complementary to the main content or task
advertisement - advertisement or sponsored content
Number free
Requirement: Not everyone can understand numbers. We therefor suggest aria-numberfree for alternative text for people who can not understand the main content
User experience
A suggested user experience would be: Numerical concepts could be rendered by the user agent slightly different so that the user knows a number free explanation is available. The user can then mouse over the content and a tooltip would give the number free value
Proposed attribute:aria-numberfree
value : string
 
For example:
<span aria-numberfree="almost all">9 out of 10 </span>
<span aria-numberfree="hat and coat weather">The weather is 9 degrees</span> Non literal text and images
Requirement: Not everyone can understand non-literal text and icons such as metaphors, idioms etc. We need a tag that identifies text or images as non literal and allows the author to explain non-literal text and images to users.
User experience:
A suggested user experience would be: Non literal content could be rendered by the user agent slightly differently so that the user knows that this content should not be taken literally and that a literal explanation is available. The user can then mouse over the content and a tooltip would give the literal value.
 
Proposed attribute:
aria-nonliteral
Value= string
Examples:
 
<span aria-nonliteral="it is raining hard"> It is raining cats and dogs </span>

User agents can render non-literal text in a different way so that users will know that this is non literal. They can then use a mouse over or other technique to receive the translation.
Confirm other features
The following may not be necessary
Views
ascending. descending
day, week month
this week
this month
today
TODO
Collect fuller set
Build sample JSON and scrips so it works..
Build consensus and adjust proposals
Write associated terms, tool tip help for collection.
Add complementary types such as example, offer etc
missing items? -todo list , note, spelling