Skip to content
This repository has been archived by the owner on Oct 6, 2022. It is now read-only.

Results from an accessibility workshop #205

Open
35 tasks
aliak00 opened this issue Sep 11, 2018 · 0 comments
Open
35 tasks

Results from an accessibility workshop #205

aliak00 opened this issue Sep 11, 2018 · 0 comments
Labels
accessibility enhancement New feature or request

Comments

@aliak00
Copy link
Contributor

aliak00 commented Sep 11, 2018

SMS login:

  • can’t know if you’re in enter phone number part or enter country code part.
  • Clear button in input field doesn’t tell you it’s a clear button
  • What’s the easiest way to type in a phone number while in voice over? Can you speech to text it?
  • Double clicking done doesn’t move to next screen and just stays silent
  • Double click continue should maybe say, “loading, please wait” or something?
  • Done should say continue?
  • Back button doesn’t say “back button”, just says “button”

SMS login verification screen:

  • Double tapping number on verification code input unit does not input a number
  • Inline error message not read out when happens.
  • How is a code supposed to be remembered when it’s resent?
  • Double tapping works when going straight there.
  • “Zero Width Space” is read out because those are what occupy the verification field’s individual input fields.
  • All fields navigable while “loading”, but not clickable.
  • Reading out of “enter the verification code we sent to” doesn’t not include the identifier because it’s a separate UI element
  • X button doesn’t say it’s a “close” button

Signup:

  • Says text field but no idea what to enter. Should say “enter your email address”
  • Clear input button here says “clear input” - unlike one in passwordless screen
  • ENter password text field says “secure text field” but not what to enter
  • What’s the deal with passwords? Is it supposed to be read out at the end so you know what you wrote?
  • Accepting terms: “check box, button” is said, but no idea what’s being accepted. Should the “i accept…” text be before the check box so that the text is read first and the swiping right goes to the check box. Or should going on the checkbox read out the text?
  • Required fields, keyboard nav, “chevron left” is spoken - because it’s the image’s name, and the right chevron says nothing, just “button”
  • When you go to birthday field, it reads out “YYYY-MM-DD”, so how do you communicate the format of the birthday?
  • Verify email address, taken to a screen that does not focus on the “click to verify link” so i assume one would just browse randomly and click whatever link is found.

Voiceover — Passwordless login with email

  • Screen starts with focus on text field for entering the email, but you have no clue about what that text field is supposed to be for
  • Weird “zero with space” message read every time you enter a digit
  • Back and cancel buttons just read “button”
  • Only first link in T&C is recognized
  • Back & forward button to move among text fields just read “button”
  • It’s hard to navigate among text fields in required fields screen since the title is separate from the field itself.
  • It’s very hard to understand the format you are supposed to enter the date in

Zoom — Passwordless login with email

  • The Done button is hard to find
  • After entering the correct code, I go to what appears to be a blank screen
  • In the T&C screen, the accept button is very far and hard to find
  • It’s hard to understand what’s happening when the UI is loading, since the loading state is only visible at the bottom of the screen.

Cambridge glasses — Passwordless login with email

  • Text is very small to read (maybe support for dynamic type would help?)
@aliak00 aliak00 added enhancement New feature or request accessibility labels Sep 11, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
accessibility enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant