This will cover Case Search accessibility improvements beyond those mandated by WCAG. These will improve the accessibility of Case Search, but are not strictly required.
[ ] Add Information modal from prototype.
[ ] Ensure that combo boxes, when expanded, do not wrap the focus around to the top of the list when the user scrolls to the bottom, or vice versa. Arrow keys are a common way to close combo boxes, and having the focus wrap around to the bottom can make it hard to close them.
[ ] Ensure the focus indicator remains onscreen (by scrolling the viewport) when opening and scrolling through the Chapter combo box.
[ ] Consider changing the name of the Primary Navigation navigation landmark. Avoid using the type of landmark in the name of the landmark, it causes repetition for screen readers.
[ ] Implement a single-column layout for Case Search, for when the viewport needs to be rescaled up to 200%.
[ ] Ensure the Clear button on the Case Number search has a meaningful, programmatic label.
[ ] Ensure field groups are labeled such that screen readers don't read the same text redundantly. Avoid things like "Case Number Case Number" and "Chapter Chapter."
[ ] Ensure the search results section has a programmatically readable label.
[ ] Investigate how we might enforce certain reading behaviors of numbers by screen readers. For example, how do we ensure that "23-11883" is read as "two three dash one one eight eight three" and not "twenty-three to eleven thousand eight-hundred and eighty-three"?
[ ] Investigate how we might make masked text easier to parse by a screen reader. Currently, it ends up reading each individual X.
jharcey-flexion
commented
2 months ago
This will cover Case Search accessibility improvements beyond those mandated by WCAG. These will improve the accessibility of Case Search, but are not strictly required.