Files
Charlie CheeverandClaude Opus 5.5 73b87a17c6 Apple's tables say where each cell stands and visit rows as drawn
The Apple hosts exposed a table, its rows and its cells by role only, and
AppKit visited a `tfoot, tbody, tfoot` table's rows as written (Foot 1,
Body, Foot 2) where the table draws Body, Foot 2, Foot 1 (CSS 2.2 §17.2).

The Apple host now sends the kernel's table formation to the presenter
after each layout, as it sends sticky constraints and column fragments:
a `table` op with a table's rows, columns and drawn order
(`Kernel::table_size`, `Kernel::table_order`) and each row's and cell's
place (`Kernel::table_place`). `Kernel::table_views` lists the views
table formation laid out, so the host reads only those. The op is
declared in `kernel/tables/schema.json`, which rotates the schema's
digest; the codec's digest snapshot and the shared-font plan fixture
carry the new one.

On the Mac a table answers `NSAccessibilityTable`'s accessors: its rows
in drawn order, column elements, its header group, its column and row
headers, `AXCellForColumnAndRow`; a row its index, and a cell its row and
column index ranges and its headers. AppKit's attribute protocol, which
is what VoiceOver is served, lists none of these from the accessors
alone (measured on macOS 27), so `NodeView`'s attribute overrides serve
them. Its children, and so VoiceOver's navigation order, follow the
drawing.

On iOS a table is UIKit's data table (`UIAccessibilityContainerDataTable`):
its size, the cell at a row and column, its headers, and its elements in
drawn order. A cell of words is one element, read by its words, a `th`
with the header trait; every node in a cell answers the cell's row and
column ranges, as WebKit's elements do, so a cell holding a control
still says where it stands. `tree --ax` shows a table's size and a
cell's place under `native` (`collection`, `item`), as Android's does.

A description list stays a list: neither UIKit nor AppKit has a term or
definition role, and WebKit serves a `dl` the same way.

AppKit's and UIKit's in-process answers are tested on a compiled fixture
(spans, row and column headers, drawn order, an empty table) and failed
before; VoiceOver itself was not run, since this machine's terminal is
not trusted for accessibility.

Follows up #669.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
2026-11-15 10:52:03 -08:00
..