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

Add best practices for dealing with accessibility #25

Open
elland opened this issue May 3, 2016 · 17 comments
Open

Add best practices for dealing with accessibility #25

elland opened this issue May 3, 2016 · 17 comments

Comments

@elland
Copy link
Contributor

elland commented May 3, 2016

That was missing. 😉

@3lvis 3lvis changed the title Add best practices for dealing with accessibility. Add best practices for dealing with accessibility May 3, 2016
@3lvis
Copy link
Contributor

3lvis commented May 3, 2016

Could you elaborate please?

@elland
Copy link
Contributor Author

elland commented May 3, 2016

There was no mention of making the app accessible. I'd like to know what the procedure is.

@3lvis
Copy link
Contributor

3lvis commented May 3, 2016

As far as I know we haven't done much regarding accessibility. Would be great to improve on this subject, I think doing UI testing could be a good first step.

That's one of the selling points of KIF:

KIF relies on the built-in accessibility of iOS to perform its test steps. As such, it's important that your app is fully accessible. This is also a great way to ensure that your app is usable by everyone. Giving your views reasonable labels is usually a good place to start when making your application accessible. More details are available in Apple's Documentation.

@3lvis
Copy link
Contributor

3lvis commented May 3, 2016

Do you have any suggestions on what we could do to improve accessibility? Or in which specific areas we should focus on?

@elland
Copy link
Contributor Author

elland commented May 3, 2016

If we're going to do UI testing, we pretty much have to make the app accessible. I think first step would be to turn on VoiceOver and try to use the app (if it's already done). For most cases, if the app uses standard components, it's a matter of tweaking some labels and adding/removing some UI elements of VO is active. Also colour consideration for different kinds of colour blindness, etc etc.

@3lvis
Copy link
Contributor

3lvis commented Nov 22, 2016

  • Accessibility coverage (?)

@3lvis
Copy link
Contributor

3lvis commented Nov 22, 2016

  • Custom Alert controllers NO

@3lvis
Copy link
Contributor

3lvis commented Nov 22, 2016

  • Use Action Sheets when possible

@3lvis
Copy link
Contributor

3lvis commented Nov 22, 2016

  • Use accessibility label for UIButtons

@elland
Copy link
Contributor Author

elland commented Nov 22, 2016

And labels for images.

@3lvis
Copy link
Contributor

3lvis commented Nov 22, 2016

You mean for UIImageView? Or for UIImage (is that even possible)?

@elland
Copy link
Contributor Author

elland commented Nov 22, 2016

I'm surprised. 😄 UIImageVIew

@3lvis
Copy link
Contributor

3lvis commented Nov 22, 2016

@elland what surprises you?

@elland
Copy link
Contributor Author

elland commented Nov 23, 2016

The question. 👍

@3lvis
Copy link
Contributor

3lvis commented Nov 23, 2016

🤦

@marijnschilling
Copy link
Contributor

Ha! I'm gonna setup some (loosely followable) guidelines for how we reply on things on Github and in slack, to avoid conversations like this 🔝

@elland
Copy link
Contributor Author

elland commented Nov 23, 2016

:dolan:

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

No branches or pull requests

3 participants