[iOS] Accessibility testing

We must accurate which scenarios or views must be tested in terms of accessibility.

Which scenarios must be tested

• Check bookmark list: all info about in the list is correctly spelt
• Add bookmark: Everything OK in the moment of adding new bookmark
• Check Settings: Enable and disable passcode, so security is assured (should everything here be tested every time?)
• File list:
  • open folder (browse)
  • open&close card, and check that all items in the card are spelt, so that all actions are accessible
  • download&open file
  • Upload content
• Quick access: check browsing and spelling of all items

Which is the app/feature with which all accessibility labels are overlayed? this is an important test so it allows to check at a glance if everything has accessibility label.

When accessibility must be checked

• Every scenario tested in regression stage, just before releasing a new version
• Every PR that contains any new UI component must include accessibility labelling, so, test must be included in the feature test plan or QA checks.

This is an open discussion to add/modify/remove scenarios, so feedback about the most important ones for final users would be welcome. Test strategy is also open to discussion.

@michaelstingl @hosy

Review the listed iOS scenarios—bookmarks, settings, file lists, and quick access—and the proposed regression and feature test-plan checks. Determine which accessibility labels and user flows need coverage, then document an agreed scenario list and when each check is required.