Some view items are not useful when navigating with a screen reader, and we do not necessarily want to add content descriptions that would make navigation frustrating.

Deliverables

• Are there best practices in the accessibility community for handling this? Document these practices and file issues for fixing in our app.

We currently implement createLogin() in a number of places. It would be nice to refactor this to a single place that can be shared everywhere as a utility function.

SearchSuggestionsPromptView is not always displayed during tests as seen in screenshots, which causes both the enable and disable tests to fail.

Test Failure

t =    42.16s Assertion Failure: SearchSuggestionsTest.swift:89: Failed to find "SearchSuggestionsPromptView" Other after 30 seconds.
t =    42.19s Assertion Failure: BaseTestCase.swift:53: Asynchronous wait failed: Exceeded ti

We're having a mix of named function syntax (old style) and non-named function syntax (new style) in our internal JavaScript.

The old style was mostly there for JS stack traces before they were as nice as what we have now. Since that's solved, having named functions has become unnecessary and will just take up JS data space when processing.

We should convert all named function syntax in JSO