# graview-view-links `graview-view-links` is one of Graview's 31 authoring skills: instructions an AI coding assistant such as Claude Code or Codex reads before it changes a Graview app. What it teaches: Send a person from a Graview worker view to a record, a place or a list — an , or a whole card or row bound to a record that opens on a click, a phone's tap and Enter — narrowed and to a section, and prove each lands by pressing it on a phone as well as a desk rather than assuming a card the describer lists opens. Installed into a project by `graview skills install .`, and read by whichever assistant is working beside you. ## The skill ## Links in a worker view A worker view (`graview-worker-view`: its manifest, its global, its limits) writes no address of the page's: an `href` it built is never drawn. What it may link to is a record, a named place or a kind's list of this app, and the host makes that a link and follows it, on both faces, only to what the viewer may see. **Go somewhere with a link, do something with a button.** `` or `` to go; ` ``` The heading's `` is the keyboard's and the screen reader's link; the card, a `
` or an `
  • ` alike, takes no role and no tab stop of its own, and is a bigger target: the host draws it with a pointer, `touch-action: manipulation` and a faint tap highlight, and follows it on a click and a phone's tap anywhere inside it — its heading, a badge, a line — unless the press lands on something with a press of its own: a button, a field, a `data-act`, a lightbox, a drop target, a control's `role`, another link. So "More" above toggles and opens nothing, and the audit finds no link inside a link. A card with no such `` is given the keyboard and `role="link"` itself (a list's item keeps its role; a table's row gives the keyboard to its first cell); then it may hold no button, and a heading that links elsewhere is a link inside a link. It is no link when it is a press scope: a `fieldset` or `role="group"` (the record a form's acts are done to), an element with `data-act`, `data-lightbox`, `data-drop` or `data-field`, a field, or an element that holds a field to type into or pick from (a checkbox inside leaves its row a link). Link such a card's title instead: `

    `. Do not work around it: no `data-open` with `graview.on("click", …, graview.navigate)`, no `pointer-events: none` on a card's children, no `touch-action` of your own. A card that should do something of its own on a press carries `data-key`, not `data-record`, and `graview.on`. ### How a tap reaches the view A phone makes a tap a `click` on what the finger landed on; iOS does so only on what looks pressable, which is why the host draws every link with a pointer. The host hears it on the view's shadow root, follows a link first, then tells the view, which hears `click` as it hears a mouse's: `graview.on("click", ".card", (e) => …)` is handed `e.target`, what the finger landed on, and `e.element`, the element the selector matched at or above it, so a tap on a card's heading hands the card. ### Narrowed, and to a section A list or a lens may be gone to **narrowed**: `where: { stage: "building" }` in navigate, `data-filter="stage:building"` on a link — the words the list's own arranging line writes, so the address is `/features?filter= stage%3Abuilding` and can be shared. A lens narrows the records it is handed; a blocks lens lists what its own `where` says. Any destination may take a **section**, a heading's words or an element's id (`section: "Every feature"`, `data-section`): the page scrolls there and gives it the keyboard (`#every-feature`). On the scene a list is the kind's stop narrowed (`in.filter`); a section is looked for there too. A filter on a field the kind lacks, or a choice it lacks, goes nowhere and says why (`Features have no field "stag" to filter by; they filter by …`), so link to the list narrowed rather than to a lens per filter; a lens kept only as a link target can be hidden (set-lens-hidden, `graview-pages`). ### A jump, what is in sight, and a file `` jumps to an element of the view's own: the host scrolls it to the top, below its own sticky bar, gives it the keyboard and leaves the address alone. A scroll margin on it (scroll-margin-top) clears a sticky header you draw. The elements jumps name, and any with `data-sight`, are watched as the page scrolls: the one in sight is `data-in-sight`, its jumps `aria-current="location"`, and the view hears `sight` on it (`graview.on("sight", "section", …)`). `` opens a record's file in a tab of its own; `data-download` downloads it under its own name. ### A column the menu knows Mark a region that holds one value of a field `data-column="status:doing"` (and `data-column-kind="task"` where the place is not that kind's; a heading's words in `data-column-label`). A right-click there, as on a status board's column, offers "Add a task in Doing" — the add act with `status` given — and "Show only Doing", the place narrowed as above. ### Then find out whether it worked 1. `graview check` the app the view links into: a link is only as sound as the records and places it names. 2. `graview view check view.js --app --manifest manifest.json --seed --roles ` says every `data-record` or `data-place` that names nothing the seat was shown and no place, and every filter that goes nowhere, and presses each link, jump and file link: one that goes nowhere fails. `--press ".card h3"` presses there and says where the host would go, or that the press is a button's of its own. `--audit` holds what it drew to the keyboard and screen-reader rules, as the host draws it: a `
    ` heard only by `graview.on("click")`, a control or link with no name, a toggle with no state, a button inside a card that opens, an `` with no alt. Each comes with its WCAG criterion and a one-line fix, and the check fails on what the view must fix. Contrast, the ring and a keyboard trap need a browser: add `--browser` (the project's Playwright and its Chromium) to run them. 3. Open it on a phone, 390 pixels wide with touch: tap a card's heading and a badge inside it, and see the record's page; tap a toggle inside it, and see it toggle and stay. On a desk, Tab through the view: every link and button is reached, with a ring; Enter on a card opens it, and Cmd-click on an `` opens it in a new tab. 4. Follow each link narrowed and to a section, and see it land where it says. ### What the check cannot see `graview check` judges the declaration, not the view. A headless run lays nothing out, so it cannot see a card covered by something drawn over it, a link too small to tap, or a card that looks like it opens and holds a field. Only tapping it on a phone does. Nor can it see a link that goes somewhere true but unhelpful. --- Send a person from a Graview worker view to a record, a place or a list — an , or a whole card or row bound to a record that opens on a click, a phone's tap and Enter — narrowed and to a section, and prove each lands by pressing it on a phone as well as a desk rather than assuming a card the describer lists opens. The page: https://graview.dev/docs/skills/graview-view-links.html · Every Graview docs page, for a model: https://graview.dev/llms.txt