FormidableLabs / FormidableLabs/eslint-plugin-react-native-a11y

why is the accessibilityHint enforced as mandatory?

Open
#142 3 comments 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
306
Forks
29
PR merge metrics
No merged PRs in 30d

Description

From your [documentation](https://github.com/FormidableLabs/eslint-plugin-react-native-a11y/blob/HEAD/docs/rules/has-accessibility-hint.md)

"An accessibility hint helps users understand what will happen when they perform an action on the accessibility element **when that result is not apparent from the accessibility label**."

Therefore, if the result is apparent from a label, and the hint is not added, the linter shouldn't flag it as an error. But hint is flagged as an error each time the label is added to an element.

An example:

``

will give me an error - error has accessibilityLabel prop but no accessibilityHint react-native-a11y/has-accessibility-hint
But there is no other information I would want to convey for a logo... so no hint is needed.

I guess this can be improved by not including images?

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.