Note: An element with a subclass role of the 'required owned element' does not fulfill this requirement. See required context role for requirements about the context where elements of a given role will be contained. While processing of a role may be incomplete without elements of given roles present as descendants, elements with roles in this list do not always have to be found within elements of the given role. Note: A role that has 'required owned elements' does not imply the reverse relationship. For example, until a page is fully initialized and complete, an author could mark the document element as busy. When a widget is missing required owned elements due to script execution or loading, authors MUST mark a containing element with aria-busy equal to true. There may be times that required owned elements are missing, for example, while editing or while loading a data set. The menu role does not require one instance of each.
For example, a menu should have at least one instance of a menuitem, menuitemcheckbox, or menuitemradio. This specification does not require an instance of each of the listed owned roles. When multiple roles are specified as required owned elements for a role, at least one instance of one required owned element is expected.
For example, an element with the role list will own at least one element with the role group or listitem. # RDF Property role:mustContain Values Any valid RDF object reference, such as a URI or an RDF ID reference.Īny element that will be owned by the element with this role.
#Dom writers to watch update#
In order to reflect the content in the DOM, user agents SHOULD map the role attribute to the appropriate value in the implemented accessibility API, and user agents SHOULD update the mapping when the role attribute changes. Typically, platform accessibility APIs do not provide a vehicle to notify assistive technologies of a role value change, and consequently, assistive technologies may not update their cache with the new role attribute value. Authors wishing to change a role MUST do so by deleting the associated element and its children and replacing it with a new element with the appropriate role. Roles are element types and authors MUST NOT change role values over time or with user actions. The RDF/OWL taxonomy may be used as a vehicle to extend WAI-ARIA in the future or by tool manufacturers to validate states and properties applicable to roles per this specification. The RDF/OWL representation used to model the taxonomy shall be considered informative. The roles, their characteristics, the states and properties they support, and specification of how they may be used in markup, shall be considered normative. A formal RDF/ OWL representation of all the information presented here is available in Schemata Appendix. This section defines the WAI-ARIA role taxonomy and describes the characteristics and properties of all roles.
0 kommentar(er)
