Haptics when interaction on components and navigations

[pylapp]

Context

Today with the incoming v0.13.0 we will have several components:

• navigation components with link (OUDSLink)
• input components with checkbox (OUDSCheckbox, OUDSCheckboxItem), radio ( OUDSRadio, OUDSRadioItem), switch (OUDSCheckbox, OUDSCheckboxItem)
• action components with button ( OUDSButton)

Some native components like the iOS Toggle have haptics returns, i.e. kind of vibrations when their state changes.

Issue

It could be interesting to use the same behavior of iOS Toggle for the OUDS Switch.
In addition, what should be the best practices for buttons, radio and checkboxes about haptics.

There is no documentation about such guidelines on a11y-guidelines.orange.com.

Nothing in iOS settings allows to know if some a11y feature related to haptics is enabled or not.

Uses cases

Use cases we have in mind:

1. notify the user there is an error
2. or notify the user somehting unexpected happened (like empty results for a search)
3. haptics during navigation (e.g. pull to refresh with haptics during pull and release)
4. haptics on toggle switch
5. haptics on checkbox or raido fill

@pya35 what do you think?
@afrahB and @Aniort what is your point of view for Android and web in most of cases?

[pylapp]

Maybe related to #582, closed has not relevant