semantics.html

<!DOCTYPE html>
<html lang="en" xmlns="http://www.w3.org/1999/xhtml">
	<head>
		<title>Personalization Semantics 1.0</title>
		<meta charset="utf-8"/>
		<script src="https://www.w3.org/Tools/respec/respec-w3c-common" class="remove"></script>
		<script src="common/biblio.js" class="remove"></script>
		<script class="remove">
	var respecConfig = {
		// embed RDFa data in the output
		trace:  true,
		doRDFa: '1.1',
		includePermalinks: true,
		permalinkEdge:     true,
		permalinkHide:     false,
		tocIntroductory: true,
		// specification status (e.g., WD, LC, NOTE, etc.). If in doubt use ED.
		specStatus:           "ED",
		noRecTrack: true,
		//crEnd:                "2012-04-30",
		//perEnd:               "2013-07-23",
		//publishDate:          "2013-08-22",
		//diffTool:             "http://www.aptest.com/standards/htmldiff/htmldiff.pl",

		// the specifications short name, as in http://www.w3.org/TR/short-name/
		shortName:            "personalization-semantics-1.0",


		// if you wish the publication date to be other than today, set this
		//publishDate:  "2017-05-09",
		copyrightStart:  "2017",

		// if there is a previously published draft, uncomment this and set its YYYY-MM-DD date
		// and its maturity status
		//previousPublishDate:  "",
		//previousMaturity:  "",
		//prevRecURI: "",
		//previousDiffURI: "",

		// if there a publicly available Editors Draft, this is the link
		edDraftURI: "https://w3c.github.io/personalization-semantics/",

		// if this is a LCWD, uncomment and set the end of its review period
		// lcEnd: "2012-02-21",

		// editors, add as many as you like
		// only "name" is required
		editors: [
			{
				name: "Lisa Seeman",
				url: 'http://athena-ict.com',
				mailto: "lisa.seeman@zoho.com",
				w3cid: 16320
			},
			{
				name: "Rich Schwerdtfeger",
				w3cid: 2460
			},
			{
				name: "Michael Cooper",
				url: 'https://www.w3.org',
				mailto: "cooper@w3.org",
				company: "W3C",
				companyURI: "http://www.w3.org",
				w3cid: 34017
			}
		],

		// authors, add as many as you like.
		// This is optional, uncomment if you have authors as well as editors.
		// only "name" is required. Same format as editors.

		//authors:  [
		//    { name: "Your Name", url: "http://example.org/",
		//      company: "Your Company", companyURI: "http://example.com/" },
		//],

		/*
		alternateFormats: [
			{ uri: 'aria-diff.html', label: "Diff from Previous Recommendation" } ,
			{ uri: 'aria.ps', label: "PostScript version" },
			{ uri: 'aria.pdf', label: "PDF version" }
		],
		*/

		// errata: 'http://www.w3.org/2010/02/rdfa/errata.html',

		// name of the WG
		wg:           "Accessible Rich Internet Applications Working Group",

		// URI of the public WG page
		wgURI:        "https://www.w3.org/WAI/ARIA/",

		// name (with the @w3c.org) of the public mailing to which comments are due
		wgPublicList: "public-aria",

		// URI of the patent status for this WG, for Rec-track documents
		// !!!! IMPORTANT !!!!
		// This is important for Rec-track documents, do not copy a patent URI from a random
		// document unless you know what you're doing. If in doubt ask your friendly neighbourhood
		// Team Contact.
		wgPatentURI:  "https://www.w3.org/2004/01/pp-impl/83726/status",
		//maxTocLevel: 2,

		localBiblio: biblio,

		// Spec URLs
        ariaSpecURLs: {
          "ED": "https://w3c.github.io/aria/aria/aria",
          "FPWD": "https://www.w3.org/TR/wai-aria-1.1/",
          "WD" : "https://www.w3.org/TR/wai-aria-1.1/",
          "CR": "https://www.w3.org/TR/wai-aria-1.1/",
          "REC": "https://www.w3.org/TR/wai-aria-1.1/"
        },

	};
		</script>
		<link href="common/css/common.css" rel="stylesheet" type="text/css" />
	</head>
	<body>

		<section id="abstract">
			<p>Personalization involves tailoring aspects of the user experience to meet the needs and preferences of the user. For example, having familiar terms and symbols is key to many users being able to use the web. However, what is familiar for one user may be unfamiliar to another requiring them to learn new symbols. The challenge has been the ability to identify the types of content in a document that should be adapted to the preferred user experience. The introduction of standardized semantics allows web applications to customize the exposure of that content to one that is familiar to individuals based on their needs and preferences. This specification defines standard semantics to enable user driven personalization such as the association of a user-preferred symbols to elements having those semantics. This ensures that users can quickly find familiar icons, such as a help icon, that apply to user interface elements.</p>
		</section>

		<section id="sotd"> </section>

		<section class="informative" id="introduction">
			<h1>Introduction</h1>
			<p>The goals of this specification include:</p>
			<ul>
				<li> expanding the accessibility information that may be supplied by the author;</li>
				<li> facilitate preference driven individual personalization;</li>
				<li> enable the author to specify key semantics needed to support users with cognitive impairments</li>
			</ul>
			<p>This is a proposal to define syntax for adaptable content such as: links, buttons, symbols, help and keyboard. This may be an WAI-ARIA COGA Extension.</p>
			<p>Personalization involves tailoring aspects of the user experience to meet the preferences or needs of the user. For example, having familiar terms and symbols is key to being able to use the web. However what is familiar for one user may be new for another requiring them to learn new symbols. Personalization could include loading a set of symbols that is appropriate for the specific user, ensuring that all users find the icons simple and familiar.</p>
			<p>Technology holds the promise of being extremely flexible and the design of many systems includes the expectation that users will be able to optimize their interaction experience according to their personal preferences or accessibility requirements (needs). </p>

			<section class="section" id="why_accessibility">
				<h2>Why We Need Personalization</h2>
				<p>We need personalization because: </p>
				<ul>
					<li>Different user needs can conflict</li>
					<li>Learning new design patterns (and widgets) can be confusing - we want to allow users to stick with what works for them </li>
					<li>Extra support can be annoying to people who do not need it </li>
					<li>Making content predictable is necessary for accessibility but can often be considered boring design </li>
					<li>Ability to change levels of complexity (increase or decrease) - As people skills improve or decrease over time or context. </li>
					<li>Enable us to really meet the user needs </li>
				</ul>
				<p>Some users need extra support. This can include: </p>
				<ul>
					<li> Symbols and graphics that they are familiar with </li>
					<li> Tool tips </li>
					<li> Language they understand </li>
					<li> Less features </li>
					<li> Separating advertisements, so they do not confuse them with native content </li>
					<li> Keyboard short cuts </li>
				</ul>
				<p>For this we need standardized terms and supportive syntax that can be linked to associated symbols, terms, translations and explanations for the individual use via an attribute and personal preferences. </p>
				<p>For example, assume an author can make it programanticaly known that a button is used to send an email. At at the user end, the button could be renderer with a symbol, term, and/or tooltips 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. </p>
				<p>Working examples of how this could be used in practice, with user preferences, are available at <a href="https://github.com/ayelet-seeman/coga.personalisation">https://github.com/ayelet-seeman/coga.personalisation</a>. This is a project to help personalization for any use - including people with learning and memory issues. It is described more at: <a href="https://www.w3.org/WAI/PF/cognitive-a11y-tf/wiki/Easy_Personalization">https://www.w3.org/WAI/PF/cognitive-a11y-tf/wiki/Easy_Personalization</a>. </p>
				<p>This project consists of 4 parts:</p>
				<ol>
					<li><a href="https://github.com/ayelet-seeman/coga.personalisation/tree/JSON-Script">JSON files for user setting</a></li>
					<li>Proposal for new syntax: (This document) <br /></li>
					<li>An HTML page that uses some of the new syntax: <a href="https://github.com/ayelet-seeman/coga.personalisation/tree/ExampleWebPage/">https://github.com/ayelet-seeman/coga.personalisation/tree/ExampleWebPage/</a></li>
					<li>Scripts that a web author can use or include that read the user settings in the JSON files and adapt the page for the user needs: <a href="https://github.com/ayelet-seeman/coga.personalisation/tree/Script-Options">https://github.com/ayelet-seeman/coga.personalisation/tree/Script-Options</a></li>
				</ol>
				<p>This is one example of personalization based on semantics. Others may follow. It is also worth noting that the GPII project is working on making user preferences portable which would also enhance this work.</p>
				<p>In another use-case 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 are not interoperable. That means end-users can only use one device, and can not use apps or AT from a different company. An open set of references for symbol codes for these symbol sets however, could be interoperable. That means the end user could use an open source symbol set or buy the symbols and use them across different devices or applications. Symbols could still be proprietary but they would also be interoperable. </p>
			</section>

			<section class="section" id="intro_context">
				<h2>Contextual Personalization</h2>
				<p>One important factor in optimizing the personalization of a product or service is to ensure that the personalization is appropriate for the current context of use. For example, settings that will suit the user of a mobile phone in their office or home will not be well suited to that user when they are driving a car. In a home or office, the typical user would probably prefer to send and receive text messages using the keyboard and screen of the mobile phone. However, in the car, voice input and text to speech output would be the most appropriate. In this car context, the profile settings of a typical user might be very similar to those that a blind user would use in all contexts.</p>
			</section>
		</section>

		<section class="informative" id="terms">
			<h1>Important Terms</h1>
			<div data-include="common/terms.html" data-oninclude="restrictReferences"></div>
		</section>

		<section class="normative" id="semanticProperties">
			<h1>Personalization Use Cases</h1> This Section covers use cases that can be addressed by personalization, and references the vocabulary items that help meet the use cases.<section>
				<h2>Simplification</h2>
				<p><strong>Requirement</strong>: The user must be able to 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 in the content. Typically, critical features may be used by many or most users, 90% of the time or more. High important features would be above 60% use. Medium important features would be 20% of users use it 20% of the time . Under 20% usage would be of low importance.</p>
				<p><strong>User experience</strong>: Based on personalization setting the user can see less options. A sample user experience is available at <a href="https://rawgit.com/ayelet-seeman/coga.personalisation/demo/conactUs.html">https://rawgit.com/ayelet-seeman/coga.personalisation/demo/conactUs.html </a></p>
				<p>Relevant properties: <a href="#simplification">simplification</a></p>
			</section>
			<section>
				<h2>Adding Context </h2>
				<p><strong>Requirement:</strong> 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. If a user agent or script knows the context of links, buttons, and other page elements then symbols and text used can be ones that the user understands. This can include: </p>
				<ul>
					<li> Symbols and graphics that they are familiar with </li>
					<li> Tool tips </li>
					<li> Language the use can understand </li>
					<li> Keyboard short cuts </li>
				</ul>
				<p>For that we need to standardize supportive syntax and terms that can be linked to associated symbols, terms, translations and explanations, for the individual, via an attribute.</p>
				<p><strong>Example user experience:</strong>, if an author gives to a button a role "send" then, without any work by the author, the button could be automatically rendered with a symbol, term, and/or tooltips that is understandable by a 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.</p>
				<p>Relevant properties: <a href="#action">action</a>, <a href="#destination">destination</a>, <a href="#field">field</a></p>
				<section>
					<h2>General context</h2>
					<p><strong>Requirement: </strong> One important factor in optimizing the personalization of a product or service is to ensure that the personalization is appropriate for the current context of use as well as what is relevant for the user. For example a female user with a cognitive disability may need less options, and options that are for men are less likely to be relevant for her and may be demoted to bellow the scroll or placed under a &quot;more option&quot; button.</p>
					<p>Relevant properties: <a href="#context">context</a></p>
				</section>
				<section>
					<h2>Interoperable symbols</h2>
					<p><strong>Requirement: </strong>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. </p>
					<p>User experience: AAC users will load symbols that they understand in different applications that are made by a different provider.</p>
					<p>Relevant properties: <a href="#concept">concept</a></p>
				</section>
			</section>
			<section>
				<h2>Potential parts of a page</h2>
				<p><strong>Requirement:</strong> The following could be extensions for aria landmarks or ePub </p>
				<p><strong>User experience:</strong> symbols and colors could be used consistently across different content. </p>
				<p>Links (such as ePub nav maps) can be automatically generated for people learn via keypoints or examples.</p>
				<p><strong>Examples:</strong>
				</p>
				<ul>
					<li>key points </li>
					<li>example </li>
					<li>note </li>
					<li>warning </li>
					<li>step </li>
					<li>external - for external content, such as sponsored or advertising </li>
					<li>offers - for special offers that are complementary to the main content or task </li>
					<li>advertisement - advertisement or sponsored content </li>
				</ul>
				<p>Relevant properties: @@</p>
			</section>
			<section>
				<h2>Number free</h2>
				<p><strong>Requirement</strong>: Not everyone can understand numbers. We therefor suggest aui-numberfree for alternative text for people who can not understand the main content</p>
				<p><strong>User experience:</strong></p>
				<p>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 tooltips would give the number free value</p>
				<p>Relevant properties: <a href="#numberfree">numberfree</a></p>
			</section>
			<section>
				<h2>Non-literal text and images</h2>
				<p><strong>Requirement: </strong>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.</p>
				<p><strong>User experience:</strong></p>
				<p>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 tooltips would give the literal value.</p>
				<p>Relevant properties: <a href="#literal">literal</a></p>
			</section>
			<section>
				<h2>Explain and feedback</h2>
				<p><strong>Requirement: </strong></p>
				<p>Some users need additional help. We request an attribute where the author can provide additional information or what just happened.</p>
				<p>Relevant properties: <a href="#feedback">feedback</a>, <a href="#explain">explain</a></p>
			</section>
			<section>
				<h3>More Help</h3>
				<p><strong>Requirement: </strong>Some users may need additional information or specifically additional help information. We request additional attributes so that an author can indicate the existence of this additional information.</p>
				<p>Relevant properties: <a href="#moreinfo">moreinfo</a>, <a href="#extrahelp">extrahelp</a>, <a href="#helptype">helptype</a></p>
			</section>
			<section>
				<h2>Potential Features</h2>
				<p>The following may not be necessary </p>
				<ul>
					<li>Views </li>
					<li>ascending. descending </li>
					<li>day, week month </li>
					<li>this week </li>
					<li>this month </li>
					<li>today </li>
				</ul>
			</section>
			<section>
				<h2>Language type support</h2>
				<p><strong>Requirement: </strong>Sometimes you may want to provide a simplified version of a section of a page. For example, you may wish to provide a simplified summary of legal document, but still have a longer version for other users. These alternative versions may not be identical in content but maintain the gist of the original content.</p>
				<p>Relevant properties: <a href="#alternative">alternative</a>, <a href="#easylang">easylang</a></p>
			</section>
			<section>
				<h3 id="logs">Logs</h3>
				<p>This proposal is to track the tasks that a user has done, so that they can be reminded of them, and return to or fix a task. The suggested syntax should allow the author to transform some of the information into breadcrumbs via CSS, and the user system can read and present more or less information to the user as per their preferences.</p>
				<p>Preferably this should be in the header so that the user agent can build a cross application log of user tasks.</p>
				<p>Note that there is no default value.</p>
				<p>Relevant properties: <a href="#log">log</a>, <a href="#step">step</a>, <a href="#actiontaken">actiontaken</a>, <a href="#steplocation">steplocation</a>, <a href="#status">status</a></p>
				<section>
					<h4>Log usage examples</h4>
					<pre>&lt;div aui-log="booking trip" aui-step="1" aria-label="buy ticket" aria-hidden="true"
    aui-actiontaken="bought ticket to NY return" steplocation ="uri" /></pre>
					<p>or</p>
					<pre>&lt;div aui-log="booking trip" aui-step="1" aui-actiontaken="bought ticket to NY return">
  buy ticket
  &lt;a href="uri">change&lt;/a>
