Pagination Accessibility Improvements

department-of-veterans-affairs / va-mobile-app

"If VA were a company, it would have a flagship mobile app."

https://department-of-veterans-affairs.github.io/va-mobile-app/

17 stars 2 forks source link

Pagination Accessibility Improvements #4627

Open dumathane opened 1 year ago

dumathane commented 1 year ago

Description

As an app user, I want to all parts of the VA Mobile App to be intentionally accessible, so that veterans requiring advanced accessibility standards have their needs met.

As part of this story we want to:

Review the current accessibility setup of the Pagination component.
Identify if any improvements can/should be made.
If improvements are identified create an engineering ticket to implement the Pagination component changes.

Acceptance Criteria

- [ ] Artifact of Accessibility suggestions. - [ ] FE Engineering ticket created and linked here. ## Notes & Open Questions - Dependencies/Roadblocks: - Any internal/external dependencies? - Test accounts needed? - Does this require QA? - Dev Notes: ## Ticket Checklist - [ ] Acceptance criteria defined - [ ] Labels added (front-end, back-end, feature) - [ ] Linked to an Epic

brea11y commented 4 months ago

Since this ticket is over a year old, I am unsure if this is still needed. Adam has asked that I unassign myself for now. If this work is still needed, please reassign and work with Adam to get this work prioritized.

TKDickson commented 4 months ago

@brea11y a purpose of this ticket could be to do the work to unblock ticket #4683. (Idk if that was the original intent, but that ticket is blocked awaiting accessibility decisions around pagination so........ seems reasonable)

The outstanding questions from that ticket are well summarized in the last comment added.

brea11y commented 4 months ago

@TKDickson – That actually makes a ton of sense. Thanks so much for linking me to that other ticket. I'd definitely think we have enough information to look into this and see if we can improve it in any way. My guess is that we may have to coordinate with the design system team to see if this is something that they'll be moving over there at some point in the future. If so, we could coordinate with them to complete this then, but if not, we could pull this in at anytime.

@jessicawoodin do you know if the pagination component is one that you guys will be bringing into the design system in the future or will that always be a Flagship-specific component?

jessicawoodin commented 4 months ago

Yup, Pagination is on our list, but it's currently 23rd in line, so it might be a while. I wouldn't recommend waiting for us on this one.

brea11y commented 4 months ago

Perfect! That is great to know. With that being said, I'll move this over into the backlog/ready to work column so we can go ahead and get started on this since it has been sitting for so long. If we can make any improvements, we can then pass that on to the design system when they begin their work on the component.