@pie-players/pie-tool-answer-eliminator 1.0.0-beta.7 → 1.0.0-beta.9

package/README.md

@@ -82,7 +82,7 @@ For a custom layout inside the toolkit. The tool detects choices under the item
 
 ## Props/Attributes
 
-`elementStateKeys` is a JS property only; the others also take the attribute shown.
+`elementStateKeys` and `elementIds` are JS properties only; the others also take the attribute shown.
 
 | Property | Attribute | Type | Default | Description |
 |----------|-----------|------|---------|-------------|
@@ -91,6 +91,7 @@ For a custom layout inside the toolkit. The tool detects choices under the item
 | `strategy` | `strategy` | `'strikethrough' \| 'mask'` | `'strikethrough'` | Elimination styling; any other value uses `strikethrough` |
 | `buttonAlignment` | `button-alignment` | `'start' \| 'end' \| 'inline'` | `'inline'` | Toggle placement: `inline` in the flow after the choice, or `start`/`end` beside it, resolved against the choice's own direction so they mirror under right-to-left content. `left` and `right` are aliases of `start` and `end`; any other value is `inline` |
 | `elementStateKeys` | | `Record<string, string>` | `{}` | Composite key `assessmentId:sectionId:attemptId:itemId:elementId` per PIE element, by model id, into the runtime context's element tool state store. A choice is tracked under its nearest ancestor with a listed id and persists under that key; choices outside a listed element are kept in memory only |
+| `elementIds` | | `string[]` | unset | Model ids of the PIE elements whose choices take a toggle; unset, every element's do. A choice belongs to an element when that element or one of its ancestors up to the item has a listed id. The toolbar sets it from the host's element list |
 
 ## Global Element ID Format
 
@@ -223,6 +224,22 @@ The outermost declaring element under the item owns its subtree: an element comp
 
 Elements that declare nothing fall back to the multiple-choice and EBSR markup this package reads (`.corespring-checkbox` and `.corespring-radio-button` choices, and the `ebsr-multiple-choice` parts with ids `a` and `b`). That fallback serves legacy pie-elements and pie-elements-ng releases from before elements declared their supports, and never runs inside a declaring element.
 
+### Host element list
+
+A host limits the eliminator to the elements whose support it has vetted, by package name, in the tool's provider entry:
+
+```typescript
+new ToolkitCoordinator({
+  tools: {
+    providers: {
+      answerEliminator: { elements: ['multiple-choice', 'ebsr'] },
+    },
+  },
+});
+```
+
+A name is the `<name>` of `@pie-element/<name>`, matched against the package the item's `elements` map binds a model's tag to, or, for a tag the map does not bind, against the tag with its version suffix and `pie-`/`pie-element-` prefix removed. A tag bound to a package outside `@pie-element` matches no name. A listed element must still support answer masking. The toolbar withdraws the eliminator from an item with no listed element, even under a PNP grant, and in a mixed item gives toggles only to the listed elements' choices. Omitting `elements` keeps every supporting element; an empty list allows none. A value that is not a list of names fails config validation and, under `toolConfigStrictness: "warn"` or `"off"`, allows none.
+
 ### 2. State Storage
 
 Eliminated choices are stored by choice ID:
@@ -257,7 +274,7 @@ Only MathJax containers are marked: natively rendered MathML keeps real text in
 
 All three treatments — the text line-through, the diagonals over an image, the line over math — are drawn in one color, `--pie-answer-eliminator-strike-color` (a registered `component-public` token, defaulting to `--pie-incorrect`), so a choice mixing prose, pictures, and math reads as a single strike and can be restyled from one place.
 
-For browsers without the Highlight API, each strategy falls back to a class on the choice container. Either way the eliminated choice also receives ARIA hooks (`data-pie-answer-eliminated`, plus `aria-disabled`/`aria-hidden` and an offscreen "(eliminated)" announcement) for assistive technology.
+For browsers without the Highlight API, each strategy falls back to a class on the choice container. Either way the eliminated choice also receives ARIA hooks (`data-pie-answer-eliminated`, `aria-disabled`, and an offscreen "(eliminated)" announcement in the interface language) for assistive technology. The choice container is never `aria-hidden` — it hosts the strategy's toggle, which must stay reachable for screen-reader and keyboard users (WCAG 4.1.2).
 
 ### 4. Toggle Behavior
 

package/custom-elements.json

@@ -7,7 +7,7 @@
 			"declarations": [
 				{
 					"kind": "class",
-					"description": "Process-of-elimination tool for the item in its enclosing `<pie-item-scope>`: it adds a toggle beside each choice an element supplies for `answer-masking` that strikes the choice through or masks it, per `strategy`. It renders nothing of its own and is active while `visible` or `always-on` is set. Eliminations persist in the runtime context's element tool state store, under the key `elementStateKeys` gives each PIE element.",
+					"description": "Process-of-elimination tool for the item in its enclosing `<pie-item-scope>`: it adds a toggle beside each choice an element supplies for `answer-masking` that strikes the choice through or masks it, per `strategy`. It renders nothing of its own and is active while `visible` or `always-on` is set; `elementIds` limits the toggles to those elements' choices. Eliminations persist in the runtime context's element tool state store, under the key `elementStateKeys` gives each PIE element.",
 					"name": "ToolAnswerEliminator",
 					"tagName": "pie-tool-answer-eliminator",
 					"customElement": true,
@@ -58,6 +58,15 @@
 							"default": "{}",
 							"description": "Store key per PIE element, by model id (JS property only)",
 							"attribute": "elementstatekeys"
+						},
+						{
+							"kind": "field",
+							"name": "elementIds",
+							"type": {
+								"text": "readonly string[]"
+							},
+							"description": "Model ids of the PIE elements whose choices take a toggle. Unset, every element's choices do.",
+							"attribute": "elementids"
 						}
 					],
 					"attributes": [
@@ -102,6 +111,14 @@
 							"default": "{}",
 							"description": "Store key per PIE element, by model id (JS property only)",
 							"fieldName": "elementStateKeys"
+						},
+						{
+							"name": "elementids",
+							"type": {
+								"text": "readonly string[]"
+							},
+							"description": "Model ids of the PIE elements whose choices take a toggle. Unset, every element's choices do.",
+							"fieldName": "elementIds"
 						}
 					],
 					"cssProperties": [

package/dist/element-props.d.ts

@@ -10,4 +10,9 @@ export interface AnswerEliminatorProps {
     alwaysOn?: boolean;
     buttonAlignment?: 'start' | 'end' | 'inline' | 'left' | 'right';
     elementStateKeys?: ElementStateKeys;
+    /**
+     * Model ids of the PIE elements whose choices take a toggle. Unset, every
+     * element's choices do.
+     */
+    elementIds?: readonly string[];
 }