Accessibility/WebAccessibilityAPI: Difference between revisions

Accessibility/WebAccessibilityAPI (view source)

142 bytes added , 8 May 2015

Confirmed users

1,396

edits

@@ Line 1,944: / Line 1,944: @@
 ===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>
-var source = {
+var source1 = {
    role: "listitem"
 };
-</pre>
-<pre>
+var source2 = {
-var source = {
    role: "listitem",
-   states: [ "selectable" ]
+   states: [ "selectable", "focusable" ]
 };
 </pre>
-The implied semantics is described by [[#SemanticsProviders|semantics provides]].
+Implied semantics is described by [[#SemanticsProviders|taxonomies]].
 ===Conflicts===