Accessibility Barriers in Quicken Deluxe and Simplifi (edited)

Jose Tamayo
Jose Tamayo Member
edited May 19 in Feedback

To Whom It May Concern,
I am writing to formally express my deep disappointment regarding the continued lack of accessibility in Quicken products for blind and visually impaired
users who rely on screen readers.  I have more than 20 years of experience testing software accessibility using screen readers such as JAWS, NVDA, and
other assistive technologies. Based on that experience, I can say clearly that the accessibility barriers present in Quicken Classic Deluxe and Simplifi
are unacceptable in 2026.
The most concerning issue is not simply that there are bugs or isolated problems. The issue is that these accessibility barriers have existed for years,
despite accessibility standards, modern development frameworks, and widespread industry awareness regarding inclusive design.
With Quicken Classic Deluxe, the desktop application continues to present major usability barriers for screen reader users, including:
• Poor or missing labeling of controls
• Inconsistent keyboard navigation
• Interfaces that do not properly expose information to assistive technologies
• Controls that appear visually but are not properly accessible through standard accessibility APIs
• Complex navigation structures that create unnecessary barriers for blind users
• Areas where screen readers fail to identify context, focus changes, or actionable elements properly
These are not minor inconveniences. For blind users, these issues can make financial management frustrating, exhausting, and in some cases impossible without
sighted assistance.
Even more concerning was my experience with Simplifi. I attempted to use the Simplifi website and could not even successfully log in using a screen reader.
A financial platform that prevents blind users from independently accessing their accounts raises serious concerns about accessibility compliance and equal
access.
At this point, accessibility should not be treated as an afterthought or a future enhancement. Screen reader compatibility is not optional. Blind users
manage mortgages, investments, retirement accounts, taxes, banking, and business finances just like everyone else. We deserve equal access to financial
tools.
After two decades of accessibility awareness in the software industry, it is difficult to understand why Quicken products still present such fundamental
barriers to accessibility.
I strongly encourage Quicken to:
• Conduct a full accessibility audit of both Quicken Classic and Simplifi
• Test with real blind users and experienced screen reader testers
• Implement proper keyboard accessibility throughout the applications
• Ensure compliance with WCAG standards and accessible desktop application practices
• Establish an ongoing accessibility program instead of reacting only after complaints
• Publicly commit to improving accessibility for blind and visually impaired customers
Accessibility is not simply about legal compliance. It is about respect, independence, dignity, and equal opportunity.
I hope Quicken leadership takes this feedback seriously and recognizes that the blind community has been patient for far too long.
Sincerely,
Jose Tamayo
Screen Reader User and Accessibility Tester
20+ Years of Accessibility Testing Experience

Tagged:

Comments

  • Coach Natalie
    Coach Natalie Administrator, Moderator admin

    @Jose Tamayo, thanks for taking the time to write this up and share your experience. We definitely understand how frustrating these kinds of accessibility barriers can be, especially when it comes to something as important as managing finances independently.

    Since this is the Quicken Simplifi Community, we’d recommend also posting your feedback about Quicken Classic in the dedicated Classic Community so the right teams there can see it as well: https://community.quicken.com/

    For Quicken Simplifi-specific feedback and feature requests, we encourage you to post in our Ideas section. The Ideas section allows other users to vote for your idea and gives our product team a place to review and track the request. More details on how Ideas work can be found here:

    We appreciate you sharing your perspective and experience with us!

    -Coach Natalie

  • DryHeat
    DryHeat Superuser ✭✭✭✭✭

    @Coach Natalie

    I do not think that fixing site accessibility issues is an "Idea" that users should vote for or against. It is a critical problem that should be addressed by Quicken regardless of whether a large number of users find it important.

    The non-profit I work with is small and has very limited funds. But in the first year of our website's operation we realized how important this issue was. It was painful, but we bit the bullet and hired someone from the local university to audit the site and fix its problems.

    Surely Quicken can up its game on this issue without waiting for a critical mass of users to complain.

    DryHeat
    -Quicken Classic (1990-2020), CountAbout (2021-2024), Simplifi (2025-…)