Accessibility fixes

[miguelbcr]

Ticket

This PR fixes the issues detected by the Accessibility Scanner App and I have also run the TalkBack App to check how it is talked.

ℹ️ I've created the files accessibility-strings.xml, in both, showcase module and for the SDK itself (core.ui module). Currently I've added only english translations (@chemarubio @VictorAlbertos could you please review the copy), but we would need also translations for the languages we support, currently en and de.

Usage example of Accessibility Scanner App

1	2

Video example

accesibility-scanner.mp4

[chemarubio]

We might need a German translation for the talk back to handle this

[VictorAlbertos]

all these copies needs to be verified by translators, let's see how we can make accessibility copies part of the translation process 👍

[VictorAlbertos]

Do you know @miguelbcr if google has some kind "on the fly" ML models to "read" the content of dynamic images (not only UI resources)?

[miguelbcr]

I initially filled that contentDescription with the title of the card, detail page,... but I removed it eventually because I though it was not needed to repeat the same content description when using TalkBack.

Looking at the doc it says:

so I think for our case is not needed because the image always goes with a text...

The ways of testing or analyzing it are the ones described here https://developer.android.com/guide/topics/ui/accessibility/testing. I used the two first ones (TalkBack and Accessibility Scanner)

Also in some cases I use .semantics(mergeDescendants = true) {} to let some widgets to use the same text in one child within the parent, for example a card containing image and text.

[VictorAlbertos]

I see, thanks for the clarification!

[VictorAlbertos]

Thanks Miguel 🚀

[chemarubio]

🚀 great ! Maybe some linter issues need to be addressed before merging.