Carousel accessibility with PageControl

[jessegreenberg]

From phetsims/circuit-construction-kit-common#1124 -

We will need a structure that combines the PageControl into the carousel logically, so that the structure is intuitive for accessibility. This is what was done in CCK and we confirmed that it is the ideal structure.

For this structure, the accessibleName for the ComboBox should not create the heading. The heading needs to appear above the PageControl and should include all components (PageControl, Carousel and its previous/next buttons). And the aria-labelledby should point to this grouping heading.

When the Carousel does not include a PageControl, the heading structure should be as it is now with the following exception - the previous/next buttons should be moved under the heading of the carousel.

[jessegreenberg]

Requested by @terracoda on slack:

I am wondering if makes sense to have an option to put the pages after the carousel instead of before, since they see pretty optional.

I think this means the PageControl, add an option to put it after the previous/next buttons.

[terracoda]

Yes, that is what I was thinking. Depending on the designed order of the PDOM, it might be helpful to have the page controls after the Previous and Next buttons.

For example, in CCK the Construction Area comes before the Carousel, so a learner always has to Tab through the Pages toolbar to add a new component.

Wondering if putting the Pages toolbar after in this case would be beneficial when the area of interest is before the carousel, and before if the area of interest is after the carousel.

If this was flexible, one can choose to place the pages where the get in the way the least.

[terracoda]

This is an idea for a dev option if it is not a heavy lift.
There is already an option to not include the Page Controls at all, so that remains a choice fro sim teams.