Forum Xamarin.Forms

Xamarin Forms - Accessibility ordering when CarouselView control is used in a ContentPage (iOS)

skadookkunnanskadookkunnan Member ✭✭
edited September 2020 in Xamarin.Forms

Again another question on the Accessibility! In my project, I have a page where it contains elements in the following structure,

<ContentPage>
    <StackLayout>
        <StackLayout Orientation=Horizontal />  // Contains 3 elements.
        <CarouselView />                        // Usually contain minimum 3 elements (a single element in the CarouselView fits the entire page).
        <Grid />                                // Contains 3 elements.
    <StackLayout>
</ContentPage>

For a disabled/accessibility user, we would like to have the option of navigating between the elements in a page by swiping right and left respectively. We have used the TabIndex property of the VisualElement to order the elements so that on swiping left and right the accessibility focus switches properly.

However, with the CarouselView present, the navigation does not work properly based on the ordering given. Once the focus goes to the CarouselView elements, it keeps continuing to the other views/pages in the CarouselView (this happens only in iOS, whereas Android correctly switches the focus to the Grid elements). According to the standards of Accessibility, the right/left swipe should not take the user to a context other than the current page elements.

Is there a way to make the ordering to switch properly from CarouselView's first view to the Grid elements in iOS?

Any help on this is highly appreciated.

Sincerely,
Sagar S. Kadookkunnan

Answers

  • ColeXColeX Member, Xamarin Team Xamurai
    edited September 2020

    I think the navigation swipe and CarouselView swipe are in conflict , TabIndex is not supported on CarouselView .

    Check the following controls which TabIndex is supported

    • Button
    • DatePicker
    • Editor
    • Entry
    • NavigationPage
    • Picker
    • ProgressBar
    • SearchBar
    • Slider
    • Stepper
    • Switch
    • TabbedPage
    • TimePicker

    Refer to

    https://docs.microsoft.com/en-us/xamarin/xamarin-forms/app-fundamentals/accessibility/keyboard#supported-controls

  • Was the issue related to Carousel view accessibilty resolved? Is there any workaround?
  • skadookkunnanskadookkunnan Member ✭✭

    Hi @Ponnu,

    We could not find a workaround to this issue yet. So we have parked this, for now, to work on other priorities. Will update this thread once we are back on this and figure out something to make it work.

    Sincerely,
    Sagar S. Kadookkunnan

  • JohnHardmanJohnHardman GBUniversity admin

    @skadookkunnan said:
    Hi @Ponnu,

    We could not find a workaround to this issue yet. So we have parked this, for now, to work on other priorities. Will update this thread once we are back on this and figure out something to make it work.

    You might want to add details of your scenarios to the GitHub enhancement request at https://github.com/xamarin/Xamarin.Forms/issues/13006 or to one of the other accessibility order related issues in the GitHub repo. Accessibility doesn't really seem to be something many people at Xamarin know much about, so the more people adding their requirements the better. On the plus side, accessibility did finally get a mention in the latest Xamarin survey, so it is finally on the radar at least.

  • @skadookkunnan Thank you for the update.

Sign In or Register to comment.