Accessibility and the Carousel Block

I have have a peer who is blind and I asked if he could go through a test file in RISE with just the Carousel block. I was struggling to figure out which instructions I need to write to move through the carousel to be accessible not fully know what a screen reader reads out.

I received the following feedback from him and was wondering since I can't make any changes to alt text of the arrows is this something Articulate could make a priority fix. and curious if others have thoughts or recommendations on how you introduce a carousel to your learners to be inclusive.

Here are his thoughts that I thought could be helpful to Artriculate product team for improving for accessibility.

"When I navigate through that slide, I hear things like "Slide X of Y" and "Go to previous slide" > "Go to next slide."

It's all pretty clear to me.

[The issue is]... its focus management means I have to do extra work to know precisely where I am at (it doesn't automatically focus the new slide's content).

It also seems to put the carousel and slide controls above the associated content. So it means selecting Next, navigating down, then  having to go back up to the controls to get to the Next button again.

The preferred pattern would be to place the controls at the bottom. When the user clicks Next, focus would be set to the heading at the top of the carousel. Then when they reached the bottom of the content, they'd get the controls again."

I just wanted to share in case Articulate staff can forward this to a product team member.

This was the example I shared: 

https://360.articulate.com/review/content/e419c690-0c39-4009-b237-67fbeab9d2c0/review