HTML| html.spec.whatwg.org
Notes on ARIA Use in HTML| w3c.github.io
HTML| html.spec.whatwg.org
The content previously found at this location has been moved to the following pages:| w3c.github.io
Living Standard — Last Updated 22 August 2025| html.spec.whatwg.org
Categories:Flow content.Phrasing content.If the type attribute is not in the Hidden state: Interactive content.If the type attribute is not in the Hidden state: Listed, labelable, submittable, resettable, and autocapitalize-and-autocorrect inheriting form-associated element.If the type attribute is in the Hidden state: Listed, submittable, resettable, and autocapitalize-and-autocorrect inheriting form-associated element.If the type attribute is not in the Hidden state: Palpable content.Contex...| html.spec.whatwg.org
ARIA semantics that extend and diverge from HTML| w3c.github.io
Accessibility of web content requires semantic information about widgets, structures, and behaviors, in order to allow assistive technologies to convey appropriate information to persons with disabilities. This specification provides an ontology of roles, states, and properties that define accessible user interface elements and can be used to improve the accessibility and interoperability of web content and applications. These semantics are designed to allow an author to properly convey user ...| www.w3.org
HTML Accessibility API Mappings (HTML-AAM) defines how user agents map HTML [HTML] elements and attributes to platform accessibility application programming interfaces (APIs). It leverages and extends the Core Accessibility API Mappings 1.2 and the Accessible Name and Description Computation 1.2 for use with the HTML host language. Documenting these mappings promotes interoperable exposure of roles, states, properties, and events implemented by accessibility APIs and helps to ensure that this...| w3c.github.io