&lt;/div></pre>
					<p>or the step number can be implied by the DOM</p>
					<pre>&lt;div aui-log="booking trip">
  &lt;div aui-actiontaken="bought ticket to NY return">
    buy ticket
    &lt;a href="uri">change&lt;/a>
  &lt;/div>
&lt;/div></pre>
				</section>
				<section>
					<h4>Alternative syntax for log</h4>
					<p>Note we are considering supporting an alternative syntax such as:</p>
					<pre>&lt;log name="booking trip">
  &lt;step status ="done">
    &lt;name>buy ticket&lt;/name>
    &lt;actiontaken>bought ticket to NY return&lt;/actiontaken>
    &lt;view changepossible="yes">url &lt;/view>
  &lt;/step>
  &lt;step  status ="done">
    &lt;name>hotel&lt;/name>
    &lt;actiontaken>booked Sheraton single room&lt;/actiontaken>
    &lt;view changepossible="yes">url &lt;/view>
  &lt;/step>
  &lt;step  status ="current">
    &lt;name>car rental&lt;/name>
    &lt;view current changepossible="yes"/>
  &lt;/step>
&lt;/log>
</pre>
				</section>
			</section>
			<section>
				<h3>Reminders and messages</h3>
				<p><strong>Requirement: </strong>We require an attribute that enables different users to experience different amount of reminders and messages based on personal preferences. Reminders are a wonderful tool for many people with cognitive disabilities. However too many reminders will be annoying or distracting for some other users. Currently people can turn off distractions such as Skype, and Facebook, across different devices, and then may forget to turn them back on.</p>
				<p>These semantics allow for different solutions so that users are able to focus without missing important messages. Users need to manage all distractions by forming a cross application and cross device distraction matrix that manages all distractions in one setting. It is based on a matrix for distractions at the operating system , browser or cloud level. People and users can be clustered in terms of importance or groups. For example, the CEO and your child's care giver could both be considered critical contacts. So even if they do not feel the message is urgent they can sometimes disrupt the user anyway. Some family members and important colleagues can be in another group, friends and extended family in a third group, system messages from the compliance system can be a different group again. </p>
				<p>Relevant properties: <a href="#messageimportance">messageimportance</a>, <a href="#messagefrom">messagefrom</a>, <a href="#messagecontext">messagecontext</a>, <a href="#messagetime">messagetime</a></p>
			</section>
			<section>
				<h2>Distractions</h2>
				<p><strong>Requirement: </strong> We require an attribute that indicates a distraction so that some users may be able to remove them from content.</p>
				<p>Relevant properties: <a href="#distraction">distraction</a></p>
			</section>
			<section>
				<h2>New Misc.</h2> Triggers: for emotional support. aui-trigger: violent, racism, etc. aui-keyparts of the page: key points, example, note, warning, external (content), advertisements, (some may be in digital publishing) aui-dates - (cancellation, return) </section>
		</section>
		<section id="characteristics_semanticproperties">
			<h2>Structure of Properties</h2>
			<p>Semantic properties have the characteristics described in the following sections.</p>
			<section id="propcharacteristic_relatedconcept">
				<h3>Related Concepts</h3>
				<p>Advisory information about features from this or other languages that correspond to this <a>property</a>. While the correspondence may not be exact, it is useful to help understand the intent of the state or property.</p>
			</section>
			<section id="propcharacteristic_value">
				<h3>Value</h3>
				<p>Value type of the semantic <a>property</a>. The value may be one of the following types:</p>
				<dl>
					<dt id="valuetype_true-false">true/false</dt>
					<dd>Value representing either true or false, with a default &quot;false&quot; value.</dd>
					<dt id="valuetype_true-false-undefined">true/false/undefined</dt>
					<dd>Value representing true or false, with a default &quot;undefined&quot; value indicating the state or property is not relevant.</dd>
					<dt id="valuetype_idref">ID reference</dt>
					<dd>Reference to the ID of another <a>element</a> in the same document</dd>
					<dt id="valuetype_idref_list">ID reference list</dt>
					<dd>A list of one or more ID references.</dd>
					<dt id="valuetype_integer">integer</dt>
					<dd>A numerical value without a fractional component.</dd>
					<dt id="valuetype_number">number</dt>
					<dd>Any real numerical value.</dd>
					<dt id="valuetype_string">string</dt>
					<dd>Unconstrained value type.</dd>
					<dt id="valuetype_token">token</dt>
					<dd>One of a limited set of allowed values.</dd>
					<dt id="valuetype_token_list">token list</dt>
					<dd>A list of one or more tokens.</dd>
					<dt id="valuetype_uri">URI</dt>
					<dd>A Uniform Resource Identifier as defined by <cite><a href="http://www.ietf.org/rfc/rfc3986.txt">RFC 3986</a></cite> [[RFC3986]]. It may reference a separate document, or a content fragment identifier in a separate document, or a content fragment identifier within the same document.</dd>
				</dl>
				<p>The "undefined" value, when allowed on a state or property, is an explicit indication that the state or property is not set. The value is used on states and properties that support tokens, and the &quot;undefined&quot; value is a string that is one of the allowed tokens. It is also used on some states and properties that accept true/false values, when &quot;undefined&quot; has a different meaning than &quot;false&quot;.</p>
				<p>These are generic types for states and properties, but do not define specific representation. See <a href="#state_property_processing" class="specref">State and Property Attribute Processing</a> for details on how these values are expressed and handled in host languages.</p>
			</section>
		</section>

		<section>
					<h2>List of properties</h2>
					<section class="property">
						<h3>simplification</h3>
						<div class="property-description">
							<p>The <code>simplification</code> attribute differentiates between critical features and less important features for simplification.</p>
							<p>This allows simplified interfaces with less options or interfaces that emphasize critical features. Adaptations can be based on personalization settings. </p>
							<div class="example"><div class="example-title marker"><span>Example:</span><span style="text-transform: none"> Simplification Using ARIA</span></div>
							&lt;input aui-simplification="critical" aria-function="submit" value="Submit" type="submit"/&gt;
							</div>

							 <p class="ednote">This was formerly aui-importance. However different people may feel that sections that would be hidden in a simplified version are still very important, such as marketing content or legal terms.)</p>

							<div class="note">
								<p>These semantics aid simplification. But what content is most useful to a user varies from user to user. For example, men may be more interested in mens clothing, and may not be interested in the more frequently use womens clothing option. For that reason we may add context for elements that will help the personalization agent select the most useful content for a given user (see the <a href="#context">context</a> attribute). This is also necessary for reminders (see bellow).</p>
								<p>It is worth mentioning that a lot of this information is known for personalization of advertisements and content optimization. </p>
							</div>
						</div>
						<table class="property-features">
							<caption>Characteristics:</caption>
							<thead>
								<tr>
									<th scope="col">Characteristic</th>
									<th scope="col">Value</th>
								</tr>
							</thead>
							<tbody>
								<tr>
									<th class="property-related-head" scope="row">Related Concepts:</th>
									<td class="property-related"><cite><a href="https://www.w3.org/TR/SVG2/"><abbr title="Scalable Vector Graphics">SVG</abbr></a></cite> [[SVG2]] and <cite><a href="https://www.w3.org/TR/dom/"><abbr title="Document Object Model">DOM</abbr></a></cite> [[DOM4]] active</td>
								</tr>
								<tr>
									<th class="property-applicability-head" scope="row">Used in Roles:</th>
									<td class="property-applicability">All elements of the base markup</td>
								</tr>
								<tr>
									<th class="property-descendants-head" scope="row">Inherits into Roles:</th>
									<td class="property-descendants">Placeholder</td>
								</tr>
								<tr>
									<th class="property-value-head" scope="row">Value:</th>
									<td class="property-value"><a href="#valuetype_token">token</a></td>
								</tr>
							</tbody>
						</table>
						<table class="value-descriptions">
							<caption>Values:</caption>
							<thead>
								<tr>
									<th scope="col">Value</th>
									<th scope="col">Description</th>
								</tr>
							</thead>
							<tbody>
							<tr>
														<th class="value-name" scope="row">simplest</th>
														<td class="value-description">This setting should be used on: <ul>
															<li> Elements that are essential for the key function (from the user perspective) of the page (Example: The send button for an email draft in an email application) or</li>
															<li> Elements that are sometimes critical to a user being able to use the site, such as &quot;save my work&quot; or &quot;emergency instructions&quot; or</li>
															<li> Elements that are used by over 90% of a user group (such as parents or teachers) use this element most times they use the content<br />
															</li>
														</ul>

												<p>Typically 3 links or buttons would be considered &quot;simplest&quot;</p></td>
								</tr>
								<tr>
									<th class="value-name" scope="row"><strong class="default">medium (default)</strong></th>
									<td class="value-description">
									 This setting should be used on: <ul>
										<li> Elements that are used frequent but are not essential for the key functioning pf the application. (Example: The delete button for an email draft in an email application) or</li>
										<li> Elements that are sometimes important to a user being able to use the site, such as settings or</li>
										<li> Elements that are used by frequently (over 60%) by a user group (such as parents or teachers) use this element most times they use the content</li>
									</ul></td>
								</tr>

								<tr>
									<th class="value-name" scope="row">low</th>
									<td class="value-description">This setting should be used on elements that are rarely used or only used by advanced users. (Example: The terms and services or the archive button for an email application.)
							         </td>
								</tr>

							</tbody>
						</table>
					</section>


			<section class="property">
				<h3>action</h3>
				<div class="property-description">
				    <p>The <code>action</code> attribute provides the context of a button. It is typically used on a button element or element with role="button".</p>

 					<pre class="example" title="Action Using ARIA">
					   <p>For example: &lt;button aui-action=&quot;undo&quot; &gt;Revert&lt;/button&gt;</p>
					   <p>A personalization agent may add a symbol, replace the text with a more familiar term, or give it a specific presentation. Note that there is no default value.</p>
                    </pre>
                </div>

				<table class="property-features">
					<caption>Characteristics:</caption>
					<thead>
						<tr>
							<th scope="col">Characteristic</th>
							<th scope="col">Value</th>
						</tr>
					</thead>
					<tbody>
						<tr>
							<th class="property-related-head" scope="row">Related Concepts:</th>
							<td class="property-related"><cite><a href="https://www.w3.org/TR/html5/links.html#linkTypes">link types</a></cite> [[Links]] and <cite><a href="https://www.w3.org/TR/html5/forms.html#states-of-the-type-attribute"><abbr title="Hypertext Markup Language ">HTML </abbr> types</a></cite> [[Types]]</td>
						</tr>
						<tr>
							<th class="property-applicability-head" scope="row">Used in Roles:</th>
							<td class="property-applicability">All elements of the base markup</td>
						</tr>
						<tr>
							<th class="property-descendants-head" scope="row">Inherits into Roles:</th>
							<td class="property-descendants">Placeholder</td>
						</tr>
						<tr>
							<th class="property-value-head" scope="row">Value:</th>
							<td class="property-value"><a href="#valuetype_token">token</a></td>
						</tr>
					</tbody>
				</table>
                <p>The following could be supported values of <code>aui-action</code> for buttons:</p>
				<table class="value-descriptions">
					<caption>Values:</caption>
					<thead>
						<tr>
							<th scope="col">Value</th>
							<th scope="col">Description</th>
						</tr>
					</thead>
					<tbody>
						<tr>
							<th class="value-name" scope="row">compose</th>
							<td class="value-description">compose new item such as an email. (Implied simplification = "critical".)</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">next</th>
							<td class="value-description">move to the next item in the series. (Implied simplification  = "critical".)</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">delete</th>
							<td class="value-description">delete current item, selected control or text</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">previous</th>
							<td class="value-description">move to the previous item in the series. (Implied simplification  = "critical".)</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">toc</th>
							<td class="value-description">opens a table of content</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">submit</th>
							<td class="value-description">submits the form data or request to the server. (Implied simplification  = "critical".)</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">undo</th>
							<td class="value-description">revert to the state before the user's most recent changes</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">cancel</th>
							<td class="value-description">closes the dialog and discards any changes the user may have made within that dialog. (Implied simplification  = "critical".)</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">reset</th>
							<td class="value-description">resets all the controls to their initial values</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">label</th>
							<td class="value-description">add label to the selected item or the item at the current location.</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">buy</th>
							<td class="value-description">buy the selected item or buy the item at the current location. Often involves adding the current item into a shopping cart. (Implied simplification  = "critical".)</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">add</th>
							<td class="value-description">add the selected item or the item at the current location to a list</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">move</th>
							<td class="value-description">move the selected item <p class</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">save</th>
							<td class="value-description">save the current content. (Implied simplification = "critical".)</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">send</th>
							<td class="value-description">send a form, email or request. (Implied simplification = "critical".)</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">close</th>
							<td class="value-description">close current dialog. (Implied simplification = "critical".)</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">more</th>
							<td class="value-description">show more information <p class="ednote" > We may need more work to identify the dirction (up left degree etc) but there may be a way to do that already </p></td>
						</tr>
						<tr>
							<th class="value-name" scope="row">print</th>
							<td class="value-description">print current page, selection or the item at the current location</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">received</th>
							<td class="value-description">open received folder</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">sent</th>
							<td class="value-description">open sent folder</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">edit</th>
							<td class="value-description">edit current item, selection or the item at the current location</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">forward</th>
							<td class="value-description">forward to current item such as an email</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">reply</th>
							<td class="value-description">reply to current item such as an email. (Implied simplification = "critical".)</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">upload</th>
							<td class="value-description">upload file to the server</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">open</th>
							<td class="value-description">open item. (Implied simplification = "critical".)</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">new</th>
							<td class="value-description">open new item. (Implied simplification= "critical".)</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">settings</th>
							<td class="value-description">open settings and options</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">mode</th>
							<td class="value-description">change the mode or functionality. (Implied simplification= "critical".)</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">higher</th>
							<td class="value-description">increases the level of the relevant setting. (Implied simplification= "critical".)</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">lower</th>
							<td class="value-description">increases the level of the relevant setting. (Implied simplification= "critical".)</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">profile</th>
							<td class="value-description">opens the user's profile page</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">expand</th>
							<td class="value-description">expand or unexpand the current item</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">refresh</th>
							<td class="value-description">manually refresh the current contents of the screen</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">properties</th>
							<td class="value-description">shows the properties of the item</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">help</th>
							<td class="value-description">opens a help function. (Implied simplification= "critical".)</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">cut</th>
							<td class="value-description">removes the selected control, item or text and places it on the Clipboard</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">copy</th>
							<td class="value-description">copies the selected control, item or text onto the Clipboard</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">color</th>
							<td class="value-description">opens a color picker</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">date</th>
							<td class="value-description">opens a date control. (Implied simplification= "critical".)</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">remove</th>
							<td class="value-description">remove an item from a list</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">right</th>
							<td class="value-description">moves a selected item to the right to another column or list</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">left</th>
							<td class="value-description">moves a selected item to the left to another column or list</td>
						</tr>
					</tbody>
				</table>
			</section>

			<section class="property">
				<h3>destination</h3>
				<div class="property-description">
					<p>The <code>destination</code> term categorizes the target of a hyperlink.</p>
					<p>A personalization agent or user agent may add additional familiar user interface features to help users understand the link and follow the right one easily. User agents might add a familiar customized icon to the link, or style the link in a customized way, or position the link on the page in a location that the user generally expects to find a link of the particular type.</p>
					<pre class="example" title="Destination Using ARIA">&lt;a href=&quot;home.html&quot; aui-destination=&quot;home&quot;&gt;our main page&lt;/a&gt;</pre>
					<p>See the <a href="https://rawgit.com/ayelet-seeman/coga.personalisation/demo/conactUs.html">destination sample user experience</a>.</p>

				</div>
				<table class="property-features">
					<caption>Characteristics:</caption>
					<thead>
						<tr>
							<th scope="col">Characteristic</th>
							<th scope="col">Value</th>
						</tr>
					</thead>
					<tbody>
						<tr>
							<th class="property-related-head" scope="row">Related Concepts:</th>
							<td class="property-related"><cite><a href="https://www.w3.org/TR/html5/links.html#linkTypes">link types</a></cite> [[Links]] and <cite><a href="https://www.w3.org/TR/html5/forms.html#autofilling-form-controls:-the-autocomplete-attribute"><abbr title="Hypertext Markup Language ">HTML </abbr> autocomplete</a></cite> [[Autocomplete]] </td>
						</tr>
						<tr>
							<th class="property-applicability-head" scope="row">Used in Roles:</th>
							<td class="property-applicability">All elements of the base markup</td>
						</tr>
						<tr>
							<th class="property-descendants-head" scope="row">Inherits into Roles:</th>
							<td class="property-descendants">Placeholder</td>
						</tr>
						<tr>
							<th class="property-value-head" scope="row">Value:</th>
							<td class="property-value"><a href="#valuetype_token">token</a></td>
						</tr>
					</tbody>
				</table>
				<table class="value-descriptions">
					<caption>Values:</caption>
					<thead>
						<tr>
							<th scope="col">Value</th>
							<th scope="col">Description</th>
						</tr>
					</thead>
					<tbody>
						<tr>
							<th class="value-name" scope="row">home</th>
							<td class="value-description">initial or main page of a website or application</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">contact</th>
							<td class="value-description">opens contact information for content owner or producer</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">phone</th>
							<td class="value-description">phone content owner or producer</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">email</th>
							<td class="value-description">email content owner or producer</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">sitemap</th>
							<td class="value-description">content containing a list of pages in a web site</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">help</th>
							<td class="value-description">a help function, support or instructions</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">chat</th>
							<td class="value-description">Human help or a dialog help function such as a chat bot</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">about</th>
							<td class="value-description">information about the content owner or producer</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">terms</th>
							<td class="value-description">terms and conditions</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">tools</th>
							<td class="value-description">available tools for the current content</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">services</th>
							<td class="value-description">services available from the content provider</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">products</th>
							<td class="value-description">products available from the content provider</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">comment</th>
							<td class="value-description">submit a comment on the current item</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">language</th>
							<td class="value-description">language options</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">signin</th>
							<td class="value-description">sign in to current web site or application</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">signout</th>
							<td class="value-description">sign out current web site or application</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">register</th>
							<td class="value-description">register for the current web site or application</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">social</th>
							<td class="value-description">content provider on social media</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">post</th>
							<td class="value-description">post current item. Item will be visible to other parties.</td>
						</tr>
					</tbody>
				</table>
			</section>


			<section class="property">
				<h3>field</h3>
				<div class="property-description">
					<p><code>field</code> provides the context of a text input field such as a text box. It is typically used on an input of type text, or element with a responding role.</p>
					<pre class="example" title="Fields Using ARIA">
              <p>&lt;input type="text" name="fname" aui-field=&quot;phone&quot;/&gt;</p>
					</pre>
					<p>A personalization agent may add a symbol, replace the text with a more familiar term, or give it a specific presentation. Note that there is no default value.</p><p>The user experience may include filling in the field and adding an icon.</p>
					<p>aui-field values that would typically be on form controls and would have a user context - for example phone would relate to the user's phone. Note that there is no default value.</p>
					<p>Note they can be more then one value for a field, such as <code>aui-field=&quot;country postcode&quot;</code></p>
				</div>
				<table class="property-features">
					<caption>Characteristics:</caption>
					<thead>
						<tr>
							<th scope="col">Characteristic</th>
							<th scope="col">Value</th>
						</tr>
					</thead>
					<tbody>
						<tr>
							<th class="property-related-head" scope="row">Related Concepts:</th>
							<td class="property-related"><cite><a href="https://www.w3.org/TR/html5/links.html#linkTypes">link types</a></cite> [[Links]] and <cite><a href="https://www.w3.org/TR/html5/forms.html#states-of-the-type-attribute"><abbr title="Hypertext Markup Language ">HTML </abbr> types</a></cite> [[Types]]</td>
						</tr>
						<tr>
							<th class="property-applicability-head" scope="row">Used in Roles:</th>
							<td class="property-applicability">All elements of the base markup</td>
						</tr>
						<tr>
							<th class="property-descendants-head" scope="row">Inherits into Roles:</th>
							<td class="property-descendants">Placeholder</td>
						</tr>
						<tr>
							<th class="property-value-head" scope="row">Value:</th>
							<td class="property-value"><a href="#valuetype_token">token</a></td>
						</tr>
					</tbody>
				</table>
				<table class="value-descriptions">
					<caption>Values:</caption>
					<thead>
						<tr>
							<th scope="col">Value</th>
							<th scope="col">Description</th>
						</tr>
					</thead>
					<tbody>
						<tr>
							<th class="value-name" scope="row">name</th>
							<td class="value-description">full name</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">honorific-prefix</th>
							<td class="value-description">prefix or title (Mr., Mrs. Dr., etc.) </td>
						</tr>
						<tr>
							<th class="value-name" scope="row">given-name</th>
							<td class="value-description">given or first name</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">additional-name</th>
							<td class="value-description">additional or middle name</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">additional-name-initial</th>
							<td class="value-description">additional or middle name initial</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">family-name</th>
							<td class="value-description">family name, surname, or last name</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">honorific-suffix</th>
							<td class="value-description">suffix (Jr., II, etc.)</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">nickname</th>
							<td class="value-description">nickname</td>
						</tr>
                        <tr>
                            <th class="value-name" scope="row">street-address</th>
                            <td class="value-description">full street address condensed into one line</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">address-line1</th>
							<td class="value-description">first line of street address </td>
						</tr>
						<tr>
							<th class="value-name" scope="row">address-line2</th>
							<td class="value-description">second line of street address</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">address-line3</th>
							<td class="value-description">third line of street address</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">city</th>
							<td class="value-description">locality or city</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">area</th>
							<td class="value-description">administrative area, state, province, or region</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">postalcode</th>
							<td class="value-description">postal or ZIP code</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">country</th>
							<td class="value-description">country name</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">fax</th>
							<td class="value-description">full fax number, including country code</td>
						</tr>
                        <tr>
							<th class="value-name" scope="row">fax-country-code</th>
							<td class="value-description">international country code</td>
						</tr>

                        <tr>
							<th class="value-name" scope="row">fax-national</th>
							<td class="value-description">national fax number: full number minus country code</td>
						</tr>
                        <tr>
                            <th class="value-name" scope="row">fax-area-code</th>
                            <td class="value-description">area code</td>
                        </tr>
                        <tr>
							<th class="value-name" scope="row">fax-local</th>
							<td class="value-description">local fax number: full number minus country and area codes</td>
						</tr>
                        <tr>
							<th class="value-name" scope="row">fax-extension</th>
							<td class="value-description">fax extension number</td>
						</tr>
                        <tr>
							<th class="value-name" scope="row">email</th>
							<td class="value-description">email address</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">tel</th>
							<td class="value-description">full phone number, including country code</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">tel-country-code</th>
							<td class="value-description">international country code</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">tel-national</th>
							<td class="value-description">national phone number: full number minus country code</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">tel-area-code</th>
							<td class="value-description">area code</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">tel-local</th>
							<td class="value-description">local phone number: full number minus country and area codes</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">tel-extension</th>
							<td class="value-description">phone extension number</td>
						</tr>
				        <tr>
							<th class="value-name" scope="row">cc-name</th>
							<td class="value-description">full name, as it appears on credit card</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">cc-number</th>
							<td class="value-description">credit card number</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">cc-exp-month</th>
							<td class="value-description">month of expiration of credit card</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">cc-exp-year</th>
							<td class="value-description">year of expiration of credit card</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">cc-exp</th>
							<td class="value-description">date of expiration of credit card</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">cc-csc</th>
							<td class="value-description">credit card security code</td>
						</tr>
                        <tr>
							<th class="value-name" scope="row">language</th>
							<td class="value-description">preferred language</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">bday</th>
							<td class="value-description">birthday</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">bday-year</th>
							<td class="value-description">year of birthday</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">bday-month</th>
							<td class="value-description">month of birthday</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">bday-day</th>
							<td class="value-description">day of birthday</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">topic</th>
							<td class="value-description">Topic for the form. Typically selected from a list of reserved words</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">comment</th>
							<td class="value-description">comment section. Typically a free text field</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">subject</th>
							<td class="value-description">form subject. Typically a free text field</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">answer</th>
							<td class="value-description">answer to a section question</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">org</th>
							<td class="value-description">company or organization</td>
						</tr>
                        <tr>
							<th class="value-name" scope="row">organization-title</th>
							<td class="value-description">user's position or title within company or organization</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">sex</th>
							<td class="value-description">sex or gender</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">gender</th>
							<td class="value-description">gender identity</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">url</th>
							<td class="value-description">Website URL</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">photo</th>
							<td class="value-description">photo or avatar</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">section-*****</th>
							<td class="value-description">used to group forms together</td>
						</tr>
					</tbody>
				</table>
			</section>
			<section class="property">
				<h3>context</h3>
				<div class="property-description">
					<p><code>context</code> gives additional contextual information about the content.</p>
					<p><code>context</code> accepts the values of a URI or shortened URI. Note that namespaces are the only additional parsing that maybe required to identify the concept.</p>
					<p>These semantics aid simplification. What content is most useful to a user varies from user to user. For example, men may be more interested in mens clothing, and may not be interested in the more frequently use womens clothing option. For that reason adding context for elements that will help the personalization agent select the most useful content for a given user. </p>
					<div class="example"><div class="example-title marker"><span>Example:</span><span style="text-transform: none"> Context Using ARIA</span></div>&lt;a href=&quot;women.html&quot; aui-context=&quot;http://schema.org/Female&quot;&gt;women&lt;/a&gt; </div>

					<p class="note">To help this be interoperable without an RDF parser we  recommend using the most commonly used ontologies. </p>
				</div>
				<table class="property-features">
					<caption>Characteristics:</caption>
					<thead>
						<tr>
							<th scope="col">Characteristic</th>
							<th scope="col">Value</th>
						</tr>
					</thead>
					<tbody>
						<tr>
							<th class="property-related-head" scope="row">Related Concepts:</th>
							<td class="property-related"><cite><a href="https://www.w3.org/TR/microdata/#the-basic-syntax">microdate</a></cite> [[microdate]] and <cite><a href="https://www.w3.org/TR/rdfa/">RDFa [[RDFa]]</td>
						</tr>
						<tr>
							<th class="property-applicability-head" scope="row">Used in Roles:</th>
							<td class="property-applicability">All elements of the base markup</td>
						</tr>
						<tr>
							<th class="property-descendants-head" scope="row">Inherits into Roles:</th>
							<td class="property-descendants">Placeholder</td>
						</tr>
						<tr>
							<th class="property-value-head" scope="row">Value:</th>
							<td class="property-value"><a href="#valuetype_uri">URI</a></td>
						</tr>
					</tbody>
				</table>
			</section>
			<section class="property">
				<h3>symbol</h3>
				<div class="property-description">
				<p><code>symbol</code> identifies the concept for symbols.</p>
				<p><code>symbol</code> accepts the values of a URI or shortened URI. Note that namespaces are the only additional parsing that maybe required to identify the concept.</p>
				<p>A personalization agent can then load alternative symbols that the user is familiar with and they do not have to learn new symbols for different applications. </p>
										<div class="example"><div class="example-title marker"><span>Example:</span><span style="text-transform: none"> Symbol Using ARIA</span></div>&lt;img aui-symbol="http://wordnet-rdf.princeton.edu/wn31/girl-n" href="mygirlsy.bmp"/&gt; </div>

										<p class="note">To help this be interoperable without an RDF parser we  recommend referencing the most commonly used ontologies and the highest level concept. (For example, reference "girl" and not "young girl" .) </p>
										<p class="ednote">We should have a note of common suggested terms and references. (Maybe with links to http://www.arasaac.org/) </p>

									</div>
									<table class="property-features">
										<caption>Characteristics:</caption>
										<thead>
											<tr>
												<th scope="col">Characteristic</th>
												<th scope="col">Value</th>
											</tr>
										</thead>
										<tbody>
											<tr>
												<th class="property-related-head" scope="row">Related Concepts:</th>
												<td class="property-related"><cite><a href="https://www.w3.org/TR/microdata/#the-basic-syntax">microdate</a></cite> [[microdate]], <cite><a href="http://www.w3.org/TR/2005/WD-swbp-skos-core-guide-20051102">SKOS Core Guide</a></cite> [[SKOS]] and <cite><a href="https://www.w3.org/TR/rdfa/">RDFa [[RDFa]]</td>
											</tr>
											<tr>
												<th class="property-applicability-head" scope="row">Used in Roles:</th>
												<td class="property-applicability">All elements of the base markup</td>
											</tr>
											<tr>
												<th class="property-descendants-head" scope="row">Inherits into Roles:</th>
												<td class="property-descendants">Placeholder</td>
											</tr>
											<tr>
												<th class="property-value-head" scope="row">Value:</th>
												<td class="property-value"><a href="#valuetype_uri">URI</a></td>
											</tr>
										</tbody>
				</table>
			</section>
			<section class="property">
				<h3>numberfree</h3>
				<div class="property-description">
					<p><code>numberfree</code> provides alternative text for people who prefer content that does not use numerical concepts.</p>
					<p>A personalization agent may replace the content with the number free alternative, or it may put the number free alternative in a tooltip or sidebar. The content must still be understandable when a user agent replaces the original content with the number free alternative.</p> </p>

					<p><strong>Supported value: </strong> String</p>
					<p>Note that there is no default value.</p>
					<div class="example"><div class="example-title marker"><span>Example 1</span><span style="text-transform: none">: Numberfree Using ARIA</span></div>
					<pre>&lt;span aui-numberfree=&quot;almost all&quot;&gt;9 out of 10 &lt;/span&gt;
			</div>
			<div class="example"><div class="example-title marker"><span>Example 2</span><span style="text-transform: none">: Numberfree Using ARIA</span></div>
			<pre>&lt;span aui-numberfree=&quot;hat and coat weather&quot;&gt;The weather is 9 degrees&lt;/span&gt;</pre>
			</div>
				</div>
				<table class="property-features">
					<caption>Characteristics:</caption>
					<thead>
						<tr>
							<th scope="col">Characteristic</th>
							<th scope="col">Value</th>
						</tr>
					</thead>
					<tbody>
						<tr>
							<th class="property-related-head" scope="row">Related Concepts:</th>
							<td class="property-related">Alt text </td>
						</tr>
						<tr>
							<th class="property-applicability-head" scope="row">Used in Roles:</th>
							<td class="property-applicability">All elements of the base markup</td>
						</tr>
						<tr>
							<th class="property-descendants-head" scope="row">Inherits into Roles:</th>
							<td class="property-descendants">Placeholder</td>
						</tr>
						<tr>
							<th class="property-value-head" scope="row">Value:</th>
							<td class="property-value"><a href="#valuetype_string">string</a></td>
						</tr>
					</tbody>
				</table>
			</section>
			<section class="property">
				<h3>literal</h3>
				<div class="property-description">
					<p><code>literal</code> provides alternative text for people who prefer content that does not use non literal text, such as metaphors.</p>
					<p>A personalization agent may replace the content with the literal alternative, or it may put the literal alternative in a tooltip.</p>
					<p>User agents may also render non-literal text in a different way so that users will be able to identify non literal content. They can then use a mouse over or other technique to receive the alternative. </p>
					<p>A user agent must be able to replace the non literal content with the literal alternative without loss of meaning.</p>
					<p><strong>Supported value: </strong>String</p>
					<p>Note that there is no default value.</p>
					<div class="example"><div class="example-title marker"><span>Example</span><span style="text-transform: none">: Literal Using ARIA</span></div>
					<pre>It is &lt;span aui-literal=&quot;raining hard&quot;&gt;raining cats and dogs&lt;/span&gt;</pre>
					</div>

				</div>
				<table class="property-features">
					<caption>Characteristics:</caption>
					<thead>
						<tr>
							<th scope="col">Characteristic</th>
							<th scope="col">Value</th>
						</tr>
					</thead>
					<tbody>
						<tr>
							<th class="property-related-head" scope="row">Related Concepts:</th>
							<td class="property-related">Alt text</td>
						</tr>
						<tr>
							<th class="property-applicability-head" scope="row">Used in Roles:</th>
							<td class="property-applicability">All elements of the base markup</td>
						</tr>
						<tr>
							<th class="property-descendants-head" scope="row">Inherits into Roles:</th>
							<td class="property-descendants">Placeholder</td>
						</tr>
						<tr>
							<th class="property-value-head" scope="row">Value:</th>
							<td class="property-value"><a href="#valuetype_string">string</a></td>
						</tr>
					</tbody>
				</table>
			</section>
			<section class="property">
							<h3>easylang</h3>
							<div class="property-description">
								<p><code>easylang</code> provides an alternative text of the content that is easier to read and understand. Note that this only works on small sections of text as the easylang attribute does not support full HTML, such as lists and sections.</p>
								<p>
								A personalization agent may replace the content with the simpler alternative, or it may put the  alternative in a tooltip or help panel.</p>
								<p>
								User agents may also render hard text in a different way so that users will be able to identify text that has an alternative provided. </p>
								<p>The content must still be understandable when a user agent replaces the original content with the simpler alternative.</p>
								<p><strong>Supported values:</strong> String</p>
								<div class="example"><div class="example-title marker"><span>Example</span><span style="text-transform: none">: Easylang Using ARIA</span></div>
								<pre>&lt;span aui-easylang=&quot;some text that is easy to read&quot;&gt; some convoluted obtuse text&lt;/span&gt;</pre></div>
								<p>Where aui-easylang should use as simple well-known words as possible, and active voicing, literal text, small simple sentences.&nbsp;Acronyms and abbreviations should be avoided, unless they are the common way to refer to an item.</p>
							</div>
							<table class="property-features">
								<caption>Characteristics:</caption>
								<thead>
									<tr>
										<th scope="col">Characteristic</th>
										<th scope="col">Value</th>
									</tr>
								</thead>
								<tbody>
									<tr>
										<th class="property-related-head" scope="row">Related Concepts:</th>
										<td class="property-related"> Alt text</td>
									</tr>
									<tr>
										<th class="property-applicability-head" scope="row">Used in Roles:</th>
										<td class="property-applicability">All elements of the base markup</td>
									</tr>
									<tr>
										<th class="property-descendants-head" scope="row">Inherits into Roles:</th>
										<td class="property-descendants">Placeholder</td>
									</tr>
									<tr>
										<th class="property-value-head" scope="row">Value:</th>
										<td class="property-value"><a href="#valuetype_string">string</a></td>
									</tr>
								</tbody>
							</table>

			<section class="property">
				<h3>feedback</h3>
				<div class="property-description">
					<p>This attribute provides immediate feedback that can be shown or spoken when any event is triggered on a control.</p>
					<p><strong>User experience: </strong>This can be rendered as text at the top of the page and read immediately. Most users will not want this text rendered and spoken. Other users however will need it to know what has just happened. </p>
				</div>
				<table class="property-features">
					<caption>Characteristics:</caption>
					<thead>
						<tr>
							<th scope="col">Characteristic</th>
							<th scope="col">Value</th>
						</tr>
					</thead>
					<tbody>
						<tr>
							<th class="property-related-head" scope="row">Related Concepts:</th>
							<td class="property-related"><cite><a href="https://www.w3.org/TR/SVG2/"><abbr title="Scalable Vector Graphics">SVG</abbr></a></cite> [[SVG2]] and <cite><a href="https://www.w3.org/TR/dom/"><abbr title="Document Object Model">DOM</abbr></a></cite> [[DOM4]] active</td>
						</tr>
						<tr>
							<th class="property-applicability-head" scope="row">Used in Roles:</th>
							<td class="property-applicability">All elements of the base markup</td>
						</tr>
						<tr>
							<th class="property-descendants-head" scope="row">Inherits into Roles:</th>
							<td class="property-descendants">Placeholder</td>
						</tr>
						<tr>
							<th class="property-value-head" scope="row">Value:</th>
							<td class="property-value"><a href="#valuetype_string">string</a></td>
						</tr>
					</tbody>
				</table>
			</section>
			<section class="property">
				<h3>explain</h3>
				<div class="property-description">
					<p>This attribute provides any information that helps the user anticipate the functionality, such as letting the user know what behavior will trigger an event. This is most important if the mechanism is not standard. </p>
					<p>User experience: This help can be rendered as a tool tip, help link or read when the control or link is read. Most users will not want this text rendered or spoken, but other users however will need it to understand the behavior of the element.</p>
					<p>Note that there is no default value.</p>
					<p><strong>Examples:</strong></p>
					<pre>aui-explain="press enter to send the email" </pre>
					<pre>aui-feedback="your email on birthdays was sent" </pre>
					<p>These values will change when the email is sent.</p>
				</div>
				<table class="property-features">
					<caption>Characteristics:</caption>
					<thead>
						<tr>
							<th scope="col">Characteristic</th>
							<th scope="col">Value</th>
						</tr>
					</thead>
					<tbody>
						<tr>
							<th class="property-related-head" scope="row">Related Concepts:</th>
							<td class="property-related"><cite><a href="https://www.w3.org/TR/SVG2/"><abbr title="Scalable Vector Graphics">SVG</abbr></a></cite> [[SVG2]] and <cite><a href="https://www.w3.org/TR/dom/"><abbr title="Document Object Model">DOM</abbr></a></cite> [[DOM4]] active</td>
						</tr>
						<tr>
							<th class="property-applicability-head" scope="row">Used in Roles:</th>
							<td class="property-applicability">All elements of the base markup</td>
						</tr>
						<tr>
							<th class="property-descendants-head" scope="row">Inherits into Roles:</th>
							<td class="property-descendants">Placeholder</td>
						</tr>
						<tr>
							<th class="property-value-head" scope="row">Value:</th>
							<td class="property-value"><a href="#valuetype_string">string</a></td>
						</tr>
					</tbody>
				</table>
			</section>
			<section class="property">
				<h3>moreinfo</h3>
				<div class="property-description">
					<p>@@1-line description</p>
					<p><strong>Supported values: </strong>URI</p>
					<p>Note that there is no default value.</p>
				</div>
				<table class="property-features">
					<caption>Characteristics:</caption>
					<thead>
						<tr>
							<th scope="col">Characteristic</th>
							<th scope="col">Value</th>
						</tr>
					</thead>
					<tbody>
						<tr>
							<th class="property-related-head" scope="row">Related Concepts:</th>
							<td class="property-related"><cite><a href="https://www.w3.org/TR/SVG2/"><abbr title="Scalable Vector Graphics">SVG</abbr></a></cite> [[SVG2]] and <cite><a href="https://www.w3.org/TR/dom/"><abbr title="Document Object Model">DOM</abbr></a></cite> [[DOM4]] active</td>
						</tr>
						<tr>
							<th class="property-applicability-head" scope="row">Used in Roles:</th>
							<td class="property-applicability">All elements of the base markup</td>
						</tr>
						<tr>
							<th class="property-descendants-head" scope="row">Inherits into Roles:</th>
							<td class="property-descendants">Placeholder</td>
						</tr>
						<tr>
							<th class="property-value-head" scope="row">Value:</th>
							<td class="property-value"><a href="#valuetype_uri">URI</a></td>
						</tr>
					</tbody>
				</table>
			</section>
			<section class="property">
				<h3>extrahelp</h3>
				<div class="property-description">
					<p>@@1-line description</p>
					<p><strong>Supported values: </strong>URI</p>
					<p>Note that there is no default value.</p>
				</div>
				<table class="property-features">
					<caption>Characteristics:</caption>
					<thead>
						<tr>
							<th scope="col">Characteristic</th>
							<th scope="col">Value</th>
						</tr>
					</thead>
					<tbody>
						<tr>
							<th class="property-related-head" scope="row">Related Concepts:</th>
							<td class="property-related"><cite><a href="https://www.w3.org/TR/SVG2/"><abbr title="Scalable Vector Graphics">SVG</abbr></a></cite> [[SVG2]] and <cite><a href="https://www.w3.org/TR/dom/"><abbr title="Document Object Model">DOM</abbr></a></cite> [[DOM4]] active</td>
						</tr>
						<tr>
							<th class="property-applicability-head" scope="row">Used in Roles:</th>
							<td class="property-applicability">All elements of the base markup</td>
						</tr>
						<tr>
							<th class="property-descendants-head" scope="row">Inherits into Roles:</th>
							<td class="property-descendants">Placeholder</td>
						</tr>
						<tr>
							<th class="property-value-head" scope="row">Value:</th>
							<td class="property-value"><a href="#valuetype_uri">URI</a></td>
						</tr>
					</tbody>
				</table>
			</section>
			<section class="property">
				<h3>helptype</h3>
				<div class="property-description">
					<p>@@1-line description</p>
					<p><strong>Example:</strong></p>
					<pre>&lt;button type="button" aui-extrahelp=&quot;uri2 uri3&quot; &gt;undo&lt;/button&gt;</pre>
					<p>URI 2 may read: </p>
					<pre>&lt;div id=&quot;uri2&quot;
    aui-helptype=&quot;morehelp&quot;
    aui-hidden=&quot;true&quot;&gt;
  pressing the undo button will erase all your work on this page.
  Use this button with care.
  If you press it by mistake, press control and y at the same time
  and your answers will come back.
&lt;/div&gt;

&lt;a href=&quot;functiongethelp()&quot;
    aui-helptype=&quot;humanhelp&quot;
    aui-hidden=&quot;true&quot;&gt;
  I want a person to help me
&lt;/a&gt;
&lt;div id=&quot;uri3&quot;
    aui-extrahelp=&quot;glossary&quot;
    aui-hidden=&quot;true&quot;&gt;
</pre>
				</div>
				<table class="property-features">
					<caption>Characteristics:</caption>
					<thead>
						<tr>
							<th scope="col">Characteristic</th>
							<th scope="col">Value</th>
						</tr>
					</thead>
					<tbody>
						<tr>
							<th class="property-related-head" scope="row">Related Concepts:</th>
							<td class="property-related"><cite><a href="https://www.w3.org/TR/SVG2/"><abbr title="Scalable Vector Graphics">SVG</abbr></a></cite> [[SVG2]] and <cite><a href="https://www.w3.org/TR/dom/"><abbr title="Document Object Model">DOM</abbr></a></cite> [[DOM4]] active</td>
						</tr>
						<tr>
							<th class="property-applicability-head" scope="row">Used in Roles:</th>
							<td class="property-applicability">All elements of the base markup</td>
						</tr>
						<tr>
							<th class="property-descendants-head" scope="row">Inherits into Roles:</th>
							<td class="property-descendants">Placeholder</td>
						</tr>
						<tr>
							<th class="property-value-head" scope="row">Value:</th>
							<td class="property-value"><a href="#valuetype_token">token</a></td>
						</tr>
					</tbody>
				</table>
				<table class="value-descriptions">
					<caption>Values:</caption>
					<thead>
						<tr>
							<th scope="col">Value</th>
							<th scope="col">Description</th>
						</tr>
					</thead>
					<tbody>
						<tr>
							<th class="value-name" scope="row">automated</th>
							<td class="value-description"></td>
						</tr>
						<tr>
							<th class="value-name" scope="row">dictionary</th>
							<td class="value-description"></td>
						</tr>
						<tr>
							<th class="value-name" scope="row">faqs</th>
							<td class="value-description"></td>
						</tr>
						<tr>
							<th class="value-name" scope="row">glossary</th>
							<td class="value-description"></td>
						</tr>
						<tr>
							<th class="value-name" scope="row">helpform</th>
							<td class="value-description"></td>
						</tr>
						<tr>
							<th class="value-name" scope="row">humanhelp</th>
							<td class="value-description"></td>
						</tr>
						<tr>
							<th class="value-name" scope="row">morehelp</th>
							<td class="value-description"></td>
						</tr>
						<tr>
							<th class="value-name" scope="row">simplified</th>
							<td class="value-description"></td>
						</tr>
						<tr>
							<th class="value-name" scope="row">thesaurus</th>
							<td class="value-description"></td>
						</tr>
						<tr>
							<th class="value-name" scope="row">tooltips</th>
							<td class="value-description"></td>
						</tr>
						<tr>
							<th class="value-name" scope="row">topicsearch</th>
							<td class="value-description"></td>
						</tr>
					</tbody>
				</table>
			</section>
			<section class="property">
				<h3>alternative</h3>
				<div class="property-description">
					<p>Would be used on an alternative content as an alternative to more detailed or difficult to understand content. aui-alternative can be used on a span, div, link or image that servers as alternative content to it's direct parent element.</p>
					<p class="ednote">This data model may be too complex, so this property could undergo substantial changes.</p>
					<p><strong>Supported values:</strong>
					</p>
					<ul>
						<li>On text: easylang, explain, more, vocab500, vocab1000, vocab2000, active, literal, numberfree, smallsentences, chunks</li>
						<li>General: lessoptions. Whitespace, largefont&nbsp;</li>
						<li>Images: symbolic , realistic</li>
						<li>p0, p1, p1, p2, p3 Where p0 are images with true content, p1 is a symbol or illustration that is typically shown with alt=&quot;&quot;, P2 are extra illustration that most people will not mind such as at the start of a paragraph or option. p3 are for disability centric illustrations that can disturb other people and may be mid sentence.&nbsp;</li>
					</ul>
					<p>Note that there is no default value.</p>
					<strong>Example:</strong>
					<pre>&lt;div&gt;
  &lt;span aui-alternative="easylang numberfree vocab1000" class="hidden"&gt;>
    most people prefer simple text
  &lt;/span&gt;
  In studies it was found that only 30% of users prefer long convoluted text
  with&nbsp;obtuse&nbsp;words and lots of numbers,
  with 56% claiming there&nbsp;preferred&nbsp;the simplified text ,
  with the&nbsp;remainder&nbsp;unsure or stated it depends on the context.
&lt;/div&gt;</pre>
				</div>
				<table class="property-features">
					<caption>Characteristics:</caption>
					<thead>
						<tr>
							<th scope="col">Characteristic</th>
							<th scope="col">Value</th>
						</tr>
					</thead>
					<tbody>
						<tr>
							<th class="property-related-head" scope="row">Related Concepts:</th>
							<td class="property-related"><cite><a href="https://www.w3.org/TR/SVG2/"><abbr title="Scalable Vector Graphics">SVG</abbr></a></cite> [[SVG2]] and <cite><a href="https://www.w3.org/TR/dom/"><abbr title="Document Object Model">DOM</abbr></a></cite> [[DOM4]] active</td>
						</tr>
						<tr>
							<th class="property-applicability-head" scope="row">Used in Roles:</th>
							<td class="property-applicability">All elements of the base markup</td>
						</tr>
						<tr>
							<th class="property-descendants-head" scope="row">Inherits into Roles:</th>
							<td class="property-descendants">Placeholder</td>
						</tr>
						<tr>
							<th class="property-value-head" scope="row">Value:</th>
							<td class="property-value"><a href="#valuetype_token_list">token list</a></td>
						</tr>
					</tbody>
				</table>
				<table class="value-descriptions">
					<caption>Values:</caption>
					<thead>
						<tr>
							<th scope="col">Value</th>
							<th scope="col">Description</th>
						</tr>
					</thead>
					<tbody>
						<tr>
							<th class="value-name" scope="row">active</th>
							<td class="value-description"></td>
						</tr>
						<tr>
							<th class="value-name" scope="row">chunks</th>
							<td class="value-description"></td>
						</tr>
						<tr>
							<th class="value-name" scope="row">easylang</th>
							<td class="value-description"></td>
						</tr>
						<tr>
							<th class="value-name" scope="row">explain</th>
							<td class="value-description"></td>
						</tr>
						<tr>
							<th class="value-name" scope="row">largefont</th>
							<td class="value-description"></td>
						</tr>
						<tr>
							<th class="value-name" scope="row">lessoptions</th>
							<td class="value-description"></td>
						</tr>
						<tr>
							<th class="value-name" scope="row">literal</th>
							<td class="value-description"></td>
						</tr>
						<tr>
							<th class="value-name" scope="row">more</th>
							<td class="value-description"></td>
						</tr>
						<tr>
							<th class="value-name" scope="row">numberfree</th>
							<td class="value-description"></td>
						</tr>
						<tr>
							<th class="value-name" scope="row">p0</th>
							<td class="value-description"></td>
						</tr>
						<tr>
							<th class="value-name" scope="row">p1</th>
							<td class="value-description"></td>
						</tr>
						<tr>
							<th class="value-name" scope="row">p1</th>
							<td class="value-description"></td>
						</tr>
						<tr>
							<th class="value-name" scope="row">p2</th>
							<td class="value-description"></td>
						</tr>
						<tr>
							<th class="value-name" scope="row">p3</th>
							<td class="value-description"></td>
						</tr>
						<tr>
							<th class="value-name" scope="row">realistic</th>
							<td class="value-description"></td>
						</tr>
						<tr>
							<th class="value-name" scope="row">smallsentences</th>
							<td class="value-description"></td>
						</tr>
						<tr>
							<th class="value-name" scope="row">symbolic </th>
							<td class="value-description"></td>
						</tr>
						<tr>
							<th class="value-name" scope="row">vocab1000</th>
							<td class="value-description"></td>
						</tr>
						<tr>
							<th class="value-name" scope="row">vocab2000</th>
							<td class="value-description"></td>
						</tr>
						<tr>
							<th class="value-name" scope="row">vocab500</th>
							<td class="value-description"></td>
						</tr>
						<tr>
							<th class="value-name" scope="row">whitespace</th>
							<td class="value-description"></td>
						</tr>
					</tbody>
				</table>
			</section>
			</section>
			<section class="property">
				<h3>log</h3>
				<div class="property-description">
					<p>Contains a label or name for the log that reflects the process or task purpose.</p>
				</div>
				<table class="property-features">
					<caption>Characteristics:</caption>
					<thead>
						<tr>
							<th scope="col">Characteristic</th>
							<th scope="col">Value</th>
						</tr>
					</thead>
					<tbody>
						<tr>
							<th class="property-related-head" scope="row">Related Concepts:</th>
							<td class="property-related"><cite><a href="https://www.w3.org/TR/SVG2/"><abbr title="Scalable Vector Graphics">SVG</abbr></a></cite> [[SVG2]] and <cite><a href="https://www.w3.org/TR/dom/"><abbr title="Document Object Model">DOM</abbr></a></cite> [[DOM4]] active</td>
						</tr>
						<tr>
							<th class="property-applicability-head" scope="row">Used in Roles:</th>
							<td class="property-applicability">All elements of the base markup</td>
						</tr>
						<tr>
							<th class="property-descendants-head" scope="row">Inherits into Roles:</th>
							<td class="property-descendants">Placeholder</td>
						</tr>
						<tr>
							<th class="property-value-head" scope="row">Value:</th>
							<td class="property-value"><a href="#valuetype_string">string</a></td>
						</tr>
					</tbody>
				</table>
			</section>
			<section class="property">
				<h3>step</h3>
				<div class="property-description">
					<p>Contains the number of the step in the process or task.</p>
					<p>This can sometimes be implied via the DOM.</p>
				</div>
				<table class="property-features">
					<caption>Characteristics:</caption>
					<thead>
						<tr>
							<th scope="col">Characteristic</th>
							<th scope="col">Value</th>
						</tr>
					</thead>
					<tbody>
						<tr>
							<th class="property-related-head" scope="row">Related Concepts:</th>
							<td class="property-related"><cite><a href="https://www.w3.org/TR/SVG2/"><abbr title="Scalable Vector Graphics">SVG</abbr></a></cite> [[SVG2]] and <cite><a href="https://www.w3.org/TR/dom/"><abbr title="Document Object Model">DOM</abbr></a></cite> [[DOM4]] active</td>
						</tr>
						<tr>
							<th class="property-applicability-head" scope="row">Used in Roles:</th>
							<td class="property-applicability">All elements of the base markup</td>
						</tr>
						<tr>
							<th class="property-descendants-head" scope="row">Inherits into Roles:</th>
							<td class="property-descendants">Placeholder</td>
						</tr>
						<tr>
							<th class="property-value-head" scope="row">Value:</th>
							<td class="property-value"><a href="#valuetype_integer">integer</a></td>
						</tr>
					</tbody>
				</table>
			</section>
			<section class="property">
				<h3>actiontaken</h3>
				<div class="property-description">
					<p>Contains a summary of key actions taken during a step of a process.</p>
				</div>
				<table class="property-features">
					<caption>Characteristics:</caption>
					<thead>
						<tr>
							<th scope="col">Characteristic</th>
							<th scope="col">Value</th>
						</tr>
					</thead>
					<tbody>
						<tr>
							<th class="property-related-head" scope="row">Related Concepts:</th>
							<td class="property-related"><cite><a href="https://www.w3.org/TR/SVG2/"><abbr title="Scalable Vector Graphics">SVG</abbr></a></cite> [[SVG2]] and <cite><a href="https://www.w3.org/TR/dom/"><abbr title="Document Object Model">DOM</abbr></a></cite> [[DOM4]] active</td>
						</tr>
						<tr>
							<th class="property-applicability-head" scope="row">Used in Roles:</th>
							<td class="property-applicability">All elements of the base markup</td>
						</tr>
						<tr>
							<th class="property-descendants-head" scope="row">Inherits into Roles:</th>
							<td class="property-descendants">Placeholder</td>
						</tr>
						<tr>
							<th class="property-value-head" scope="row">Value:</th>
							<td class="property-value"><a href="#valuetype_string">string</a></td>
						</tr>
					</tbody>
				</table>
			</section>
			<section class="property">
				<h3>steplocation</h3>
				<div class="property-description">
					<p>Contains a link to the location of the step for editing and review. The referenced location should support editing.</p>
					<p>An embedded link inside a step can serve the same function as aui-steplocation.</p>
				</div>
				<table class="property-features">
					<caption>Characteristics:</caption>
					<thead>
						<tr>
							<th scope="col">Characteristic</th>
							<th scope="col">Value</th>
						</tr>
					</thead>
					<tbody>
						<tr>
							<th class="property-related-head" scope="row">Related Concepts:</th>
							<td class="property-related"><cite><a href="https://www.w3.org/TR/SVG2/"><abbr title="Scalable Vector Graphics">SVG</abbr></a></cite> [[SVG2]] and <cite><a href="https://www.w3.org/TR/dom/"><abbr title="Document Object Model">DOM</abbr></a></cite> [[DOM4]] active</td>
						</tr>
						<tr>
							<th class="property-applicability-head" scope="row">Used in Roles:</th>
							<td class="property-applicability">All elements of the base markup</td>
						</tr>
						<tr>
							<th class="property-descendants-head" scope="row">Inherits into Roles:</th>
							<td class="property-descendants">Placeholder</td>
						</tr>
						<tr>
							<th class="property-value-head" scope="row">Value:</th>
							<td class="property-value"><a href="#valuetype_uri">URI</a></td>
						</tr>
					</tbody>
				</table>
			</section>
			<section class="property">
				<h3>status</h3>
				<div class="property-description">
					<p>Describe whether a step in a process is done, pending, current, or not done.</p>
					<p class="ednote">Need a better token for "not done", or is that value actually needed given the presence of prending and current?</p>
					<p class="ednote">Not clear how the true and false values below relate to the done/pending/current/not-done values above.</p>
					<p>When <a href="#actiontaken">actiontaken</a> is not null it implies that <code>aui-status</code> is true. </p>
					<p>When <a href="#actiontaken">actiontaken</a> is null it implies that <code>aui-status</code> is false.</p>
				</div>
				<table class="property-features">
					<caption>Characteristics:</caption>
					<thead>
						<tr>
							<th scope="col">Characteristic</th>
							<th scope="col">Value</th>
						</tr>
					</thead>
					<tbody>
						<tr>
							<th class="property-related-head" scope="row">Related Concepts:</th>
							<td class="property-related"><cite><a href="https://www.w3.org/TR/SVG2/"><abbr title="Scalable Vector Graphics">SVG</abbr></a></cite> [[SVG2]] and <cite><a href="https://www.w3.org/TR/dom/"><abbr title="Document Object Model">DOM</abbr></a></cite> [[DOM4]] active</td>
						</tr>
						<tr>
							<th class="property-applicability-head" scope="row">Used in Roles:</th>
							<td class="property-applicability">All elements of the base markup</td>
						</tr>
						<tr>
							<th class="property-descendants-head" scope="row">Inherits into Roles:</th>
							<td class="property-descendants">Placeholder</td>
						</tr>
						<tr>
							<th class="property-value-head" scope="row">Value:</th>
							<td class="property-value"><a href="#valuetype_token">token</a></td>
						</tr>
					</tbody>
				</table>
				<table class="value-descriptions">
					<caption>Values:</caption>
					<thead>
						<tr>
							<th scope="col">Value</th>
							<th scope="col">Description</th>
						</tr>
					</thead>
					<tbody>
						<tr>
							<th class="value-name" scope="row">done</th>
							<td class="value-description">@@</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">pending</th>
							<td class="value-description">A step has not yet been completed but is not the current step. It is used <a href="#actiontaken">actiontaken</a> when has not been used.</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">current</th>
							<td class="value-description">@@</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">not-done</th>
							<td class="value-description">@@</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">true</th>
							<td class="value-description">@@</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">false</th>
							<td class="value-description">@@</td>
						</tr>
					</tbody>
				</table>
			</section>
			<section class="property">
				<h3>messageimportance</h3>
				<div class="property-description">
					<p>@@1-line description</p>
					<p><strong>Example:</strong></p>
					<pre>&lt;div role=&quot;alert&quot;
    aui-messageimportance=&quot;medium&quot;&gt;
  It is your daughter's birthday tomorrow
&lt;/div&gt;</pre>
				</div>
				<table class="property-features">
					<caption>Characteristics:</caption>
					<thead>
						<tr>
							<th scope="col">Characteristic</th>
							<th scope="col">Value</th>
						</tr>
					</thead>
					<tbody>
						<tr>
							<th class="property-related-head" scope="row">Related Concepts:</th>
							<td class="property-related"><cite><a href="https://www.w3.org/TR/SVG2/"><abbr title="Scalable Vector Graphics">SVG</abbr></a></cite> [[SVG2]] and <cite><a href="https://www.w3.org/TR/dom/"><abbr title="Document Object Model">DOM</abbr></a></cite> [[DOM4]] active</td>
						</tr>
						<tr>
							<th class="property-applicability-head" scope="row">Used in Roles:</th>
							<td class="property-applicability">All elements of the base markup</td>
						</tr>
						<tr>
							<th class="property-descendants-head" scope="row">Inherits into Roles:</th>
							<td class="property-descendants">Placeholder</td>
						</tr>
						<tr>
							<th class="property-value-head" scope="row">Value:</th>
							<td class="property-value"><a href="#valuetype_token">token</a></td>
						</tr>
					</tbody>
				</table>
				<table class="value-descriptions">
					<caption>Values:</caption>
					<thead>
						<tr>
							<th scope="col">Value</th>
							<th scope="col">Description</th>
						</tr>
					</thead>
					<tbody>
						<tr>
							<th class="value-name" scope="row">critical</th>
							<td class="value-description">To be critical a message needs to be both urgent and content that the user is very likely to consider important. For example, a system may send a message that it is going to reboot in one minute to install updates. </td>
						</tr>
						<tr>
							<th class="value-name" scope="row"><strong class="default">medium (default)</strong></th>
							<td class="value-description">Important messages that needs the user's attention at their convenience. For example, a relatively important chat message.</td>
						</tr>
						<tr>
							<th class="value-name" scope="row">low</th>
							<td class="value-description">A message that does not need time sensitive attention. For example, a typical chat message.</td>
						</tr>
					</tbody>
				</table>
			</section>
			<section class="property">
				<h3>messagefrom</h3>
				<div class="property-description">
					<p>@@1-line description</p>
					<p><strong>Supported values: </strong>a string value that identifies the sender of the message. If multiple names are used they can be separated by a coma.</p>
					<p>Note that there is no default value.</p>
					<p><strong>Example:</strong></p>
					<pre>&lt;div role=&quot;alert&quot;
    aui-messageimportance=&quot;low&quot;
    aui-messagefrom=&quot;lisa seeman, lseeman&quot;&gt;
  I posted a new version on GitHub for you to review
&lt;/div&gt;</pre>
				</div>
				<table class="property-features">
					<caption>Characteristics:</caption>
					<thead>
						<tr>
							<th scope="col">Characteristic</th>
							<th scope="col">Value</th>
						</tr>
					</thead>
					<tbody>
						<tr>
							<th class="property-related-head" scope="row">Related Concepts:</th>
							<td class="property-related"><cite><a href="https://www.w3.org/TR/SVG2/"><abbr title="Scalable Vector Graphics">SVG</abbr></a></cite> [[SVG2]] and <cite><a href="https://www.w3.org/TR/dom/"><abbr title="Document Object Model">DOM</abbr></a></cite> [[DOM4]] active</td>
						</tr>
						<tr>
							<th class="property-applicability-head" scope="row">Used in Roles:</th>
							<td class="property-applicability">All elements of the base markup</td>
						</tr>
						<tr>
							<th class="property-descendants-head" scope="row">Inherits into Roles:</th>
							<td class="property-descendants">Placeholder</td>
						</tr>
						<tr>
							<th class="property-value-head" scope="row">Value:</th>
							<td class="property-value"><a href="#valuetype_string">string</a></td>
						</tr>
					</tbody>
				</table>
			</section>
			<section class="property">
				<h3>messagecontext</h3>
				<div class="property-description">
					<p>@@1-line description</p>
					<p><strong>Supported values: </strong><strong> </strong>a string value that identifies the location that makes this message relevant. Typical values are &quot;home&quot; and &quot;work&quot;. If multiple locations are relevant they can be separated by a coma.</p>
					<p>Note that there is no default value.</p>
					<p><strong>Example:</strong></p>
					<pre>&lt;div role=&quot;alert&quot;
   aui-messageimportance=&quot;low&quot;
   aui-messagefrom=&quot;lisa seeman, lseeman&quot;
   aui-messagecontext=&quot;work&quot;&gt;
  I posted a new version on GitHub for you to review
&lt;/div&gt;</pre>
				</div>
				<table class="property-features">
					<caption>Characteristics:</caption>
					<thead>
						<tr>
							<th scope="col">Characteristic</th>
							<th scope="col">Value</th>
						</tr>
					</thead>
					<tbody>
						<tr>
							<th class="property-related-head" scope="row">Related Concepts:</th>
							<td class="property-related"><cite><a href="https://www.w3.org/TR/SVG2/"><abbr title="Scalable Vector Graphics">SVG</abbr></a></cite> [[SVG2]] and <cite><a href="https://www.w3.org/TR/dom/"><abbr title="Document Object Model">DOM</abbr></a></cite> [[DOM4]] active</td>
						</tr>
						<tr>
							<th class="property-applicability-head" scope="row">Used in Roles:</th>
							<td class="property-applicability">All elements of the base markup</td>
						</tr>
						<tr>
							<th class="property-descendants-head" scope="row">Inherits into Roles:</th>
							<td class="property-descendants">Placeholder</td>
						</tr>
						<tr>
							<th class="property-value-head" scope="row">Value:</th>
							<td class="property-value"><a href="#valuetype_string">string</a></td>
						</tr>
					</tbody>
				</table>
			</section>
			<section class="property">
				<h3>messagetime</h3>
				<div class="property-description">
					<p>@@1-line description</p>
					<p><strong>Supported values: </strong><strong> </strong>24 hour date time format. DD.MM.YEAR.HOUR.MM - DD.MM.YEAR.HOUR.MM where the second date is an optional exclusive expiry date.</p>
					<p>Note that there is no default value.</p>
					<p><strong>Example:</strong></p>
					<pre>&lt;div role=&quot;alert&quot;
    aui-messageimportance=&quot;medium&quot;
    aui-messagefrom=&quot;my calender&quot;
    aui-messagecontext=&quot;work&quot;
    aui-messagetime=&quot;10.02.2017.00.00-16.02.2017.00.00&quot;&gt;
  Renew your driving license this week
&lt;/div&gt;</pre>
					<pre>&lt;div role=&quot;alert&quot;
    aui-messageimportance=&quot;critical&quot;
    aui-messagefrom=&quot;my calender&quot;
    aui-messagecontext=&quot;work&quot;
    aui-messagetime=&quot;16.02.2017.00.00&quot;&gt;
  Renew your driving license ASAP
&lt;/div&gt;</pre>
				</div>
				<table class="property-features">
					<caption>Characteristics:</caption>
					<thead>
						<tr>
							<th scope="col">Characteristic</th>
							<th scope="col">Value</th>
						</tr>
					</thead>
					<tbody>
						<tr>
							<th class="property-related-head" scope="row">Related Concepts:</th>
							<td class="property-related"><cite><a href="https://www.w3.org/TR/SVG2/"><abbr title="Scalable Vector Graphics">SVG</abbr></a></cite> [[SVG2]] and <cite><a href="https://www.w3.org/TR/dom/"><abbr title="Document Object Model">DOM</abbr></a></cite> [[DOM4]] active</td>
						</tr>
						<tr>
							<th class="property-applicability-head" scope="row">Used in Roles:</th>
							<td class="property-applicability">All elements of the base markup</td>
						</tr>
						<tr>
							<th class="property-descendants-head" scope="row">Inherits into Roles:</th>
							<td class="property-descendants">Placeholder</td>
						</tr>
						<tr>
							<th class="property-value-head" scope="row">Value:</th>
							<td class="property-value"><a href="#valuetype_string">string</a></td>
						</tr>
					</tbody>
				</table>
			</section>
			<section class="property">
				<h3>distraction</h3>
				<div class="property-description">
					<p>This attribute should be used on , detracting content, so that people who have challenges keeping focus can have distracting content hidden..</p>
					<p><strong>Example: </strong></p>
					<pre>aui-distraction=&quot;moving ad&quot;</pre>
					<p><strong>Supported values: </strong>animations, auto-starting, moving, ad, message, chat , overlay, popup<br /> Auto-changing (logs) third-party, offer ( includes suggestions).</p>
					<p>Note that there is no default value.</p>
					<p>Note that elements with the aui-distraction attribute should also have a label or accessible name.</p>
				</div>
				<table class="property-features">
					<caption>Characteristics:</caption>
					<thead>
						<tr>
							<th scope="col">Characteristic</th>
							<th scope="col">Value</th>
						</tr>
					</thead>
					<tbody>
						<tr>
							<th class="property-related-head" scope="row">Related Concepts:</th>
							<td class="property-related"><cite><a href="https://www.w3.org/TR/SVG2/"><abbr title="Scalable Vector Graphics">SVG</abbr></a></cite> [[SVG2]] and <cite><a href="https://www.w3.org/TR/dom/"><abbr title="Document Object Model">DOM</abbr></a></cite> [[DOM4]] active</td>
						</tr>
						<tr>
							<th class="property-applicability-head" scope="row">Used in Roles:</th>
							<td class="property-applicability">All elements of the base markup</td>
						</tr>
						<tr>
							<th class="property-descendants-head" scope="row">Inherits into Roles:</th>
							<td class="property-descendants">Placeholder</td>
						</tr>
						<tr>
							<th class="property-value-head" scope="row">Value:</th>
							<td class="property-value"><a href="#valuetype_token_list">token list</a></td>
						</tr>
					</tbody>
				</table>
				<table class="value-descriptions">
					<caption>Values:</caption>
					<thead>
						<tr>
							<th scope="col">Value</th>
							<th scope="col">Description</th>
						</tr>
					</thead>
					<tbody>
						<tr>
							<th class="value-name" scope="row">ad</th>
							<td class="value-description"></td>
						</tr>
						<tr>
							<th class="value-name" scope="row">animations</th>
							<td class="value-description"></td>
						</tr>
						<tr>
							<th class="value-name" scope="row">auto-changing</th>
							<td class="value-description"></td>
						</tr>
						<tr>
							<th class="value-name" scope="row">auto-starting</th>
							<td class="value-description"></td>
						</tr>
						<tr>
							<th class="value-name" scope="row">chat</th>
							<td class="value-description"></td>
						</tr>
						<tr>
							<th class="value-name" scope="row">message</th>
							<td class="value-description"></td>
						</tr>
						<tr>
							<th class="value-name" scope="row">moving</th>
							<td class="value-description"></td>
						</tr>
						<tr>
							<th class="value-name" scope="row">offer</th>
							<td class="value-description"></td>
						</tr>
						<tr>
							<th class="value-name" scope="row">overlay</th>
							<td class="value-description"></td>
						</tr>
						<tr>
							<th class="value-name" scope="row">popup</th>
							<td class="value-description"></td>
						</tr>
						<tr>
							<th class="value-name" scope="row">third-party</th>
							<td class="value-description"></td>
						</tr>
					</tbody>
				</table>
			</section>
		</section>

		<section>
			<h2>User Settings</h2>
			<p class="ednote">This section is not yet developed. A <a href="user-settings">draft of user settings</a> is available separately.</p>
		</section>

		<section class="appendix">
			<h2>Vocabulary Implementations</h2>
			<section>
				<h3>RDFa</h3>
				<p>The context based properties should be convertible to RDFa. (see <a href="https://www.w3.org/TR/xhtml-rdfa-primer/">RDFa Primer</a>) and the task force should create this mapping.</p>
				<p>Note that a lot of this can be done using RDFa. However it is easy to change the meaning with RDFa and a very basic parser will misinterpret the result. The coga work needs to be usable by as many authors as possible, and not only those who can implement RDF logic.</p>
				<p>Further , personalization setting need to be limited, and RDF can give an unlimited number of potential options which will make the system unusable. (This is unless we create restrictions and controls on an ontology uses - such as mapping to know ontologies.)</p>
				<p>For example, in the code below the property homepage does not refer to the home page of the site but of the person being references. Beyond declaring the type of data we are dealing with, each typeof creates a new blank node with its own distinct properties. </p>
				<pre>
&lt;div vocab="http://xmlns.com/foaf/0.1/"&gt;
&lt;ul&gt;
   &lt;li typeof="Person"&gt;
      &lt;a property="homepage" href="http://example.com/bob/"&gt;Bob&lt;/a&gt;
   &lt;/li&gt;
   &lt;li typeof="Person"&gt;
      &lt;a property="homepage" href="http://example.com/eve/"&gt;Eve&lt;/a&gt;
   &lt;/li&gt;
   &lt;li typeof="Person"&gt;
      &lt;a property="homepage" href="http://example.com/manu/"&gt;Manu&lt;/a&gt;
   &lt;/li&gt;
&lt;/ul&gt;
				</pre>
				<p>We may recommend adding RDFA that describe the role of the item (see <a href="https://www.w3.org/TR/xhtml-rdfa-primer/">RDFa Primer</a>):</p>
				<pre>
&lt;div resource="/alice/posts/jos_barbecue"&gt;
	&lt;h2 property="title"&gt;Jo's Barbecue&lt;/h2&gt;
	&lt;p&gt;Date: &lt;span property="created"&gt;2011-09-14&lt;/span&gt;&lt;/p&gt;
	&lt;h3 property="creator"&gt;Eve&lt;/h3&gt;
	...
&lt;/div&gt;
			</pre>
			</section>
			<section>
				<h3>WAI-ARIA</h3>
				<p>Properties in this case can be represented as WAI-ARIA properties by adding the prefix "aria-" to the attribute name, and the property value as the attribute value.</p>
				<p class="ednote">The prefix above is not yet accepted by the ARIA Working Group.</p>
				<section>
					<h2>Additional WAI-ARIA roles</h2>
					<p><strong>Requirement: </strong> We may want to add roles for sections a page such as: contact us - for a contact us form&nbsp; </p>
					<p><strong>User experience: </strong>symbols and colors could be used consistently across different content.</p>
					<p>Nav maps can be automatically generated for people learn via key-points or examples.</p>
					<p>Further these sections could be hidden in the normal rendering of a page or rendered the top of page depending on user preferences. The location of these sections can also be changed, based on the user preference, enabling the user to find them easily.</p>
					<p>Values:</p>
					<ul>
						<li>summary</li>
						<li>keypoints</li>
						<li>example</li>
						<li>note</li>
						<li>warning</li>
						<li>step</li>
						<li>external - for external content, such as sponsored or advertising</li>
						<li>offers - for special offers that are complementary to the main content or task</li>
						<li>advertisement - advertisement or sponsored content</li>
						<li>contact us</li>
						<li>about us</li>
					</ul>
				</section>
			</section>
			<section>
				<h3>HTML Microdata</h3>
				<p>Properties in this vocabulary can be used in <a href="https://www.w3.org/TR/microdata/">HTML Microdata</a> [[microdata]]. The property name is uses as the item name, the property value as the item value. Authors SHOULD use the itemtype property to express to the <a href="#propcharacteristic_value">value type</a> defined in this specification.</p>
			</section>
		</section>

		<!--

		<section class="appendix" id="changelog">
			<h2>Change Log</h2>

			<section>
				<h2>Substantive changes since the <a href="@@">last public working draft</a></h2>
				<ul>
					<li>@@</li>
					<!- EdNote: After each WD publish, move contents of this list into the next one below. ->
				</ul>
			</section>

			<section>
				<h2>Other substantive changes since the <a href="@@">First Public Working Draft</a></h2>
				<ul>
					<li>@@</li>
					<!- EdNote: After each WD publish, move previous list into this one. ->
				</ul>
			</section>
		</section>

		-->
		<div data-include="common/acknowledgements.html" data-oninclude="fixIncludes" data-include-replace="true">Acknowledgements placeholder</div>
	</body>
</html>