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
Is your feature request related to a problem? Please describe
For users using non-traditional means of navigation through a11y tools, the h1 element is considered the title of the page. When users open storybook, what is considered the title? Is it the current element that is open?
Currently, the element that appears as the h1 header is an invisible error
Describe the solution you'd like
I'd like to see a header at the top of the page with the name of the chosen element and/or access tree (ex Basics < Document Formatting < With Markdown) so the purpose/content of the open webpage is immediately apparent.
Is your feature request related to a problem? Please describe
For users using non-traditional means of navigation through a11y tools, the
h1
element is considered the title of the page. When users open storybook, what is considered the title? Is it the current element that is open?Currently, the element that appears as the
h1
header is an invisible errorDescribe the solution you'd like
I'd like to see a header at the top of the page with the name of the chosen element and/or access tree (ex Basics < Document Formatting < With Markdown) so the purpose/content of the open webpage is immediately apparent.
Describe alternatives you've considered
To maintain visual clarity, an
h1
that is only present for screenreader users could be usedhttps://webaim.org/techniques/css/invisiblecontent/
Are you able to assist to bring the feature to reality?
yes, I can
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: