Differences between revisions 13 and 14
| Deletions are marked like this. | Additions are marked like this. |
| Line 19: | Line 19: |
| An {{{access}}} element must have either a {{{targetrole}}} or a {{{targetid}}} attribute specified. If neither a [http://www.w3.org/MarkUp/2008/WD-xhtml-access-20080418/#sec_3.1.3. targetrole] nor a [http://www.w3.org/MarkUp/2008/WD-xhtml-access-20080418/#sec_3.1.4. targetid] attribute are specified, the user agent '''''MUST NOT''''' define a mapping nor deliver any events. | An {{{access}}} element must have either a {{{targetrole}}} or a {{{targetid}}} attribute specified. If neither a {{{targetrole}}} nor a {{{targetid}}} attribute are specified, the user agent '''''MUST NOT''''' define a mapping nor deliver any events. |
XHTML Access Module's ACCESS Element
Current Wording
3.1. The access element
The access element assigns an accessibility mapping to elements within a document. Actuating the mapping results in the element gaining focus or, optionally, in some other event being delivered.
source: Section 3.1. of the 14 April 2008 draft of the XHTML Access Module
Proposed Re-Wording
3.1. The access element
The access element assigns an accessibility mapping to elements within a document. Actuating the mapping results in the element gaining focus (either the document focus or an inspection focus, as determined by the user agent), and, if set by the author and permitted by the user's settings, in one or more other events being activated.
An access element must have either a targetrole or a targetid attribute specified. If neither a targetrole nor a targetid attribute are specified, the user agent MUST NOT define a mapping nor deliver any events.
Continue UAWG Review: Access Element | Activate Attribute | Key Mapping/Binding