Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Accessibility] Accessibility / 508 compliance ? #342

Closed
wesleyahall opened this issue Mar 27, 2015 · 10 comments
Closed

[Accessibility] Accessibility / 508 compliance ? #342

wesleyahall opened this issue Mar 27, 2015 · 10 comments
Labels
Resolution: Locked This issue was locked by the bot.

Comments

@wesleyahall
Copy link

Movie ListView Example : iOS Accessibility (Screen Reader) is not reading anything, even the plain text elements on the screen. The images are skipped entirely, as if they were background images or something.

Is there a way to get accessibility / screen reader mode activated?
If not, is it planned (soon)?
Or... do I have to go back to cordova?

This is a 100% breaking issue for my company. I guess I was dumb to assume "native" would include accessibility support.

@roman01la
Copy link

+1

I believe React Native components does not expose accessibility props to iOS, I'm not an expert, but it seems true.

@frantic
Copy link
Contributor

frantic commented Mar 27, 2015

We definitely do support that. See https://github.com/facebook/react-native/blob/master/Libraries/Components/View/View.js#L69
I know @vjeux implemented the support in ObjC land that automagically makes UI accessible, but maybe his change was lost during refactoring. cc @nicklockwood

@wesleyahall
Copy link
Author

I figured out the image problem (read the docs 😑) by adding accessible={true} but this prop doesn't appear to be available on Text components. How do we make the non-touchable Text components still readable?

On Mar 27, 2015, at 10:01, Alexander Kotliarskyi notifications@github.com wrote:

We definitely do support that. See https://github.com/facebook/react-native/blob/master/Libraries/Components/View/View.js#L69
I know @vjeux implemented the support in ObjC land that automagically makes UI accessible, but maybe his change was lost during refactoring. cc @nicklockwood


Reply to this email directly or view it on GitHub.

@vjeux
Copy link
Contributor

vjeux commented Mar 27, 2015

All the text elements should be accessible by default. Need to ensure that the accessibility features that we have in the internal codebase are ported to open source.

@hapasa
Copy link

hapasa commented Mar 27, 2015

There appears to be code looking for accessiblityLabel from the UIView.
Is there a way to set that from javascript?

@hapasa
Copy link

hapasa commented Mar 27, 2015

Ok, the following works: <Text accessibilityLabel='Hey, I'm accessible!'>Hello World</Text>
But accessibilityLabel should default to 'Hello World' in the above.

@ide
Copy link
Contributor

ide commented May 27, 2015

0.5.0-rc includes accessibility improvements: https://github.com/facebook/react-native/releases/tag/v0.5.0-rc

Can someone familiar with accessibility report whether the improvements are good enough and open up more specific issues if there are areas that still need to be addressed?

@brentvatne brentvatne changed the title Accessibility / 508 compliance ? [Accessibility] Accessibility / 508 compliance ? May 31, 2015
@brentvatne
Copy link
Collaborator

ping @wesleyahall

@christopherdro
Copy link
Contributor

@wesleyahall Any updates on this issue?

@brentvatne
Copy link
Collaborator

I'm using accessibility features extensively on an app to integrate with KIF for acceptance testing, everything seems to be working well. If you stumble upon this and accessibility tools within React Native aren't currently meeting your needs, please open an issue and let us know what your use cases are! Thanks!

@facebook facebook locked as resolved and limited conversation to collaborators Jul 23, 2018
@react-native-bot react-native-bot added the Resolution: Locked This issue was locked by the bot. label Jul 23, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Resolution: Locked This issue was locked by the bot.
Projects
None yet
Development

No branches or pull requests

9 participants