new·The score now tells you which way it movedA brain's exam only ever grows: its own material writes questions, and so does every question a real caller asked and did not get answered. The score is a percentage over that growing set, so a brain that learned more could post a smaller number — and this week three did. One of them answered two MORE questions than the week before and showed eighteen points less. Printed as a single percentage, that reads as decline to a reader and as punishment to anyone who contributes material.all news →
mozg.beta
Sign in

shadcn/ui · Components · all subjects

attachment/accessibility

6 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

AttachmentAction accessibility

AttachmentAction is usually icon-only and renders a Button. Give each action an aria-label attribute describing the action and its target, for example: <AttachmentAction aria-label="Remove sales-dashboard.pdf"><XIcon /></AttachmentAction>

Label icon-only attachment actions

AttachmentAction is usually icon-only, so give each one an aria-label describing the action and its target. Example: ```tsx <AttachmentAction aria-label="Remove sales-dashboard.pdf"> <XIcon /> </AttachmentAction> ```

Label the attachment trigger

AttachmentTrigger covers the card with no text of its own, so give it an aria-label for what activating it does. Example: ```tsx <AttachmentTrigger asChild> <a href={url} target="_blank" rel="noreferrer" aria-label="Open workspace.png" /> </AttachmentTrigger> ```

Attachment trigger stacking order

The AttachmentTrigger sits behind the actions in the stacking order, so an AttachmentAction and the AttachmentTrigger never trap each other. Both remain separately focusable and clickable.

Keyboard scrolling in AttachmentGroup

An AttachmentGroup scrolls horizontally. When its attachments are interactive (a trigger or actions), keyboard users reach off-screen items by tabbing to them. For a row of presentational attachments, make the group itself focusable and scrollable by adding tabIndex={0}, role="group", and an aria-label.

Error state color accessibility

The error state uses a destructive color. Keep the failure reason in AttachmentDescription so the state is not conveyed by color alone.

Give your agent this brain