Appearance
Data Display
Avatars, badges, chips, dots, timelines, lists, progress and the small components that carry most of an admin panel's information.
The live reference for everything on this page is html/pages/ui/data-display.html, which renders each component beside its own source.
Avatar
Initials by default, not an image. No second request, no broken-image state and no layout shift when the request is slow. An <img> dropped inside still works — the box clips it.
html
<span class="av-avatar" aria-hidden="true">SK</span>
<span class="av-avatar av-avatar--sm">
<img src="avatars/01.jpg" alt="" width="28" height="28">
</span>| Class | Size | Typical use |
|---|---|---|
.av-avatar--sm | 28px | Table rows, activity feeds, avatar groups |
.av-avatar | 36px | The default: topbar, lists, cards |
.av-avatar--lg | 48px | A record's header |
.av-avatar--xl | 88px | A profile page. Carries a double ring and a bottom margin. |
The initials are aria-hidden on every shipped page, because the name is always beside them. An avatar that announces "SK" before the words "Sarah Kim" is noise.
alt on avatars
| Context | alt |
|---|---|
| Name is adjacent in the DOM | alt="" — otherwise the name is announced twice |
| Avatar is the only identifier | alt="Sarah Kim" |
| Avatar is a link to a profile | alt="", and put the name in the link's text |
Presence
html
<span class="av-avatar av-avatar--status" data-av-status="away" aria-hidden="true">JW</span>data-av-status takes away, busy or offline; omitting it leaves the dot in the online colour. The dot is a pseudo-element, so there is nothing to write inside the avatar and nothing to keep in sync.
It is decorative on purpose. The state has to exist as text somewhere the reader can reach, because a colour is not an accessible name — on the contact list that is the row's own status column, in chat it is the conversation header.
overflow: visibleon--statusis load-bearing, and it was missing. The dot hangs a pixel outside the disc on each axis, and theoverflow: hiddenthat rounds an<img>was clipping it into a wedge — everywhere an avatar carried one. Turning containment off for this modifier means the image has to round itself, which is one line and what a photo should have been doing anyway.
Group
html
<span class="av-avatar-group" role="img"
aria-label="Sarah Kim, James Wong, Maya Byrne and 3 others">
<span class="av-avatar av-avatar--sm" aria-hidden="true">SK</span>
<span class="av-avatar av-avatar--sm" aria-hidden="true">JW</span>
<span class="av-avatar av-avatar--sm" aria-hidden="true">MB</span>
<span class="av-avatar av-avatar--sm av-avatar-group__more" aria-hidden="true">+3</span>
</span>The group carries the accessible name and the discs inside it are decorative — one image with one label, rather than four unlabelled ones. Each avatar is punched out of the one before it with a ring in the surface colour, so the stack reads as separate discs rather than a smear.
Not built
There is no --xs, --md or --2xl (the four sizes above are the set), no --square, no --initials colour-from-name modifier and no avatarHue() utility. There is no .av-avatar__status child element either — presence is the data-av-status attribute above.
Avatar upload and crop
[data-av-avatar-upload] turns a <dialog> into a photo chooser and a cropper. There is no vendor behind it: a cropping library is 40–60 KB to do arithmetic the browser already provides, and this is the same trade the calendar, the carousel, the virtual list and every date picker in this template already take.
html
<button class="av-btn av-btn--outline" type="button"
data-av-modal-open="#avatarUpload">Upload photo</button>
<span class="av-avatar av-avatar--xl" id="settingsAvatar" aria-hidden="true">FP</span>
<dialog class="av-dialog av-dialog--lg" id="avatarUpload"
data-av-avatar-upload
data-av-avatar-target="#settingsAvatar"
data-av-avatar-max-size="2MB"
data-av-avatar-min="200"
data-av-avatar-output="512"
aria-labelledby="avatarUploadTitle">
<!-- see html/_partials/avatar-upload-dialog.html for the full body -->
</dialog>| Attribute | Default | What it decides |
|---|---|---|
data-av-avatar-target | — | The selector the finished photo is written into. Named here, not in the module, so one dialog serves any avatar on any page. |
data-av-avatar-max-size | 2MB | Refused above this, by byte count. |
data-av-avatar-min | 200 | Refused below this, by dimension. A 40×40 PNG is a few hundred bytes and passes every size check while being useless as an avatar. |
data-av-avatar-output | 512 | The edge of the square that is saved, re-encoded as WebP at 0.9. |
Six things about it are decisions rather than styling, and each is a way a cropper is wrong while looking right.
The preview and the saved file come out of one draw call. paint(context, size) serves the stage, both live previews and the export. A cropper with a separate export path is two implementations of one transform, and the one nobody watches is the one that ships the avatar with the head cut off. npm run test:avatar frames one half of a two-tone image and reads the pixel back off the saved blob for exactly this reason.
The crop is a circle, because the avatar is. Cropping to a square and letting CSS round it later shows the reader corners they are about to lose.
The image can never leave the frame. Scale has a floor that covers the circle and the offsets are clamped whenever either changes, so there is no way to produce an avatar that is half background.
EXIF orientation is applied on the way in. A phone photograph carries its rotation as metadata, and drawImage from a decoded bitmap ignores it unless asked — so a portrait selfie arrives on its side and the person crops a sideways face without being told why. createImageBitmap(file, { imageOrientation: 'from-image' }) is the whole fix.
The arrow keys move the photo and zoom is a real input[type=range], so the control is settable and announced. A drag-only cropper cannot be operated without a pointer at all, and nothing on screen reveals that.
Save is aria-disabled, never disabled. The property drops the control out of the tab order, so a keyboard reader tabs straight past the one button the dialog exists for and is told nothing about why. The capture-phase guard in initActions is what makes the attribute mean something.
The live examples are on Settings and the account profile page. npm run test:avatar is the gate.
Badge
A badge carries its meaning in its text. The colour is reinforcement, never the message.
html
<span class="av-badge av-badge--success-soft">Paid</span>
<span class="av-badge av-badge--warning-soft">Pending</span>
<span class="av-badge av-badge--danger-soft">Refunded</span>
<span class="av-badge av-badge--info-soft">Shipped</span>
<span class="av-badge av-badge--primary-soft">New</span>
<span class="av-badge av-badge--neutral-soft">Draft</span>
<span class="av-badge av-badge--success-soft">
<svg class="av-icon" aria-hidden="true" viewBox="0 0 24 24"><path d="M4 12.5l5 5 11-11"/></svg>
Verified
</span>Two families, both generated from the one role list in src/scss/abstracts/_variants.scss so a new role reaches every component that has one rather than four of the five:
| Family | Roles | Reads as |
|---|---|---|
--<role>-soft | primary, success, warning, danger, info, neutral | A label |
--<role> (solid) | primary, success, warning, danger, info | A claim |
Neutral is deliberately absent from the solid set. There is no --av-text-on-neutral token, because a solid neutral badge is a grey slab that says nothing louder than the soft one — the roles that ship solid are the five with something to shout. A catalogue needs both weights: when every pill on a card carries the same emphasis the eye has nothing to sort by, and a 25% discount arrives as the equal of a category tag, which is the one thing the discount is not.
The icon inside a badge is sized by the badge (.av-badge .av-icon { inline-size: 12px }), never inline, so a badge built by the runtime matches one written by hand.
A status badge must carry an icon and text, or text alone. Colour alone fails WCAG 1.4.1. "Paid" in green and "Refunded" in red are indistinguishable to about 8% of men.
Counts on a control
A count on an icon button is .av-notif__badge, inside a .av-notif wrapper, and the number goes into the control's accessible name rather than being left for a reader to find:
html
<div class="av-notif">
<button class="av-btn av-btn--ghost av-btn--icon" type="button"
data-av-drawer-open="#avNotifDrawer"
aria-haspopup="dialog" aria-label="Notifications, 3 unread">
<svg class="av-icon" aria-hidden="true" viewBox="0 0 24 24">
<path d="M6 17v-6a6 6 0 0 1 12 0v6l1.5 2.2H4.5L6 17z"/><path d="M10 21a2 2 0 0 0 4 0"/>
</svg>
<span class="av-notif__badge av-notif__badge--pulse" aria-hidden="true">3</span>
</button>
</div>The badge's ring punches it out of the icon beneath it, and --pulse advertises unread mail — a read tray must sit still.
A printed count beside a list the page already knows the length of is a second writer, and this codebase has shipped that bug more than five times. One function owns the number and both the badge and the list read from it; tests/msgs.mjs asserts all four unread-count locations agree.
Chip
A chip is a tag: a label a reader scans, not a status a system sets. That is the whole difference from a badge, and it is why a chip is square-ish and quiet while a badge is a pill.
html
<span class="av-chip">Work</span>
<span class="av-chip av-chip--primary">Design</span>
<span class="av-chip av-chip--danger">Bug</span>
<span class="av-chip av-chip--sm">Dense</span>Plain is the default; the role modifiers are the same six soft-surface() roles every other component here uses, so a board and a mailbox cannot invent two palettes for one idea. --sm is for a label on a card, where a row of tags competes with the title above it.
This component is why
lint:cssforbids a class defined in two component partials._kanban.scssand_mail.scsseach declared.av-chipat 0-1-0 in the same layer, so what a chip looked like was decided by@useorder — and the result was neither of them. Equal specificity in one layer resolves per property: mail wonfont-weight,padding,border-radiusandbackground, while kanban kept the two mail never mentioned,min-block-sizeandletter-spacing. Every chip on four pages was rendering as a merge of two components nobody designed, and each partial looked correct on its own.
The role modifiers used to be --design, --bug, --content, --research and --infra — five names from one board's domain, living in a component partial. A label on a card carries a role, not a subject; the board maps its own subjects onto the roles now.
Not built
There is no --removable, no .av-chip__remove button and no --filter toggle. Filter controls in this build are .av-facet checkboxes and the data-grid filter drawer, both of which keep the filter's state where the list can read it rather than on a chip that has to be kept in sync.
Dots
Two components that look alike and answer different questions.
html
<!-- "There is something here" — a count badge with no count -->
<span class="av-dot av-dot--danger" aria-hidden="true"></span>
<!-- Presence -->
<span class="av-status-dot av-status-dot--busy" aria-hidden="true"></span>| Component | Variants | Meaning |
|---|---|---|
.av-dot | --success, --warning, --danger, --info, --neutral (primary is the base) | Unseen activity, on a sidebar row or a bell |
.av-status-dot | --online, --away, --busy, --offline | A person's availability |
Both are aria-hidden, and the meaning is carried by the control's accessible name. A reader that picks up a bare dot announces nothing useful; one that picks up a digit announces a number with no noun attached.
The status dot's ring is a border in the surface colour, not a box-shadow. Over an avatar the dot has to punch a hole in the image, and a border does that by participating in the border box — a shadow paints over the top and shifts with any transform on the parent.
Timeline
An ordered list of events. The marker is decorative and the order is in the markup.
html
<ol class="av-timeline">
<li class="av-timeline__item av-timeline__item--success">
<span class="av-timeline__marker" aria-hidden="true">
<svg class="av-icon" viewBox="0 0 24 24"><path d="M4 12.5l5 5 11-11"/></svg>
</span>
<div class="av-timeline__body">
<p class="av-timeline__title">Payment captured</p>
<p class="av-timeline__text">€284.52 via Visa ending 4242.</p>
<p class="av-timeline__meta"><time datetime="2026-08-14T06:41">Today, 06:41</time></p>
</div>
</li>
</ol>The role modifier goes on the item, not the marker — .av-timeline__item--success tints the marker through a child selector, so one class per entry decides both the tint and anything else the state should reach.
__meta separates its children with a · from a pseudo-element, so a date, an author and a reference can be written as three plain elements without a separator in the markup.
The connecting rail is drawn on the item rather than as a pseudo-element on the list, so it stops cleanly at the last marker without needing to know how many items there are.
is-new on an item gives it one gentle highlight, so an entry that arrived while the reader was looking elsewhere is visible. It is disabled under prefers-reduced-motion.
Stepper
A timeline records what happened; a stepper says where you are.
html
<ol class="av-steps" aria-label="Fulfilment progress">
<li class="av-steps__item" data-av-state="done">
<span class="av-steps__marker" aria-hidden="true">
<svg class="av-icon" viewBox="0 0 24 24"><path d="M4 12.5l5 5 11-11"/></svg>
</span>
<span class="av-steps__label">Placed</span>
</li>
<li class="av-steps__item" data-av-state="current" aria-current="step">
<span class="av-steps__marker" aria-hidden="true">2</span>
<span class="av-steps__label">Fulfilled</span>
</li>
<li class="av-steps__item" data-av-state="todo">
<span class="av-steps__marker" aria-hidden="true">3</span>
<span class="av-steps__label">Delivered</span>
</li>
</ol>The state is data-av-state — an enumerated value, per the state convention — and the current step also carries aria-current="step". Both are needed: the attribute drives the styling, and aria-current is what a screen reader announces.
Activity feed
html
<ul class="av-activity">
<li class="av-activity__item">
<span class="av-avatar av-avatar--sm" aria-hidden="true">SK</span>
<div>
<p class="av-activity__text">
<strong>Sarah Kim</strong> approved refund <strong>#10479</strong>
</p>
<span class="av-activity__time">
<time datetime="2026-08-14T08:48" data-av-relative-time>08:48</time>
</span>
</div>
</li>
</ul>A <ul>, not an <ol>: a feed is a collection of events that happen to be sorted, where a timeline is a sequence in which order is part of the meaning. Rows are separated by a border on __item + __item, so the first row has no rule above it and the last none below.
Detail list
html
<dl class="av-detail-list">
<div><dt>Email</dt><dd><a href="mailto:mark@acme.io">mark@acme.io</a></dd></div>
<div><dt>Phone</dt><dd><span dir="ltr">+353 1 234 5678</span></dd></div>
<div><dt>Customer since</dt><dd><time datetime="2024-03-02">2 Mar 2024</time></dd></div>
<div><dt>Lifetime value</dt><dd><span data-av-money="284500">€2,845.00</span></dd></div>
</dl>Each pair is wrapped in a <div>. That is the only way to make dt/dd a grid row without losing the definition-list semantics a screen reader announces.
The label column is minmax(0, 7rem), and --stacked puts the value under the key instead of beside it — for a side panel where 7rem of label leaves nothing for the value. Below 576px the base component stacks on its own.
A phone number gets dir="ltr": it is not natural-language text and it must not follow an right-to-left interface, or the + moves to the wrong end.
Money and relative time
Both are markup with a server-rendered fallback, reformatted at boot. Neither is derived in JavaScript from something else on the page.
html
<span data-av-money="2845200">€28,452.00</span>
<time datetime="2026-08-14T06:41" data-av-relative-time>Today, 06:41</time>data-av-money holds integer minor units; the visible text is what the server rendered and what a reader sees if the bundle never arrives. AdminVora.utils.formatCurrency rewrites it through Intl at boot, so changing the browser's locale and reloading changes every figure and no markup. Floating point and hand-rolled thousands separators are both ways of being wrong in a currency somebody actually uses.
Add data-av-money-compact for a headline figure, such as a KPI tile: the amount is written in compact notation with three significant digits ("€87.4K", "€1.05M"), and the exact amount goes into the element's title.
html
<div class="av-stat-card__value" data-av-money="8742000" data-av-money-compact>€87.4K</div>data-av-relative-time rewrites the visible text to "3 days ago" and leaves datetime alone, so the exact timestamp is still there for anyone who needs it.
Three things about it are worth knowing before you use it:
- The hook only works on a
<time>with a parseabledatetime. The module readsel.getAttribute('datetime')and returns silently when the result is not a date — so on a<span>, or with a typo, the server-rendered fallback simply stays on screen and nothing fails.npm run check:demo-datesholds both halves: the hook must sit on a<time>, and the value must parse. - It renders once, at init. There is no interval and no re-render; "2 minutes ago" on a page left open for an hour still says two minutes. That is a deliberate trade in a zero-build runtime — a timer per timestamp on a page with sixty of them is sixty timers — and it is stated here because the opposite is easy to assume.
- A hooked timestamp may not be in the future. Feed it a date after the demo's "now" and the same code renders "in 4 days" in a Last active column.
check:demo-datesfails the build on one, and pins the demo's instant to the clocktests/visual.mjsfreezes so the two cannot drift.
Progress
html
<div class="av-channel">
<div class="av-channel__row">
<span class="av-channel__name">Storage used</span>
<span class="av-channel__value">68%</span>
</div>
<div class="av-progress" role="progressbar" aria-valuenow="68"
aria-valuemin="0" aria-valuemax="100" aria-label="Storage used">
<div class="av-progress__bar" style="inline-size: 68%"></div>
</div>
</div>.av-channel is the label-and-value row above a bar; .av-progress is the track and .av-progress__bar the fill. --indeterminate animates the fill for work whose length is unknown, and takes no aria-valuenow.
A ring is the same value in a different shape. The value is set once as --av-ring-value and the stroke maths follows it:
html
<div class="av-progress-ring" style="--av-ring-value: 68" role="progressbar"
aria-valuenow="68" aria-valuemin="0" aria-valuemax="100" aria-label="Storage used">
<svg viewBox="0 0 44 44" aria-hidden="true">
<circle class="av-progress-ring__track" cx="22" cy="22" r="20"></circle>
<circle class="av-progress-ring__fill" cx="22" cy="22" r="20"></circle>
</svg>
<span class="av-progress-ring__label">68%</span>
</div>The width is for the eye; the attribute is for everyone else. Every bar and ring carries role="progressbar" with a real aria-valuenow and a label — a <div> at 68% width announces nothing at all.
A stack of .av-channel rows is usually a better choice than a pie chart: the exact values are readable, it works at any width, and it needs no data-table fallback.
Identifier
html
<th scope="row" class="av-ident">PT-4846</th>
<td class="av-ident av-ident--sm" data-av-key="sku" data-av-value="BP-S-BL">BP-S-BL</td>An SKU, an order number, a charge reference, a discount code, a delivery or patient id — anything a machine produced and a person may have to transcribe. It is set in the mono face for the reason code is: 1, l and I are the same shape in a proportional face, and so are 0 and O.
--sm drops it to xs. The distinction is the role, not the taste: an identifier in a <th scope="row"> names the row and stays at the table's own size, while one in a <td> or a <dd> is one value among several and reads as secondary. Pick by which of those the cell is doing.
These thirty-nine cells carried the face inline before the class existed, and collecting them is what exposed the inconsistency: two detail lists disagreed with each other about the size for the same charge reference. Choosing one value for all of them would move nine pages, which is a design decision rather than a refactor — so both roles are named and the pages render unchanged.
Gantt
A schedule: one row per task, a bar across the weeks it runs, a fill for how much is done and a line for today. The stylesheet draws it; there is no script. Each bar carries its own numbers as custom properties.
html
<div class="av-gantt" role="region" aria-label="Project schedule" tabindex="0"
style="--av-gantt-cols: 4; --av-gantt-now: 1.43">
<div class="av-gantt__head" aria-hidden="true">
<span></span>
<div class="av-gantt__scale"><span>3 Aug</span><span>10 Aug</span><span>17 Aug</span><span>24 Aug</span></div>
</div>
<ul class="av-gantt__rows">
<li class="av-gantt__row">
<div class="av-gantt__task">
<span class="av-gantt__name">Checkout redesign</span>
<span class="av-gantt__meta">3 Aug to 30 Aug · 70% done</span>
</div>
<div class="av-gantt__track" aria-hidden="true">
<span class="av-gantt__bar av-gantt__bar--success" style="--av-gantt-start: 1; --av-gantt-span: 4; --av-gantt-done: 70"></span>
</div>
</li>
<li class="av-gantt__now" aria-hidden="true"></li>
</ul>
</div>| Custom property | On | Meaning |
|---|---|---|
--av-gantt-cols | .av-gantt | How many columns the chart has |
--av-gantt-now | .av-gantt | Where today falls, in columns from the start (1.43 is 43% into the second) |
--av-gantt-start | a bar | The column the bar starts in, counted from 1 |
--av-gantt-span | a bar | How many columns it covers |
--av-gantt-done | a bar | Per cent complete, drawn as the darker fill |
.av-gantt__bar--success, --warning and --danger colour a bar by its state. The bars are decoration: write the dates and the progress in .av-gantt__meta, which is what a screen reader reads. The chart scrolls sideways inside itself on a narrow column, so give it role="region", a label and tabindex="0". It does not draw dependencies between tasks, and it is not editable.
Prose block
html
<p class="av-prose">Water-resistant 24L daypack with a roll-top closure.</p>A block of written English: a 70-character measure, looser leading and secondary ink. Past roughly seventy characters the eye loses the start of the next line, which is why the measure is capped rather than left to fill the column.
It carries no padding. A pane that needs edges supplies them itself — .av-message-body in the mail reader is exactly that and nothing more.
Code
html
<pre class="av-code" tabindex="0"><code>AdminVora.toast.success('Order #1042 saved');</code></pre>Two decisions in this component are about direction rather than appearance:
direction: ltron the block. Source code is left-to-right in every locale. Without it, a snippet underdir="rtl"overflows towards the inline start, which is outside the scroll container's start edge — the block scrolls the wrong way and the code runs off the side of the viewport.tests/rtl.mjscaught exactly that on the UI-kit overview.unicode-bidi: isolateon inline code. A class name inside a right-to-left sentence gets its punctuation reordered by the bidi algorithm otherwise, and.av-btn--primarycomes out with its leading dot on the wrong end.
It scrolls inside its own box rather than widening its grid track — an over-wide <pre> is the classic way a page pushes .av-content past the viewport, which is what tests/pages.mjs measures. tabindex="0" is required, because a scroll container that cannot be focused cannot be scrolled by keyboard.
Copy
html
<code class="av-code" id="ui-copy-src">npm run create -- my-app --kit=laravel</code>
<button class="av-btn av-btn--ghost" type="button" data-av-clipboard="#ui-copy-src">
<span data-av-clipboard-label>Copy command</span>
</button>data-av-clipboard holds a selector, and the text is read from the rendered element it names — never from a duplicate string in an attribute, which is the same rule the icon index follows: two copies of one thing, and the one nobody looks at is the one that rots. With no value it falls back to the button's previous sibling.
data-av-clipboard-label marks the span whose text is swapped to "Copied", and the original is restored from what was there rather than a hard-coded string — so a button that said "Copy token" does not come back saying "Copy". data-av-state is set to copied or failed for styling, and the result is announced.
The failure path is not theoretical. navigator.clipboard is unavailable on an insecure origin, and these demo pages are built to be opened from file:// — so the button reports "Press Ctrl+C" rather than doing nothing, which is the difference between a limitation and a broken control.
One-time codes
.av-code-list is a grid of recovery codes — meant to be read, printed and taken away, which is the opposite job from .av-secret. A used code stays in the list with is-used, struck through, rather than being removed: a list that silently shrinks from ten to eight reads as a bug in the page, where two struck out is a record of two sign-ins. The strike is paired with a note in words, because a strike alone is not announced.
The example block
Every code sample on the UI-kit pages is a .av-example: the rendered component, a Code toggle and a Copy button, with the source in a .av-code.av-example__code panel that is hidden until asked for. It is generated by tools/build-html.mjs from the same markup it renders, so the sample a reader copies cannot drift from the component above it.
Keyboard key
html
Press <kbd class="av-kbd">Ctrl</kbd> + <kbd class="av-kbd">K</kbd> to open the command palette.A real <kbd>, so it is announced as one.
A placement debt, recorded rather than hidden.
.av-kbdis defined insrc/scss/layout/_topbar.scss, because the search trigger needed it first — but it is used by the shortcuts dialog, the command palette, three utility pages and the UI-kit. That is the pattern this repository has already corrected three times (.av-sectionout of_example.scss,.av-avatarout of the topbar partial,.av-table__linkout of a customer-shaped name): a primitive named or filed under the first screen that wanted it. It belongs in its own component partial.
A person in a table
html
<th scope="row" data-av-key="user" data-av-value="Amara Okafor">
<span class="av-table__person">
<span class="av-avatar av-avatar--sm" aria-hidden="true">AO</span>
<span>
<a class="av-table__link" href="user.html">Amara Okafor</a><br>
<span class="av-table__person-meta">amara@northwind.io</span>
</span>
</span>
</th>The person cell is the most repeated composition in the product — it appears on seventeen page sources, for customers, users, deal owners, employees, post authors, project leads and ticket reporters.
.av-table__link is the row's own link, and it is not underlined at rest. Underlining puts a rule under every row and turns the column into a wall of chrome competing with the data; the underline arrives with the pointer, and a focus ring arrives with the keyboard. Colour is deliberately not the signal — both of those survive a colour-blind reader, and the cell is already carrying a badge and two shades of grey.
All three parts were called
__customeronce, for the first table that used one — and none of these rows is necessarily a customer..av-table__customer-namebecame.av-table__linkwhen the demo index needed a row link;__customerand__customer-mailwere left behind and became__personand__person-meta. The second line is-metarather than
Accessibility checklist
- [ ] Avatar
altis empty when the name is adjacent, populated when it is the only identifier - [ ] An avatar's initials are
aria-hiddenwhen the name is beside them - [ ] Presence and activity dots are
aria-hidden; the state exists as text somewhere reachable - [ ] An avatar group carries one
role="img"and one name, not four unlabelled discs - [ ] Badges pair colour with an icon or text; colour is never the only signal
- [ ] A count appears in the control's accessible name, and one function owns the number
- [ ] Timelines use
<ol>; activity feeds use<ul> - [ ] A stepper carries both
data-av-stateandaria-current="step" - [ ]
<dl>with a<div>per pair for label/value lists - [ ] Relative times keep the absolute value in
datetime, and the hook sits on a<time> - [ ] Progress bars and rings carry
role="progressbar",aria-valuenowand a label - [ ] Scrollable code blocks have
tabindex="0" - [ ] Code blocks are
direction: ltr; inline code isunicode-bidi: isolate
Read next: Animated Icons.