Description
Summary
We presently support assistive technology (AT) users with the action-bar
component for the collapse/expand buttons.
However, the support also provides the same context visually updating the text, which in some use cases doesn't provide a good interface, or user experience for visual users.
Could we support both AT and visual users in providing opportunities to support both use cases?
Actual Behavior
When setting the intlCollapse
property the visual text and label contain the value.
Expected Behavior
Developers should be able to specify different values for the action-bar
collapse button with the displayed text (perhaps new props, textCollapse
/textExpand
versus what is read by AT intlCollapse
/intlExpand
)?
For instance, visual users may only need displayed text of "Collapse", whereas additional context is needed to support AT users, such as "Collapse accordion sample menu bar".
Reproduction Sample
https://codepen.io/geospatialem/pen/Jjvgrqv
Reproduction Steps
- Open the sample
- Observe when supplied with the
intlCollapse
prop the "Collapse" text is replaced with the value (e.g., "Collapse accordion sample menu bar").
Reproduction Version
beta.95
Working W3C Example/Tutorial
No response
Relevant Info
There may still be a use case for allowing the developer to change the visual text, so perhaps a new property should be introduced to account for both the accessible label (intlCollapse
/intlExpand
and text (perhaps textCollapse
/textExpand
)?
Additional background:
- A sample with a native button that is supplied with different visual text and an accessible label for context.
- Many other CC have similar options, such as Loader where
label
andtext
properties co-exist on the component.
Regression?
No response
Esri team
Calcite (dev)