Disable mandatory a11y hint

[ceceppa]

Description

Accessibility hint should be provided only when the results of an action are not evident from the element’s label.

Fixes #142

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Checklist: (Feel free to delete this section upon completion)

• I have included a changeset if this change will require a version change to one of the packages.
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have run all builds, tests, and linting and all checks pass
• I have added tests that prove my fix is effective or that my feature works
• My changes generate no new warnings
• Any dependent changes have been merged and published in downstream modules

[carbonrobot]

Would it better to modify the code so that it only applies to the correct places instead of disabling it entirely?

https://github.com/FormidableLabs/eslint-plugin-react-native-a11y/blob/master/src/rules/has-accessibility-hint.js

[ceceppa]

Would it better to modify the code so that it only applies to the correct places instead of disabling it entirely?

https://github.com/FormidableLabs/eslint-plugin-react-native-a11y/blob/master/src/rules/has-accessibility-hint.js

AFAIK, There are no "correct places" where an accessibility hint is needed. Even for the Pressable, the hint should be used rarely and depends on the app itself.
We can't safely suggest when it should be used. So, we either turn it off or remove that rule entirely.

[carbonrobot]

Can you add a changeset for a patch using yarn changeset? Then we can merge and leave it disabled. If someone finds a way to target in the future we still have the code to modify.