Add description attributes to all app texts for sight impared a11y support

[andrewtavis]

Terms

• I have searched open and closed feature requests
• I agree to follow Scribe-Android's Code of Conduct

Description

As of now Scribe-Android and Scribe-Conjugate-Android are not written to allow sight impaired users to use them easily with a screen reader. This issue would add add the needed description attributes to getString() uses across the app such that the text can also be read to the user in their language.

This would be the first issue for this functionality, with a future discussion being where else in the application support for screen readers is needed.

Contribution

Happy to support this, review a PR and also discuss what other changes need to be made to support screen reader users!

[prince-0408]

Hi @andrewtavis,

I'd love to work on this issue! 🙋‍♂️

Since it's an important step toward sight-impaired accessibility, could you assign it to me and guide me on:

1. Which specific layout elements or navigation bars we should prioritize first.
2. The preferred naming conventions for these new accessibility i18n description keys.

I'm ready to dive in and get started under your guidance! 😊

[andrewtavis]

Thanks for your interest, @prince-0408! I think we can try to prioritize the menu options and tab bar first, and also look at the texts in the about tab submenus. Feel free to name them similar to our other i18n keys, where we'd use the page it's used on and a descriptor, but the descriptor in this case should end in _alt_text.