Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
We’re working on making the filters on edX.org vertical and are running into space constraints. What is the best approach to shrinking each checkbox input?
Notes:
There are concerns about going smaller than 24x24px for the hit area of the checkbox
Try reducing padding between checkboxes before making the checkbox smaller
10 minutes
Accessibility considerations for Expandable Input Groups
Harper Wentz
Some of our filtering options on edx.org have as many as 100 options. For example the Partner field could have many Schools and Companies that offer learning products. We want to ask what is the best approach for making these lists accessible?
If we display the partners with the most results (instead of displaying them in alphabetical order) how should we indicate this to screen readers?
Notes:
We should what auditors will do, a blind user for instance will click on the “show more”, should be an explicit click on the “show more”
10 minutes
vertical variant for Stepper
@Vladyslav Zadorozhnii
In the 2U MFE Studio project there is a task to rewrite this component to React.
And they wanted to use stepper but there is no vertical variant for this. Should we customize stepper component to support vertical variant? Something like this:
Notes:
Disabled should use low contrast text
Should not use color alone to represent state
Needs some design thinking for the component
Some pushback on the component usage/use case, consider stateful functionality
