Accessibility/WebAccessibilityAPI - Revision history

Surkov.alexander: /* Questions/concerns */

2015-05-08T15:06:18Z

Questions/concerns

← Older revision		Revision as of 15:06, 8 May 2015
Line 481:		Line 481:

	Here's the image of InideUI action/interaction concept.		Here's the image of InideUI action/interaction concept.
			<div style="height: 254px; overflow: hidden;">
	http://www.w3.org/WAI/intro/iui-scroll.png		http://www.w3.org/WAI/intro/iui-scroll.png
			</div>

	Alternatively we could introduce relations between actions like "triggers" and "triggeredby".		Alternatively we could introduce relations between actions like "triggers" and "triggeredby".


	* What about highlevel actions (uberactions), for example, "press" buttons means "send something somewhere". This may be covered by label. Another example, selected listitem on the left changes a view on the right, "select" actions has meaning of "change view". Or checkbox that enables/disables related controls, "check/uncheck" action means "enable/disable controls". These examples correlates to controlledby/controllerfor relations, but the relations doesn't reveal type of control.		* What about highlevel actions (uberactions), for example, "press" buttons means "send something somewhere". This may be covered by label. Another example, selected listitem on the left changes a view on the right, "select" actions has meaning of "change view". Or checkbox that enables/disables related controls, "check/uncheck" action means "enable/disable controls". These examples correlates to controlledby/controllerfor relations, but the relations doesn't reveal type of control.

Surkov.alexander: /* Interactions */

2015-05-08T14:54:33Z

Interactions

← Older revision		Revision as of 14:54, 8 May 2015
Line 476:		Line 476:


	Questions/concerns		====Questions/concerns====

	* Interactions should be extended to allow to specify a control that triggers the action. The concept is described by InidieUI: you can use mouse, touchscreen, keyboard, voice control or a control element to invoke the action. Maybe Interactions should be renamed to Triggers to share terms with IndieUI.		* Interactions should be extended to allow to specify a control that triggers the action. The concept is described by InidieUI: you can use mouse, touchscreen, keyboard, voice control or a control element to invoke the action. Maybe Interactions should be renamed to Triggers to share terms with IndieUI.

	Here's the image of InideUI action/interaction concept.		Here's the image of InideUI action/interaction concept.
	http://www.w3.org/WAI/intro/iui-scroll.png		http://www.w3.org/WAI/intro/iui-scroll.png

			Alternatively we could introduce relations between actions like "triggers" and "triggeredby".

			* What about highlevel actions (uberactions), for example, "press" buttons means "send something somewhere". This may be covered by label. Another example, selected listitem on the left changes a view on the right, "select" actions has meaning of "change view". Or checkbox that enables/disables related controls, "check/uncheck" action means "enable/disable controls". These examples correlates to controlledby/controllerfor relations, but the relations doesn't reveal type of control.

	===Parent-child relations===		===Parent-child relations===

Surkov.alexander: /* Interactions */

2015-05-08T13:08:14Z

Interactions

← Older revision		Revision as of 13:08, 8 May 2015
Line 474:		Line 474:
	});		});
	</pre>		</pre>


			Questions/concerns
			* Interactions should be extended to allow to specify a control that triggers the action. The concept is described by InidieUI: you can use mouse, touchscreen, keyboard, voice control or a control element to invoke the action. Maybe Interactions should be renamed to Triggers to share terms with IndieUI.

			Here's the image of InideUI action/interaction concept.
			http://www.w3.org/WAI/intro/iui-scroll.png

	===Parent-child relations===		===Parent-child relations===

Surkov.alexander: /* Sniffing */

2015-05-08T12:46:16Z

Sniffing

← Older revision		Revision as of 12:46, 8 May 2015
Line 1,963:		Line 1,963:

	[to be done conflicts between native semantics, ARIA and this API, I tend to think that the author should be able to replace/remove native semantics if needed. This can ruin the web page but it gives the absolute control over the page content. A dangerous but quite powerful tool like atomic energy. ]		[to be done conflicts between native semantics, ARIA and this API, I tend to think that the author should be able to replace/remove native semantics if needed. This can ruin the web page but it gives the absolute control over the page content. A dangerous but quite powerful tool like atomic energy. ]


	===Sniffing===		===Sniffing===

	In order to make optimization the content provider has to know whether accessibility consumer is active. The provider can add a callback for <code>deploy</code> and <code>conceal</code> event types which will be triggered when consumer appears/gets inactive.		In order to make an optimization, the content provider has to know whether an accessibility consumer (like screen reader) is active. The provider can add a callback for <code>deploy</code> and <code>conceal</code> event types which will be triggered when consumer appears/gets inactive.

	<pre>		<pre>

Surkov.alexander: /* Conflicts */

2015-05-08T12:44:51Z

Conflicts

