Board's card title and Calendar's entry title (issues #96, #105) render the Collection's resolved primary field as a bare <input> via PropertyValueCell, with no associated <label> or aria-label. A screen reader announces it only as "edit text," not as the record's title field — unlike every other labeled control on the same card/entry (the delete/expand buttons both carry explicit aria-labels).
PropertyValueCell.svelte's other input types (number, date, select, checkbox) have the identical gap, but the primary-field title cell is the most visible instance, since it's the one control every Board card and Calendar entry always shows.
Surfaced during PR reflection on #268 (Calendar's mirror of Board's editable-title pattern).
Not in scope: the broader Bits UI primitive adoption tracked in #262 — that's overlay/dialog/menu accessibility mechanics, a different surface than this plain-input labeling gap.
Done when: the title input on a Board card or Calendar entry has a screen-reader-announced name identifying which field it edits, verified by a component test.
Priority: P2 — matches every comparable accessibility-adjacent issue currently on the board (#250, #251, #262 are all P2). Targeted at 0.4.0 since #96/#104/#105 (the features that introduced/duplicated this gap) all ship in this milestone, which names WCAG 2.1 AA as a cross-cutting acceptance bar.
Board's card title and Calendar's entry title (issues #96, #105) render the Collection's resolved primary field as a bare
<input>viaPropertyValueCell, with no associated<label>oraria-label. A screen reader announces it only as "edit text," not as the record's title field — unlike every other labeled control on the same card/entry (the delete/expand buttons both carry explicitaria-labels).PropertyValueCell.svelte's other input types (number, date, select, checkbox) have the identical gap, but the primary-field title cell is the most visible instance, since it's the one control every Board card and Calendar entry always shows.Surfaced during PR reflection on #268 (Calendar's mirror of Board's editable-title pattern).
PropertyValueCell's inputs an accessible name — at minimum, the primary-field title usage inBoardCollectionView.svelteandCalendarCollectionView.svelte(e.g.aria-label="{property.label}")getByRole('textbox', { name: ... })resolves for the title inputNot in scope: the broader Bits UI primitive adoption tracked in #262 — that's overlay/dialog/menu accessibility mechanics, a different surface than this plain-input labeling gap.
Done when: the title input on a Board card or Calendar entry has a screen-reader-announced name identifying which field it edits, verified by a component test.
Priority: P2 — matches every comparable accessibility-adjacent issue currently on the board (#250, #251, #262 are all P2). Targeted at 0.4.0 since #96/#104/#105 (the features that introduced/duplicated this gap) all ship in this milestone, which names WCAG 2.1 AA as a cross-cutting acceptance bar.