VAMC story and news release pagination is not announced properly

[laflannery]

Describe the defect

On the VAMC Stories and News Releases pages, the search results are not properly announced to a non-visual user when using the pagination. This makes it difficult to fully understand the results.

To Reproduce

Steps to reproduce the behavior:

1. Go to a page on within the VAMC that has paging, like Boston news releases
2. Turn your screen reader on
3. Go to page 2 of the results list
4. Confirm that you are directed to the top of page 2 and "Current" is announced, instead of the number of new results on the page

Additional Context

• The search results should behave the same as the other searches throughout the VA.gov site (i.e Find a form, Resources and Support)
• It's interesting that these listings don't have a "Showing X - XX of XXX results" at the top of the listing. If this was present we could send focus to this as we do on the PW listings. Is there a product reason we don't do this or could this be added?

AC / Expected behavior

• Update search results to announce new results on the page.
• Accessibility review
• Platform sister issue (#64843) should be closed when this work is done.

[eselkin]

I think the current here is related to jumping to the content immediately. In form search it jumps (when you click page 2) to the next set of form items. In the event, story, news release the page 2 jumps to the top of the screen and does not announce the next items until you tab your way down the page a bit.

So I guess this is still reproducible.

[randimays]

Somewhat related defect that could use a look on the Facilities events page: #14737

[mmiddaugh]

Is this related to #12088?

[laflannery]

@mmiddaugh I think an engineer is going to have to answer this definitively but I feel like no - I think additional work has to go into this beyond just waiting for the DST to update their component class

[CherylEvans]

This ticket was recreated in va.gov-team repo Ticket # 64843

[xiongjaneg]

@xiongjaneg Remove this from V3 upgrade tickets

[Agile6MSkinner]

@laflannery to revaluate ACs

[laflannery]

@Agile6MSkinner This is all set, there is a product question in the "Additional Context" section that should probably be answered before this goes to the team for refinement. That being said, I will move this to Backlog until this is answered.