[iOS][Accessibility ] [Focus is not going to the first accessibility element]

[jyoti-ms]

Platform

What platform is your issue or question related to?

• iOS

Author or host

Teams Mobile Client

Version of SDK

SDK version 2.1.0 (ACv1.3)

Details

When there are errors on the cards after pressing submit action, focus is not going to the first accessibility element (input field) on the card that has error message. Link to video

[ghost]

please review this issue for target Milestone, Inconsistencies & Priority upon triage.

[ghost]

Hi @jyoti-ms. We have acknowledged this issue report. Please continue to follow this issue for updates/progress/questions.

[shalinijoshi19]

@jwoo-msft assigning to you for initial investigation. Pls update once we do have an action plan for this. Thanks

[jwoo-msft]

Hello @jyoti-ms,

Can you be more specific about what's the issue here? If there is an error, the focus will be set on the first input item with an error. For example, if it's input.text, the focus will be set on the input.text and open up a keyboard.

[ghost]

Hello @jyoti-ms! We need some additional information from you to process this issue. Please see discussion comments above. Thanks!

[jyoti-ms]

@jwoo-msft When user clicks on submit button and if there is an error then, the view is getting scrolled and focus is not going to the first input that has errors.
Focus is going out of the adaptive card's view when voice over is on (on input validation).

This is happening whenever layout of the superview is changed due to errors.
Can you please take a look at the video once? Link to video Do let me know if you need more info on this.

[ghost]

Thanks @jyoti-ms for following up on this issue. A member of our triage crew will re-engage as soon as possible to follow up. Thanks.

[jyoti-ms]

@jwoo-msft This issue can be fixed only when action type is known to me on layout change notification.

Scenario - Currently layout change notification is sent to the host on button click(Action.ShowCard, Action.Submit, Action.ToggleVisibility). The host would need to have different layout change functions (teams client) based on the type of the action.
So if we have action.submit layout update call, then we can avoid performing reloadRows (because of this we are losing focus) we only need to update the height of the cell and changing the button state.
Can you please confirm on this if this is possible to provide action type and button ref on layout change notification?

Thanks!
cc:@sowrabh-msft @shalinijoshi19

[ghost]

🎉This issue is now fixed by #4944 and successfully released as part of our AdaptiveCards@2020.10 offering.:tada:

Handy links:

• Release Notes
• AdaptiveCards Website
• Official NPM Designer Release
• Official NPM Templating Release
• Official NPM Renderer Release
• Official Nuget Templating Release
• Official Nuget Renderer Release
• Official Maven Renderer Release
• Official CocoaPod Renderer Release

[ghost]

🎉AdaptiveCards@2020.10 has been released which fixes this issue.:tada:

Handy links:

• Release Notes
• AdaptiveCards Website
• Official NPM Designer Release
• Official NPM Templating Release
• Official NPM Renderer Release
• Official Nuget Templating Release
• Official Nuget Renderer Release
• Official Maven Renderer Release
• Official CocoaPod Renderer Release