I would like to raise a serious accessibility issue that affects thousands of Google users worldwide — including organizations using Google Workspace and Google for Nonprofits.
Currently, 2-Step Verification (2SV) can only be completed via SMS or QR code prompts, both of which require a smartphone. However, many users — especially those who, for personal or community reasons, do not use smart devices — are completely unable to access their Google accounts because of this limitation.
We strongly request that Google add an alternative voice call–based verification method.
For example, the system could:
Generate a unique code for the user.
Provide a number the user can call.
The user enters the code via keypad and receives a verification code in return.
This would allow full security (since it’s as safe as SMS) while ensuring accessibility for all users — even those without smartphones.
A Google Workspace Support representative (Kasarla) advised me to submit this request here in the developers forum, so that the engineering team can review it and consider this option in future updates.
I sincerely hope this suggestion reaches the relevant engineering teams and helps Google make its authentication process more inclusive.
Thank you for your time and for considering this feedback.
You are highlighting a valid challenge in the “Mobile-First” security era. For organizations or communities that rely on landlines or basic feature phones, the move toward “Google Prompts” and QR codes can feel like a barrier.
It is worth noting that Google does currently support voice calls for 2SV, though it is often secondary to prompts. When a user is asked to verify, they can often select “Try another way” and choose “Get a verification code at (phone number)”, which offers a “Voice Call” option. However, your proposal for a user-initiated call-in system is a distinct and interesting mechanical shift.
the 2SV Architecture
To visualize how suggestion of user calling to a number would integrate into the current security flow, here is a look at the standard verification paths:
The current “Voice Call” method is outbound (Google calls you). Your other suggestion for an inbound system (you call Google) would require a significant change to the authentication handshake to ensure that the incoming call is securely mapped to the specific login session.
Strategic Ways to Move This Forward
Since a Support Representative directed you here, the goal is to get this into the hands of the Identity and Access Management (IAM) engineers. Here are the most effective channels:
• Google Workspace Feature Ideas: If you have a Workspace account, the Customer Idea Portal is the most direct way to get “votes” on a feature. Engineering teams prioritize requests that show high community demand.
• The “Send Feedback” Button: In the Google Admin Console or the standard Security Checkup page, using the “Send Feedback” link actually sends metadata (like your browser/account type) along with the request, which helps engineers understand the technical context.
• Accessibility Support: Google has a dedicated Disability Support team that focuses specifically on hurdles like this. You can reach out to them via the Google Accessibility site, as they advocate for users who cannot use standard hardware.
Immediate Alternatives more reliable but not very cost effective "
For users who cannot use a smartphone today, I highly recommend looking into FIDO-compliant Security Keys (like YubiKeys). These:
Plug directly into a USB port.
Require no smartphone or cellular signal.
Are actually more secure than SMS or Voice codes.
A Big Shout-Out to Moshe
Kudos to Moshe for taking the time to write such a clear, constructive, and impactful request. It’s exactly this kind of feedback—focused on real-world accessibility and human-centric design—that forces tech giants to build better, more inclusive tools for everyone. Moving the needle on global security policy starts with voices like his.
I also want to give a huge shout-out to Kasarla from Google Workspace Support. It’s great to see a support representative who doesn’t just give a scripted answer but recognizes a systemic gap and directs a user to the right place to advocate for real change. Kudos to both of you for bridging that gap!
I haven’t been able to find the “voice call” option. It isn’t offered not as a primary prompt nor as a secondary or any other. The only option given is a via text/SMS. Any help with this would be greatly appreciated.
Glad to see you responded, buddy.
Unfortunately Google does not support voice call verification on free user accounts.
To this day thousands of reports online about this limitation, as can be seen here.
Unfortunately there is no clear progress with this.
Keep in mind that when opening an account, Google requires the use of a QR code
Hundreds of thousands of users do not have this option!
And are unable to open a new account!
And I’m not talking about accessibility for the disabled, someone who chose to go down the path without a smartphone or iPhone, is he called disabled?
He chose to use a device that doesn’t receive SMS
He is not disabled! He chose a certain way of life, and he is proud to follow it. He would be happy if large and giant companies like Google would find him the solutions for his way of life! (Of course, when thousands of friends share his path)
Keep in mind that users can also use physical USB, NFC, or Bluetooth security keys (such as YubiKeys or Titan Security Keys) plugged directly into a computer desktop or laptop to authenticate without needing any mobile device.
I’m also talking about creating an account!
Or about those who didn’t create a USB
I expect you to grow up, thousands of people who got stuck, didn’t think before about the option of disabling voice verification, or that one day they will require them.
I’m also not just talking about two-step verification! Also about basic security measures that Google sometimes requires.