aria-required — semantic requiredness
`aria-required` communicates that a supported control requires a value but adds no native form constraint.
CKTIS / HTML
Programming syntax, operators and concepts. Find an explanation, explore an example and return to learning.
`aria-required` communicates that a supported control requires a value but adds no native form constraint.
`aria-selected` describes selection of an item such as a tab, option, or interactive cell according to its role.
`as` on a preload link identifies how a resource will be used, not its filename or MIME type.
`async` allows fetching alongside document processing and running a script when ready without guaranteeing execution order.
Guide a text input method without mistaking a keyboard hint for validation.
Describe field purpose and distinguish shipping, billing and separate autofill sections.
Allow or forbid typing corrections without turning a field into a text-cleaning function.
The `autofocus` attribute asks the browser to focus an element when it becomes available in a document, dialog, or popover; it is neither a guarantee nor a scrolling command.
Request a start while preserving user control and accounting for playback policy.
Distinguish render blocking from HTML parsing and script execution order.
The capture attribute requests media capture through a file input and hints at the preferred camera direction.
Make the declared encoding agree with the actual bytes and the HTTP response.
Understand checkbox and radio defaults, user changes and form reset.
Record a source URL and add a visible link separately when readers need it.
The `class` attribute assigns tokens used by selectors, scripts, and tooling; a class name alone supplies neither semantics nor an accessibility state.
Separate automatic dismissal from explicit application controls.
A narrowly scoped link attribute, not the CSS text-color property.
Use wide-gamut color progressively and distinguish a standard rule from browser support.
Control the default display width without setting a text-length limit.
Reason about table-grid positions instead of counting only DOM cells.
Invoke native dialog or popover actions, or dispatch a custom command.
Connect one button to a specific element rather than a CSS selector or every matching node.
Interpret a metadata value together with its name or directive.
The `contenteditable` attribute enables or disables editing of an element’s contents, but it does not create a form control or provide safe persistence by itself.