Skip to content

add accessibility support#179

Open
sarvarrose wants to merge 4 commits intoFortAwesome:0.3.xfrom
sarvarrose:sarvar-add-accessibility-support
Open

add accessibility support#179
sarvarrose wants to merge 4 commits intoFortAwesome:0.3.xfrom
sarvarrose:sarvar-add-accessibility-support

Conversation

@sarvarrose
Copy link

@sarvarrose sarvarrose commented Aug 8, 2025

Fixes #177

Example Usage:

import { faMugSaucer } from '@fortawesome/free-solid-svg-icons/faMugSaucer'
import { FontAwesomeIcon } from '@fortawesome/react-native-fontawesome'

... react component
return {
	<FontAwesomeIcon icon={faMugSaucer} accessibilityLabel='Saucer' />
}

In web, DOM looks like:
dom

@sarvarrose
Copy link
Author

Open Questions:

  • Should aria-hidden prop take precedence over accessible if passed?
  • There are 2 other props for which support can be added:
  • aria-labelledby
  • aria-describedby

@phazei
Copy link

phazei commented Oct 14, 2025

@sarvarrose

The aria props are, I can only presume, for react-native web, since they don't do anything for native. I think the native first props should have priority over mobile only ones.

@charles4221 is anyone maintaining this repo? Please have someone at FontAwesome remember this exists!

@robmadole robmadole self-requested a review February 3, 2026 21:30
@robmadole
Copy link
Member

I'm reviewing this now against the 1.x branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

zero accessibility

3 participants