Syntax for adaptable links and buttons (symbols, help and keyboard)
Sometimes users need extra support. This can include:
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:
aria-importance: This could be an ARIA attribute with the following settings:1 (main task such as send for an email
Some users need additional help. 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. aria-feedback= "your email was sent" aria-explain= "this item costs more"
The following could be types of ARIA role button
Note, you should always have the default "button" eg role="button undo"
aria-concept : The following could enable interoperable symbol set codes for Non verbal people. example aria-concept="http....(EA fill in an example)"
The following could be extensions for aria landmarks or ARIA for ePub
The following may not be necessary