Right now we have icons in the contentBefore/contentAfter story that don't have labels but also aren't hidden (the examples kind of look like search box variants). https://fluentuipr.z22.web.core.windows.net/heads/master/react-components/storybook/index.html?path=/docs/components-input--default#content-before-after

This is not an accessible appropriate and therefore probably not something we should demonstrate, but it's not clear what to do instead.

It's also extremely unclear in general how contentBefore/After should be associated with the field in an accessible way, which is a further reason that the example should demonstrate a good pattern (or at least "less bad").

Some ideas:

• Make it "more realistic": give the icons labels and maybe add type=search? But in this case it's weird that the icons don't have associated actions, and it doesn't solve the association problem.
• Use different icons that don't imply anything, and make them aria-hidden? But then why are there icons at all?
• Add a full search box pattern example, possibly in addition to a meaningless hidden before/after icons example?

cc @smhigley