← Older revision		Revision as of 12:44, 8 May 2015
Line 1,958:		Line 1,958:

	Implied semantics is described by [[#SemanticsProviders\|taxonomies]].		Implied semantics is described by [[#SemanticsProviders\|taxonomies]].


	===Conflicts===		===Conflicts===

Surkov.alexander: /* Conflicts */

2015-05-08T12:44:31Z

Conflicts

← Older revision		Revision as of 12:44, 8 May 2015
Line 1,961:		Line 1,961:
	===Conflicts===		===Conflicts===

	[to be done conflicts between native semantics, ARIA and this API]		[to be done conflicts between native semantics, ARIA and this API, I tend to think that the author should be able to replace/remove native semantics if needed. This can ruin the web page but it gives the absolute control over the page content. A dangerous but quite powerful tool like atomic energy. ]

	===Sniffing===		===Sniffing===

Surkov.alexander: /* Implied semantics */

2015-05-08T12:40:03Z

Implied semantics

← Older revision		Revision as of 12:40, 8 May 2015
Line 1,944:		Line 1,944:
	===Implied semantics===		===Implied semantics===

	The author ~~has~~ to be less verbose as possible. If a role ~~usually~~ implies number of ~~sets~~ or ~~attributes~~ then they are ~~supposed to set so~~ the ~~authur doesn~~'t ~~need to~~ list them. For example if <code>listitem</code> is selectable then ~~you don~~'t have to point <code>selectable</code> ~~state on it~~, in other words, these code snippets are equivalent:		The idea is to help the author to keep the code less verbose as possible. If role implies a number of preset attributes or states then they are present on the accessible element by default, i.e. if the author didn't list them. For example, if <code>listitem</code> role is selectable and focusable by default then the author doesn't have to point <code>selectable</code> and <code>focusable</code> states when he describes a listitem source, in other words, these code snippets are equivalent:

	<pre>		<pre>
	var ~~source~~ = {		var source1 = {
	role: "listitem"		role: "listitem"
	};		};
	~~</pre>~~

	~~<pre>~~		var source2 = {
	var ~~source~~ = {
	role: "listitem",		role: "listitem",
	states: [ "selectable" ]		states: [ "selectable", "focusable" ]
	};		};
	</pre>		</pre>

	~~The implied~~ semantics is described by [[#SemanticsProviders\|~~semantics provides~~]].		Implied semantics is described by [[#SemanticsProviders\|taxonomies]].

	===Conflicts===		===Conflicts===

Surkov.alexander: /* Text */

2015-05-07T19:49:11Z

Text

← Older revision		Revision as of 19:49, 7 May 2015
Line 1,049:		Line 1,049:

	<code>		<code>
	AccessibleDocument .''text''		AccessibleDocument .''text(AccessiblePos)''
	::Returns the text enclosed between this and given accessible positions.		::Returns the text enclosed between this and given accessible positions.

	AccessibleDocument .''text''		AccessibleDocument .''text(CriteriaLiteral)''
	::Returns the text at the position complying the given criteria. See [[#Criteria\|criteria]] for options.		::Returns the text at the position complying the given criteria. See [[#Criteria\|criteria]] for options.
	</code>		</code>
Line 1,103:		Line 1,103:
	p.textAttributes.get("font-weight") == 700; // true		p.textAttributes.get("font-weight") == 700; // true
	</pre>		</pre>


	==Caret and selection==		==Caret and selection==

Surkov.alexander: /* States */

2015-05-07T19:37:22Z

States

← Older revision		Revision as of 19:37, 7 May 2015
Line 2,326:		Line 2,326:
	},		},
	focused: { },		focused: { },

	singleline: {		singleline: {
	exlcusives: [ "multiline" ]		exlcusives: [ "multiline" ]
Line 2,332:		Line 2,333:
	exlcusives: [ "singleline" ]		exlcusives: [ "singleline" ]
	},		},

	readonly: { },		readonly: { },
	editable: { },		editable: { },
	required: { }		required: { },

			checked: {
			exlusives: [ "mixed" ]
			},
			mixed: {
			exlusives: [ "checked" ]
			}
	};		};
	</pre>		</pre>

Surkov.alexander: /* States */

2015-05-07T19:35:47Z

States

← Older revision		Revision as of 19:35, 7 May 2015
Line 2,301:		Line 2,301:
	DOMString description;		DOMString description;
	sequence<DOMString> dependents;		sequence<DOMString> dependents;
	DOMString ~~opposite~~;		DOMString exclusives;
	}		}
	</pre>		</pre>
Line 2,313:		Line 2,313:
	::List of all dependent states. For example, "focused" state always accompanied by "focusable" state.		::List of all dependent states. For example, "focused" state always accompanied by "focusable" state.

	StateTaxon ..''~~opposite~~''		StateTaxon ..''exclusives''
	::~~An opposite state~~ if ~~any. Opposite state are mutually exclusive~~. For example, if "vertical" state is applied then "horizontal" is not and vice versa.		::Mutually exclusive states if applicable. For example, if "vertical" state is applied then "horizontal" is not and vice versa.
	</code>		</code>

Line 2,327:		Line 2,327:
	focused: { },		focused: { },
	singleline: {		singleline: {
	~~opposite~~: "multiline"		exlcusives: [ "multiline" ]
	},		},
	multiline: {		multiline: {
	~~opposite~~: "singleline"		exlcusives: [ "singleline" ]
	},		},
	readonly: { },		readonly: { },
Line 2,337:		Line 2,337:
	};		};
	</pre>		</pre>


	====Attributes====		====Attributes====