| ui/NkSearchFilter.tsx:71 | focus:border-primary/30 | outline-none removes the native focus ring; focus:border-primary/30 + focus:bg-card/90 ARE the replacement indicator, and they are COLOUR ONLY — a consumer re-skinning this field to their own palette removes the only way to see where the keyboard is. It cannot be made expressible without adding a ring to a shipped control, which is a visual change to every call site and belongs in its own deliberate pass; it cannot be protected (see the header). So it is recorded. |
| ui/NkCheckbox.tsx:61 | group-data-[selected]:bg-primary | group-data-[selected]:bg-primary/border-primary is the only checked affordance the BOX itself has; without it the box renders invisible (`:52-57` records that shipping). Colour only — the glyph's scale is the expressible half, recorded separately below. |
| ui/NkCheckbox.tsx:70 | selected && 'scale-100' | the check glyph's presence is a `scale` transform, not a mount/unmount, so the checked state survives any colour re-skin: a consumer who repaints the box cannot remove the glyph appearing. This is what makes the colour entry above a degradation rather than a total loss. |
| ui/NkCheckbox.tsx:71 | !selected && 'scale-0' | the other half of the same transform. Recorded separately because the two are on separate lines and a refactor that keeps one and drops the other leaves a glyph that is always visible. |
| ui/NkSwitch.tsx:56 | group-data-[selected]:bg-primary | group-data-[selected]:bg-primary is one of only two on/off signals, and the colour one; `:50-54` records that the previous `not-selected:` spelling never matched and the off-track rendered fully transparent. The travel below is the half that survives a re-skin. |
| ui/NkSwitch.tsx:66 | translate-x-0 group-data-[selected]:translate-x-5 | translate-x-0 → translate-x-5 IS the thumb travel, i.e. the affordance itself, and a transform is not reachable by a colour override — so the on/off state remains perceivable in any palette. Under reduced motion the travel collapses to 1ms rather than disappearing (`motion.css`), so the END POSITION still differs; the indicator is the position, not the movement. |
| ui/NkOtpInput.tsx:728 | text-transparent caret-transparent | text-transparent/caret-transparent keep the real input focusable while invisible; display:none breaks autofill and screen readers (the comment states the alternative explicitly). This is a CONCEALMENT rather than an indicator, so there is no second carrier to fall back on: a consumer who restores a text colour here double-renders the code, once in the real input and once in the cells. Recorded as untouchable. |
| ui/NkTable.tsx:388 | focus-visible:ring-2 | a ring is a box-shadow: re-theming `ring-primary/60` changes the ring's COLOUR, never its existence, so the indicator survives any palette. `ring-inset` is load-bearing geometry rather than taste — the table clips, so an outset ring would be cut off. `NkTable.tsx:51` records the defect this replaced: a `<tr>` carrying a focus-visible class but no tabIndex, i.e. a ring nothing could reach. |
| ui/NkTable.tsx:473 | data-[focus-visible]:ring-2 | the same ring on the ROW, which is the element a keyboard user actually lands on. Recorded as its own site because the three are three separate class strings and a refactor can drop one of them. |
| ui/NkTable.tsx:516 | data-[focus-visible]:ring-2 | the same ring on the CELL, reached by cell-navigation mode. Recorded separately for the same reason as the row: three class strings, three ways to lose it. |
| ui/NkDataTable.tsx:396 | focus-visible:ring-2 | the drag-reorder header's focus ring, inset for the same clipping reason as NkTable's. Reachable only when `reorderable`, which is why it is written as a conditional rather than a base class. |
| ui/NkCloseButton.tsx:97 | focus-visible:ring-2 focus-visible:ring-ring | a box-shadow, so the indicator survives a re-skin. The absence of a ring OFFSET is the part worth recording: `:56-58` explains the offset would be clipped by the overlay edge, so "adding the missing offset" is a plausible-looking change that silently removes the indicator on exactly the surface this button exists for. |
| ui/NkDropdownMenu.tsx:124 | data-[focused]:bg-primary/10 | the menu item's ONLY focus indicator, and it is colour only (`outline-none` is on the line above). It satisfies WCAG 2.4.7 today — something visible does change — but a consumer who re-skins `bg-primary/10` to their own hover colour can flatten focused and unfocused into the same pixels. Same class of site as NkSearchFilter:71, same verdict, and found only because this record was re-derived from the source rather than copied from the inventory. |
| ui/NkNumberPicker.tsx:155 | focus-visible:ring-2 focus-visible:ring-ring focus-visible:ring-inset | WAS a 2.4.7 failure: `focus:outline-none` stood alone and the field had no focus indicator at all (measured in a browser: `outline: none`, `box-shadow: none` on a focused input). The ring added in this pass is inset, because the enclosing Group is `overflow-hidden` and clips an outset one — the same geometry NkCloseButton records. |
| ui/NkLogin.tsx:154 | focus-visible:ring-2 focus-visible:ring-ring | WAS a 2.4.7 failure: `outline-none` on a text button whose only affordance was `hover:underline`, which a keyboard user never triggers. The ring added in this pass carries an offset (nothing clips here) and `focus-visible:underline` beside it, so the indicator is not a ring alone under forced colours. |