You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Per this HN post, terminal charting can be challenging with respect to accessibility. Capturing some ideas for paths of work:
Add guidelines to the README with respect to accessibility, so devs may be aware of the issues.
Introduce alternative rendering modes, controlled by environment variables:
NTCHARTS_BLANK so users with screen readers will have blank canvas rendering
NTCHARTS_ALT with an experience / output appropriate for a screen reader or other devices?
Would have to be chart dependent... e.g. meters/guages could emit their value, but what for a line chart?
Send some rendered representation of the data to an LLM which summarizes it and renders descriptive text? This is an example where assistive features could also help other users.
How would this interact with BubbleTea, focus, event loops, etc.
The text was updated successfully, but these errors were encountered:
Per this HN post, terminal charting can be challenging with respect to accessibility. Capturing some ideas for paths of work:
Add guidelines to the README with respect to accessibility, so devs may be aware of the issues.
Introduce alternative rendering modes, controlled by environment variables:
NTCHARTS_BLANK
so users with screen readers will have blank canvas renderingNTCHARTS_ALT
with an experience / output appropriate for a screen reader or other devices?Would have to be chart dependent... e.g. meters/guages could emit their value, but what for a line chart?
Send some rendered representation of the data to an LLM which summarizes it and renders descriptive text? This is an example where assistive features could also help other users.
How would this interact with BubbleTea, focus, event loops, etc.
The text was updated successfully, but these errors were encountered: