ranger-compiler 3.5.0 → 3.5.2

package/dist/lib/evg/gl/evg-a11y.js

@@ -0,0 +1,566 @@
+/**
+ * evg-a11y.js — the accessibility tree, as DOM, over the canvas.
+ *
+ * A screen reader does not look at pixels. It asks the browser for the tree it
+ * built out of the DOM, and a <canvas> contributes one empty graphic to that
+ * tree no matter what was drawn into it. So the app publishes what the frame
+ * MEANS — `EVGA11yTree`, built in Ranger beside the display list — and this
+ * file turns it into real DOM elements positioned over the canvas, with the
+ * roles, names and states the tree carries.
+ *
+ *   GridApp ─┬─ sceneJson()  ─► evg-webgl.js  ─► pixels
+ *            └─ a11yJson()   ─► THIS FILE     ─► DOM  ─► NVDA / VoiceOver / Orca
+ *
+ * Google Sheets does the same thing for the same reason. There is no other
+ * approach that works: `role="application"` plus an announcement region gives a
+ * reader nothing to explore, and nothing to put a braille cursor on.
+ *
+ * What the elements look like
+ * ---------------------------
+ * They are transparent rather than hidden. `display:none` and
+ * `visibility:hidden` remove a node from the accessibility tree, which is the
+ * one thing being built here, and `opacity:0` is treated as hidden by some
+ * combinations. Transparent ink over a canvas that already drew the same text
+ * is visible to the accessibility API and invisible to the eye.
+ *
+ * They are positioned at their real rectangles, because a rectangle is not
+ * decoration: touch exploration on a tablet, a screen magnifier following the
+ * cursor, and "route the mouse to the focus" all use it.
+ *
+ * The container takes no pointer events, so the mouse keeps going to the canvas
+ * and the app's own hit testing stays the only hit testing. A reader ACTIVATING
+ * an element still arrives as a click on that element — and this file answers it
+ * by pressing the app where the element is. That is deliberately not a mapping
+ * table from node ids to commands: there is nothing to keep in step with the
+ * app, and a button that moved is still pressed in the right place.
+ *
+ * Focus
+ * -----
+ * The app owns it. Whatever `tree.focus` names is the only element with
+ * `tabindex="0"` — the roving tabindex an ARIA grid is built on — and this file
+ * calls `.focus()` on it when it changes. It never tells the app that focus
+ * moved, because a mirror that reports focus back gets into a loop with the app
+ * that is trying to set it.
+ *
+ * Updates
+ * -------
+ * Elements are kept in a map by node id and reused. That is what makes the ids
+ * matter: rebuilding the subtree under a reader's cursor loses the cursor, and
+ * the ids the tree carries are derived from identity — `sheet/cell:B7` — so a
+ * repaint, a scroll and a recalculation all leave the same element in place.
+ * A tree whose `gen` has not changed is skipped entirely.
+ */
+
+const HIDDEN_ROLES = new Set(["none", "presentation"]);
+
+// Roles whose own text IS the content, so the element carries it as text and
+// takes no aria-label — a label would override the content and read instead of
+// it. The rest get an aria-label and are containers for their children.
+const CONTENT_ROLES = new Set([
+  "text", "heading", "button", "gridcell", "columnheader", "rowheader",
+  "checkbox", "radio", "tab", "menuitem", "menuitemcheckbox", "menuitemradio",
+  "listitem", "link",
+]);
+
+// A native <button> is better understood by every screen reader than a div with
+// role="button", and it is activatable without any extra key handling. A
+// textbox is a native <input> for the same reason, and for one more: it is
+// the element the text-input bridge edits in. A div with role="textbox" and
+// the value as its text is a textbox a reader can read and not type into —
+// measured with the RealTrainer port: the reader found the field, Tab could
+// not leave it for the send button, and the mouse could not select in it.
+function elementFor(role) {
+  if (role === "button") return document.createElement("button");
+  if (role === "textbox") {
+    const input = document.createElement("input");
+    input.type = "text";
+    input.autocapitalize = "off";
+    input.autocomplete = "off";
+    input.spellcheck = false;
+    return input;
+  }
+  return document.createElement("div");
+}
+
+/**
+ * NOTHING HERE MAY PAINT. The canvas underneath already drew all of it, so a
+ * mirror node that puts one pixel on the screen is a second copy of the page
+ * — and, because the mirror is rebuilt on its own schedule rather than every
+ * frame, a second copy AT AN OLDER SCROLL OFFSET. Two pages superimposed.
+ *
+ * `color: transparent` is not enough to promise that, and the gap is exactly
+ * where it hurts: the mirror makes NATIVE controls, because a real <button>
+ * and a real <input> are what readers understand and what the text bridge
+ * edits in — and a native control on iOS is painted through
+ * `-webkit-text-fill-color` and `-webkit-appearance`, neither of which
+ * `color` reaches. Everything a UA can decide to draw is turned off here by
+ * name, and `evg:a11y:paint` holds the list.
+ */
+export function styleBase(el) {
+  const s = el.style;
+  s.position = "absolute";
+  s.margin = "0";
+  s.padding = "0";
+  s.border = "0";
+  s.background = "transparent";
+  s.color = "transparent";
+  s.font = "inherit";
+  // SIXTEEN PIXELS, AND IT IS NOT A DESIGN CHOICE. Nothing here paints, so
+  // the size is invisible — but iOS Safari zooms the whole page in when a
+  // text field it is focusing computes to less than 16px, and the mirror's
+  // `<input>` is what a tap on a drawn field focuses. The page then sat at
+  // some magnification the person had to pinch their way out of, over a
+  // canvas that used to refuse the pinch as well.
+  //
+  // It costs nothing: the node is clipped by `overflow: hidden` below and its
+  // text is transparent either way. Anyone tidying this back to 10px would
+  // bring the zoom back with it, which is why `evg:a11y:paint` holds it.
+  s.fontSize = "16px";
+  s.lineHeight = "1";
+  s.overflow = "hidden";
+  s.whiteSpace = "pre";
+  s.outline = "none";
+  // The three a native control paints itself with, which `color` does not
+  // reach: the fill iOS uses for button and input text, the platform chrome
+  // it would draw around them, and the caret that blinks in a text field
+  // even when its text is invisible.
+  s.webkitTextFillColor = "transparent";
+  s.webkitAppearance = "none";
+  s.appearance = "none";
+  s.caretColor = "transparent";
+  // And the two that paint outside the box, so they are not clipped away by
+  // `overflow: hidden` above.
+  s.textShadow = "none";
+  s.boxShadow = "none";
+  // The canvas underneath already drew all of this. Nothing here should paint,
+  // and nothing here should take a click away from it.
+  s.pointerEvents = "none";
+  s.userSelect = "none";
+}
+
+function setAttr(el, name, value) {
+  if (value === null || value === undefined || value === "") {
+    if (el.hasAttribute(name)) el.removeAttribute(name);
+  } else if (el.getAttribute(name) !== String(value)) {
+    el.setAttribute(name, String(value));
+  }
+}
+
+const TRI = { 1: "false", 2: "true", 3: "mixed" };
+
+/**
+ * Create a mirror over a canvas.
+ *
+ *   host      element that positions the canvas; the mirror is appended to it
+ *             and must sit exactly over the canvas, so the host needs
+ *             `position: relative` and no padding of its own.
+ *   canvas    hidden from the accessibility tree, since the mirror replaces it
+ *   onActivate(node)  a reader pressed something. Default: press the app at the
+ *             node's centre.
+ *   scale     app pixels → CSS pixels, when the canvas is not drawn 1:1
+ */
+/**
+ * @param {object} opts
+ * @param {"roving"|"all"} [opts.tabbable]  "roving" (the default, and what an
+ *        ARIA grid wants): exactly one element is tabbable, the one the app
+ *        says has focus. "all": every focusable node is a tab stop in tree
+ *        order — a page of buttons and fields, where Tab has to walk from the
+ *        field to the send button beside it.
+ * @param {(node: object) => void} [opts.onFocus]  Focus moved inside the
+ *        mirror by the reader or the keyboard — not by the app. Reported so
+ *        the app can follow; the mirror never reports the focus it set itself.
+ */
+export function createA11yMirror(host, { canvas, onActivate, onFocus, canMoveFocus, scale = 1, label = "Application", tabbable = "roving" } = {}) {
+  const root = document.createElement("div");
+  root.className = "evg-a11y";
+  root.style.position = "absolute";
+  root.style.left = "0";
+  root.style.top = "0";
+  root.style.right = "0";
+  root.style.bottom = "0";
+  root.style.overflow = "hidden";
+  root.style.pointerEvents = "none";
+  host.appendChild(root);
+
+  if (canvas) {
+    // The canvas is scenery now. Leaving it in the accessibility tree gives the
+    // reader an empty graphic beside a full tree of real nodes.
+    canvas.setAttribute("aria-hidden", "true");
+  }
+
+  const els = new Map();      // node id → element
+  let lastGen = -1;
+  let lastFocus = null;
+  let settingFocus = false;
+  // The tab stop held open while the app names no focus — see `update`.
+  let entryStop = null;
+
+  function activate(node) {
+    if (onActivate) onActivate(node);
+  }
+
+  function ensure(node) {
+    let entry = els.get(node.id);
+    // A node that changed role cannot keep its element: a <button> does not
+    // become a gridcell, and a reader would keep the old one's semantics.
+    if (entry && entry.role !== node.role) {
+      entry.el.remove();
+      entry = null;
+    }
+    if (!entry) {
+      const el = elementFor(node.role);
+      styleBase(el);
+      if (node.role === "button") {
+        el.type = "button";
+        el.tabIndex = -1;
+      }
+      if (node.role === "textbox") {
+        el.tabIndex = -1;
+        // The bridge takes the pointer while it edits here; until then the
+        // canvas keeps every hit test, as for every other element.
+        el.style.pointerEvents = "none";
+      }
+      el.dataset.a11yId = node.id;
+      el.addEventListener("click", (ev) => {
+        ev.preventDefault();
+        // The elements are NESTED — a row is inside its menu is inside the
+        // bar — so a click that keeps bubbling reaches every ancestor's
+        // listener too, and each one presses the app at ITS OWN centre. One
+        // activation on a menu row then became three: the row, the menu
+        // behind it, and the page behind that.
+        ev.stopPropagation();
+        const n = els.get(node.id);
+        if (n) activate(n.node);
+      });
+      entry = { el, role: node.role, node };
+      els.set(node.id, entry);
+    }
+    entry.node = node;
+    return entry;
+  }
+
+  function applyAria(el, node, byId) {
+    const role = node.role;
+    // A native <button> already has the role; anything else is a div and needs
+    // to be told what it is.
+    if (el.tagName !== "BUTTON") setAttr(el, "role", role);
+
+    const content = CONTENT_ROLES.has(role);
+    if (role === "textbox") {
+      // A field's label and its contents are two different strings, and a
+      // reader announces both: "Formula, equals SUM open paren…". The value
+      // is the input's own; while the input has focus the bridge is writing
+      // it and the app is mirroring it, so it is left alone.
+      setAttr(el, "aria-label", node.name);
+      const text = node.value || "";
+      if (document.activeElement !== el && el.value !== text) el.value = text;
+    } else if (role === "status") {
+      const text = node.value || node.name || "";
+      if (el.textContent !== text) el.textContent = text;
+      setAttr(el, "aria-label", null);
+    } else if (content) {
+      const text = node.name || "";
+      if (el.textContent !== text) el.textContent = text;
+      setAttr(el, "aria-label", null);
+    } else {
+      setAttr(el, "aria-label", node.name);
+    }
+
+    setAttr(el, "aria-description", node.desc);
+    // Some controls are a known role doing an unfamiliar job. A sortable row
+    // is a `button`, and a reader told only that learns nothing about being
+    // able to move it.
+    setAttr(el, "aria-roledescription", node.roledesc);
+    // Open or closed. A trigger that never says which is a trigger a reader
+    // cannot tell has already been pressed.
+    setAttr(el, "aria-expanded", node.expanded ? TRI[node.expanded] || null : null);
+    // What it opens. The tree has carried `haspopup` ("menu", "listbox",
+    // "dialog") and serialised it all along; nothing here read it, so a select
+    // trigger or a date picker's button reached a reader as a plain button
+    // that happened to expand.
+    setAttr(el, "aria-haspopup", node.haspopup || null);
+    setAttr(el, "aria-disabled", node.disabled ? "true" : null);
+    // A native button that is disabled is not a tab stop and not activatable,
+    // which is what the drawn one is.
+    if (el.tagName === "BUTTON") el.disabled = !!node.disabled;
+    if (tabbable === "all" && !(el.tagName === "BUTTON" && node.disabled)) {
+      const stop = node.focusable ? 0 : -1;
+      if (el.tabIndex !== stop) el.tabIndex = stop;
+    }
+    // Three states, passed STRAIGHT THROUGH: "true", "false", or absent.
+    // `node.readonly ? "true" : null` was right while the field was a boolean
+    // and became a bug the moment it became a string — "false" is truthy in
+    // JavaScript, so a field that had been asked and answered no would have
+    // been mirrored as yes. Absent and "false" are different claims, which is
+    // the entire reason these are strings.
+    setAttr(el, "aria-readonly", node.readonly || null);
+    setAttr(el, "aria-required", node.required || null);
+    setAttr(el, "aria-invalid", node.invalid || null);
+    setAttr(el, "aria-modal", node.modal ? "true" : null);
+    // A tab says "false" out loud when it is not the selected one, as Radix's
+    // (and the APG's) do; elsewhere an unselected node carries nothing.
+    setAttr(el, "aria-selected", node.selected ? "true" : node.role === "tab" ? "false" : null);
+    // A toggle button that says so in its own field. `node.pressed` has been
+    // in the tree and in the serialisation all along and NOTHING read it here:
+    // the only route to `aria-pressed` was through `checked`, so a control
+    // that set `pressed` honestly got nothing. Checked first, because a
+    // checkbox mirrored as a toggle would be worse than either.
+    if (!node.checked && node.pressed) {
+      setAttr(el, "aria-pressed", role === "button" ? TRI[node.pressed] || null : null);
+      setAttr(el, "aria-checked", null);
+    } else if (node.checked) {
+      const state = TRI[node.checked] || null;
+      if (role === "button") {
+        setAttr(el, "aria-pressed", state);
+        setAttr(el, "aria-checked", null);
+      } else {
+        setAttr(el, "aria-checked", state);
+        setAttr(el, "aria-pressed", null);
+      }
+    } else {
+      setAttr(el, "aria-pressed", null);
+      setAttr(el, "aria-checked", null);
+    }
+    // A number the reader announces. `now` is deliberately absent on an
+    // indeterminate progress bar: a range with no position in it is how every
+    // platform spells "busy, length unknown", and writing 0 there instead
+    // would have the reader say the work has not started.
+    setAttr(el, "aria-valuenow", node.now == null ? null : node.now);
+    setAttr(el, "aria-valuemin", node.min == null ? null : node.min);
+    setAttr(el, "aria-valuemax", node.max == null ? null : node.max);
+    // Virtualization: the counts are the whole sheet, the indices say where the
+    // emitted rows sit in it.
+    setAttr(el, "aria-rowcount", node.rows || null);
+    setAttr(el, "aria-colcount", node.cols || null);
+    setAttr(el, "aria-rowindex", node.row || null);
+    setAttr(el, "aria-colindex", node.col || null);
+    setAttr(el, "aria-posinset", node.pos || null);
+    setAttr(el, "aria-setsize", node.size || null);
+    // A flat tree carries its nesting HERE and nowhere else: without it a
+    // reader announces a tree as a list of siblings all at the same depth.
+    setAttr(el, "aria-level", node.level || null);
+    // What a key MEANS on a splitter, and the only thing that tells a
+    // horizontal one from a vertical one — every other observation about the
+    // two is identical.
+    setAttr(el, "aria-orientation", node.orientation || null);
+    setAttr(el, "aria-current", node.current || null);
+    setAttr(el, "aria-live", node.live === 2 ? "assertive" : node.live === 1 ? "polite" : null);
+
+    const b = node.b || [0, 0, 0, 0];
+    const parent = hostNode(node, byId);
+    const pb = parent ? parent.b || [0, 0, 0, 0] : [0, 0, 0, 0];
+    // Relative to the element this one is placed IN — see `hostNode` — because
+    // an absolutely positioned ancestor is the containing block for everything
+    // under it.
+    const left = (b[0] - pb[0]) * scale;
+    const top = (b[1] - pb[1]) * scale;
+    const w = Math.max(0, b[2] * scale);
+    const h = Math.max(0, b[3] * scale);
+    const s = el.style;
+    if (s.left !== left + "px") s.left = left + "px";
+    if (s.top !== top + "px") s.top = top + "px";
+    if (s.width !== w + "px") s.width = w + "px";
+    if (s.height !== h + "px") s.height = h + "px";
+  }
+
+  /** Hide everything a modal dialog is covering. A reader that can still walk
+   *  the sheet behind an open dialog will walk it, and none of those keys are
+   *  going anywhere. */
+  function applyModal(tree, byId) {
+    const modal = tree.nodes.find((n) => n.modal);
+    const keep = new Set();
+    if (modal) {
+      let at = modal;
+      while (at) {
+        keep.add(at.id);
+        at = at.p ? byId.get(at.p) : null;
+      }
+    }
+    // Only the top-level regions are hidden or shown: hiding deeper would have
+    // to be undone node by node, and hiding a subtree the dialog is inside of
+    // would hide the dialog.
+    for (const n of tree.nodes) {
+      if (n.p !== tree.root) continue;
+      const entry = els.get(n.id);
+      if (!entry) continue;
+      const hide = modal && !keep.has(n.id);
+      setAttr(entry.el, "aria-hidden", hide ? "true" : null);
+    }
+  }
+
+  // The node whose element holds this one's. Usually the parent; but a
+  // textbox is a native <input>, which can hold no children, so a node under
+  // one — a password field's show/hide button, drawn inside the field's box —
+  // goes under the nearest ancestor that can hold it, and is placed relative
+  // to that one's box. Appended into the <input> it had no box at all: the
+  // reader was told of a button that was nowhere, and a pointer aimed at its
+  // rectangle landed at the page's corner.
+  function hostNode(node, byId) {
+    let at = node.p ? byId.get(node.p) : null;
+    while (at && at.role === "textbox") at = at.p ? byId.get(at.p) : null;
+    return at;
+  }
+
+  function update(tree) {
+    if (!tree || !tree.nodes) return { skipped: true };
+    if (tree.gen === lastGen && tree.focus === lastFocus) return { skipped: true };
+    lastGen = tree.gen;
+
+    const byId = new Map();
+    for (const n of tree.nodes) byId.set(n.id, n);
+
+    const seen = new Set();
+    for (const node of tree.nodes) {
+      if (HIDDEN_ROLES.has(node.role)) continue;
+      seen.add(node.id);
+      const entry = ensure(node);
+      applyAria(entry.el, node, byId);
+      // Re-parent only when it actually changed: moving an element the reader
+      // is sitting on drops its cursor.
+      const host = hostNode(node, byId);
+      const parentEl = host ? (els.get(host.id) || {}).el : root;
+      const want = parentEl || root;
+      if (entry.el.parentNode !== want) want.appendChild(entry.el);
+    }
+
+    for (const [id, entry] of els) {
+      if (!seen.has(id)) {
+        entry.el.remove();
+        els.delete(id);
+      }
+    }
+
+    // `aria-describedby`, once every element exists: the message a field
+    // points at is usually built AFTER the field. The target gets a DOM id
+    // derived from its node id; the resolved `aria-description` is dropped
+    // when the reference resolves, or a reader would say the sentence twice.
+    // A reference to a node that is not in the mirror falls back to the text.
+    for (const node of tree.nodes) {
+      const entry = els.get(node.id);
+      if (!entry) continue;
+      const target = node.describedby ? els.get(node.describedby) : null;
+      if (target) {
+        const domId = "evg-a11y-" + String(node.describedby).replace(/[^A-Za-z0-9_-]/g, "_");
+        if (target.el.id !== domId) target.el.id = domId;
+        setAttr(entry.el, "aria-describedby", domId);
+        setAttr(entry.el, "aria-description", null);
+      } else {
+        setAttr(entry.el, "aria-describedby", null);
+      }
+      // `aria-controls` and `aria-labelledby` resolve the same way: a tab
+      // names its panel, the panel is named by its tab. A reference to a node
+      // that is not in the mirror (an inactive panel) is left off rather than
+      // pointing at nothing, which axe reports as a broken reference.
+      for (const [key, attr] of [["controls", "aria-controls"], ["labelledby", "aria-labelledby"]]) {
+        const ref = node[key];
+        const to = ref ? els.get(ref) : null;
+        if (to) {
+          const domId = "evg-a11y-" + String(ref).replace(/[^A-Za-z0-9_-]/g, "_");
+          if (to.el.id !== domId) to.el.id = domId;
+          setAttr(entry.el, attr, domId);
+        } else {
+          setAttr(entry.el, attr, null);
+        }
+      }
+    }
+
+    applyModal(tree, byId);
+
+    // Roving tabindex: exactly one element in the whole mirror is tabbable, and
+    // it is the one the app says has focus. With every focusable a tab stop
+    // the app's focus is still followed, only nothing is taken away.
+    if (tabbable !== "all" && tree.focus !== lastFocus) {
+      const prev = lastFocus ? els.get(lastFocus) : null;
+      if (prev) prev.el.tabIndex = -1;
+    }
+    const focused = tree.focus ? els.get(tree.focus) : null;
+    if (focused) {
+      if (tabbable !== "all") focused.el.tabIndex = 0;
+      // `canMoveFocus` is how a host that parks the keyboard somewhere else —
+      // a text-input bridge editing in its own transparent <input> — says so.
+      // The tab stop still moves; only the `.focus()` is withheld, because two
+      // elements calling `.focus()` for one field take it off each other.
+      if (document.activeElement !== focused.el && (!canMoveFocus || canMoveFocus(focused.node))) {
+        settingFocus = true;
+        try {
+          focused.el.focus({ preventScroll: true });
+        } finally {
+          settingFocus = false;
+        }
+      }
+    }
+    lastFocus = tree.focus;
+
+    // THE WAY IN. An app that has not been touched yet has nothing focused,
+    // and a roving tabindex read literally then makes NO element tabbable —
+    // so Tab walks straight past the whole widget and there is no way to reach
+    // it from the keyboard at all. That is not the roving pattern; a roving
+    // pattern always has one tab stop, and before anything is chosen it is the
+    // first focusable node. Once the app names a focus this does nothing.
+    if (tabbable !== "all") {
+      if (!focused) {
+        if (entryStop && (!entryStop.isConnected || entryStop.tabIndex !== 0)) entryStop = null;
+        if (!entryStop) {
+          for (const node of tree.nodes) {
+            if (!node.focusable || node.disabled) continue;
+            const entry = els.get(node.id);
+            if (!entry) continue;
+            entry.el.tabIndex = 0;
+            entryStop = entry.el;
+            break;
+          }
+        }
+      } else if (entryStop) {
+        if (entryStop !== focused.el && entryStop.isConnected) entryStop.tabIndex = -1;
+        entryStop = null;
+      }
+    }
+
+    return { nodes: tree.nodes.length, elements: els.size, gen: tree.gen };
+  }
+
+  function destroy() {
+    root.remove();
+    els.clear();
+    if (canvas) canvas.removeAttribute("aria-hidden");
+  }
+
+  // Focus that moved on its own — Tab, or a reader's cursor — is reported.
+  // The app's own `.focus()` above is not: `settingFocus` is what tells them
+  // apart, and a mirror that reported its own focus back would loop with the
+  // app that is setting it.
+  root.addEventListener("focusin", (ev) => {
+    if (settingFocus || !onFocus) return;
+    const el = ev.target && ev.target.closest ? ev.target.closest("[data-a11y-id]") : null;
+    if (!el) return;
+    const entry = els.get(el.dataset.a11yId);
+    if (entry) onFocus(entry.node);
+  });
+
+  root.setAttribute("aria-label", label);
+  return {
+    root,
+    update,
+    destroy,
+    /** The element a node is mirrored as, or null — the bridge edits in it. */
+    elementOf(id) {
+      const entry = els.get(id);
+      return entry ? entry.el : null;
+    },
+    get size() {
+      return els.size;
+    },
+    isSettingFocus() {
+      return settingFocus;
+    },
+  };
+}
+
+/** The default answer to "a reader pressed this": press the app where it is.
+ *  No mapping table, and nothing to keep in step with the app's own commands. */
+export function pressAtCentre(node, press) {
+  const b = node.b || [0, 0, 0, 0];
+  const cx = Math.round(b[0] + b[2] / 2);
+  const cy = Math.round(b[1] + b[3] / 2);
+  press(cx, cy);
+}