Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More →
chart2music
Advanced tools
chart2music - npm Package Versions
julianna-langston
published 1.3.0 • Changelog
1.3.0
- New feature: Add support for logarithmic axes
- New feature: Support passing custom hotkeys
- New feature: Support assigning focus to a specific data point in a chart when resetting the data/contents of that chart
julianna-langston
published 1.2.0 • Changelog
1.2.0
- New experimental feature: Add support for mobile interactions
julianna-langston
published 1.1.0 • Changelog
1.1.0
- New feature: the Options dialog. This allows end-users to control the hertz range of their sonification.
- Added a warning message when a user presses "M" on a non-live chart. If a user presses "M" on a live chart, that begins "Monitor" mode, where newly-added data is automatically played. However, if the user press "M" on a chart that isn't live, they will be told as much, so that the end-user doesn't get confused when no data is being updated.
julianna-langston
published 1.0.6 • Changelog
1.0.6
- Remove all notes below 55 Hertz, as many speakers have difficulty playing those notes.
julianna-langston
published 1.0.5 • Changelog
1.0.5
- Force a
roleattribute on chart elements if they don't already have one. This fixes a bug where firefox wouldn't read thearia-labelattribute on chart elements.
julianna-langston
published 1.0.3 • Changelog
1.0.3
- Fix bug where multiple instances of Chart2Music on the same page sharing the same CC element could cause the screen reader to stop reading text.
julianna-langston
published 1.0.2 • Changelog
1.0.2
- Refined support for multiple charts on a page using the same CC element. While this behavior previously worked for screen reader users, the content of the CC element wasn't clearing properly when switching between charts. This resulted in excess text in the CC element, which made debugging confusing.
julianna-langston
published 1.0.1 • Changelog
1.0.1
- Add support for missing y-values. In the cases of missing values (any data that is NaN), no sound plays, and the screen reader will say that the value is missing.
- Add support for out-of-bounds values. Out-of-bounds values occur when the report author explicitly sets a minimum or maximum for an axis, but also provides data that goes beyond those limits. In thhese cases, no sound plays, and the screen reader will say that the value is too low or too high.