[Interactive Graph] POC custom point names for screen reader accessibility#3387
[Interactive Graph] POC custom point names for screen reader accessibility#3387
Conversation
… custom point names for screen reader accessibility
npm Snapshot: PublishedGood news!! We've packaged up the latest commit from this PR (abb6572) and published it to npm. You Example: pnpm add @khanacademy/perseus@PR3387If you are working in Khan Academy's frontend, you can run the below command. ./dev/tools/bump_perseus_version.ts -t PR3387If you are working in Khan Academy's webapp, you can run the below command. ./dev/tools/bump_perseus_version.js -t PR3387 |
🗄️ Schema Change: Changes Detected
|
🛠️ Item Splitting: Changes Detected
|
|
Size Change: +383 B (+0.08%) Total Size: 487 kB
ℹ️ View Unchanged
|
Summary:
Problem
When a content author writes a question like "Move Point T to coordinates (3, 4)", the screen reader reads the point as "Point 1" instead of "Point T", creating a confusing disconnect for visually impaired users.
Changes
Data layer (perseus-core):
Rendering (perseus):
Editor (perseus-editor):
Design decisions
Notes
This is a proof of concept. See
interactive-graph-custom-points.mdfor full investigation notes, architecture decisions, remaining work (tests to write, edge cases), and future scope.Issue: LEMS-XXXX
Co-Authored by Claude Code (Opus)