Source-verified skills for the Charm terminal stack: Bubble Tea v2, Bubbles v2, Lip Gloss v2, Huh v2, Log v2, Glamour v2, plus the gum and vhs CLIs.
100
100%
Does it follow best practices?
Impact
100%
1.02xAverage score across 9 eval scenarios
Passed
No findings from the security scan
How Huh v2.0.3 decides on accessible mode, and where it behaves differently from the TUI.
form.WithAccessible(true) swaps the TUI for plain line based prompts that
screen readers handle.
NewForm switches accessible mode on when TERM is dumb, and any later
WithAccessible call replaces that decision. So
WithAccessible(os.Getenv("ACCESSIBLE") != "") turns it back off on a dumb
terminal whenever the variable is unset. Honor the common ACCESSIBLE
convention without losing the default by only calling WithAccessible when
the variable is present, as the
theme example
does with os.LookupEnv.
WithOutput(os.Stderr) to keep stdout for results in both modes.ErrTimeoutUnsupported).RunWithContext
and does not skip hidden groups. Check accessible behavior separately
when using conditional pages.Run discards field errors and returns nil: on EOF a prompt keeps its
default value and skips validation, and ErrUserAborted is never
returned. Validate the bound values after Run.The spinner has its own WithAccessible, mirroring the form.