In our first iteration, the keyboard accessory should blend in with the keyboard. A drawback is that it's unclear that the accessory and its suggestions originate from Chrome (which is a trusted, unsurprising source for these suggestions).

To address this ambiguity:
1. Apply the clean white layout that used all over Chrome (e.g. in the Omnibox, the bottom bar, infobars, etc.) as tracked in issue 911084.

2. Add in-product help that shows the purpose and source of suggestions to new users.

3. Consider a First-Run Experience to hint to the feature (e.g. the hint-sheet that was overlaying the keyboard in mocks).



For SEO: Previously, this was referred to as user education. To make it consistent with other documents and names used in code, I mainly use IPH (In-Product Help).