alt — text that replaces an image
`alt` conveys an image’s meaning or the purpose of an image link; empty text for decoration differs from a missing attribute.
CKTIS / Knowledge base
Programming syntax, operators and concepts. Find an explanation, explore an example and return to learning.
`alt` conveys an image’s meaning or the purpose of an image link; empty text for decoration differs from a missing attribute.
`aria-atomic` specifies whether a live-region update should be presented as a whole or only as the changed part.
`aria-busy="true"` tells assistive technologies that a region’s changes are incomplete and may be presented later.
`aria-checked` describes the checked state of a suitable control role; it does not implement checkbox behavior.
`aria-controls` connects a control with elements whose contents or visibility it manages.
`aria-current` marks the current page, step, or another current item within a related set.
`aria-describedby` connects an element to an explanation that supplements its accessible name.
aria-disabled tells assistive technologies that an element is perceivable but unavailable for operation. The attribute alone neither prevents actions nor removes the element from the focus order; the author must implement that behavior.
`aria-expanded` reports whether controlled content is expanded and must match the real interface state.
`aria-hidden` can remove redundant contents from the accessibility tree without hiding them on screen.
`aria-invalid` communicates a control’s error state but does not perform validation or prevent form submission.
`aria-label` gives an accessible name to an element whose role permits author-provided naming.
`aria-labelledby` constructs an accessible name from the text of elements referenced by identifiers.
`aria-live` indicates how urgently assistive technology should present changes to a region.
The aria-modal attribute tells assistive technologies whether a displayed element is modal, meaning interaction is restricted to its contents. It does not block the background or manage focus by itself: the declaration must match the interface's actual behavior.
`aria-pressed` distinguishes a toggle button from an ordinary button that performs a one-off command.
`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.