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 Tests performed #290

Open
mouxdesign opened this issue Jun 30, 2022 · 8 comments
Open

Accessibility Tests performed #290

mouxdesign opened this issue Jun 30, 2022 · 8 comments

Comments

@mouxdesign
Copy link

Myself and Christoph did some accessibility testing today on the Phoenix wallet.

Overall the accessibility was quite good. We found a few things that can be optimized:

  • Some labelling issues
  • The Qr code recognition
  • The camera option opening and users being informed of this
  • Receive screen; Voice over confirmation of the amount and date of sats received

    Group 1 (1)

To provide a brief overview of what we are doing:

@mouxdesign
Copy link
Author

Have done some follow up tests on the receive flow which I recorded as well. This was a voice over only test performed on the Receive flow of Phoenix.

Summary of findings:
Overall the app is quite accessible with regards to voice over features, some areas could could be improved are:

  • Time is read out as numbers and not as an actual time
  • Copy button is labelled as a Tab button and so the screen reader reads it out as “Tabs”
  • Pop up modal (Receive screen) is not read out by voice over
  • The qr code is not acknowledged by the Voice over
  • Desc is read out as desc, however it is the description of the transaction

Link to google doc with video and notes how the app was analyzed and what actions were performed.

@dpad85
Copy link
Member

dpad85 commented Jul 8, 2022

Hello, thanks for testing the app and providing such a detailed feedback. Regarding Android we are completely reworking the app so some of the accessibility issues you found may just disappear, and new ones will certainly be created! Accessibility is something we will look at once the new Android app is ready to ship. Hopefully, jetpack-compose should make things easy to fix.

@robbiehanson
Copy link
Contributor

@mouxdesign Thank you so much ! This is incredibly helpful !

@GBKS
Copy link

GBKS commented May 4, 2023

Accessibility day is coming up on May 18 and in the Bitcoin Design Community we're looking to rally designers and developers to spend that day learning about accessibility and making improvements. Would you be interested in joining? Doesn't have to be a huge effort, could be simply about making some of the easier fixes of what is posted in this issue.

@robbiehanson
Copy link
Contributor

Just wanted to note that I spent a fair amount of time fixing a lot of accessibility issues earlier this year. So the iOS tests may need to be updated.

@mouxdesign
Copy link
Author

@robbiehanson Great to see this! Would it help if we re-tested the application?

@robbiehanson
Copy link
Contributor

Would it help if we re-tested the application?

Yes, that would be super helpful. We fixed many issues, but then we made large changes across the app for version 2. So I may have broken several things since then.

@GBKS
Copy link

GBKS commented Jan 5, 2024

We fixed many issues

So awesome to hear. I just did a quick test and the app is in really good shape (Version 2.1.0 on iPhone 15). Thank you for digging into this.

I found a handful of smaller issues that I documented here.

Phoenix accessibility test summary 240105

Great job adding in the tap-and-hold actions on the receive screen. A bit hard to discover, but super useful.

I am curious as to what user feedback you are getting for the "add liquidity" flow. I see you're using metaphors to explain the concept, I wonder if it clicks for people. Do you also explain these concepts on onboarding or is the "add liquidity" screen the first time people encounter them?

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

No branches or pull requests

4 participants