Most CRMs are not accessible. Not slightly inaccessible -- fundamentally broken for anyone using assistive technology. Try navigating Salesforce with a keyboard only. Try using HubSpot with a screen reader. Try reading the tiny gray-on-white text in Pipedrive with low vision. These are not edge cases. According to the WHO, over 1 billion people worldwide live with some form of disability. In the US alone, 1 in 4 adults has a disability that affects daily activities.
When I started building SalesSheet, I made a decision that most startup founders skip: accessibility would be a first-class requirement, not a retrofit. Every feature would meet WCAG AA standards before shipping. This post explains what that means practically, why it matters for CRM software specifically, and what we did to get there.
Accessibility is not a feature. It is a prerequisite. Software that excludes 25% of potential users is not finished -- it is broken.
WCAG stands for Web Content Accessibility Guidelines, published by the W3C. The "AA" level is the standard most organizations target -- it covers the most impactful accessibility requirements without the extreme constraints of AAA. Here is what it means in practice for a CRM:
All text must have a minimum contrast ratio of 4.5:1 against its background (3:1 for large text). This sounds simple until you realize how many SaaS products use light gray text on white backgrounds for "aesthetic" reasons. That gray-on-white text might look sleek in a design mockup, but it is unreadable for the 300 million people worldwide with color vision deficiency or low vision.
In SalesSheet, we audit every color combination. Our primary text uses a contrast ratio of 7:1 or higher. Secondary text never drops below 4.5:1. Status indicators (deal stages, activity types) use both color and icons, so the information is conveyed even without color perception. We run automated contrast checks on every pull request -- if a developer introduces a color that fails WCAG AA, the build fails.
Every interactive element in SalesSheet is reachable and operable using only a keyboard. Tab moves between elements. Enter activates buttons and links. Arrow keys navigate within components like dropdown menus, pipeline boards, and data tables. Escape closes modals and menus.
This matters more in a CRM than in most applications. Sales reps spend hours per day in their CRM. Repetitive mouse movements cause real physical strain over time. Keyboard navigation is not just for screen reader users -- it is for anyone who wants to work faster or reduce wrist strain. Power users who learn keyboard shortcuts are measurably faster than mouse users, regardless of ability.
We publish our full keyboard shortcut reference and test every feature with keyboard-only navigation before release.
When you tab through a web application, you need to see where you are. The focus indicator -- typically an outline around the currently focused element -- is the visual equivalent of a cursor. Many web applications hide focus indicators because designers think they look ugly. This makes keyboard navigation impossible because users cannot see which element is selected.
SalesSheet uses visible, high-contrast focus indicators on every interactive element. The focus ring is a 2px solid outline in our brand teal color with an additional 2px offset for clarity. It is visible on both light and dark backgrounds. We do not suppress the default browser focus indicator -- we enhance it.
Screen readers (JAWS, NVDA, VoiceOver) convert visual interfaces into spoken text. For this to work, the HTML must be semantically correct. Buttons must be buttons, not divs with click handlers. Navigation must use nav elements. Form inputs must have associated labels. Images must have alt text. Data tables must have proper headers.
CRM-specific screen reader challenges include:
Cookie consent banners are one of the most common accessibility failures on the web. The banner covers content, traps keyboard focus, uses tiny dismiss buttons, and often cannot be navigated with a screen reader at all. For SalesSheet's marketing site and application, we built our cookie consent to be fully accessible:
CRM accessibility is not just about compliance or avoiding lawsuits (though ADA lawsuits against SaaS companies are increasing). There are practical business reasons why your CRM should be accessible:
If you have a sales team of 10 people, statistically 2-3 of them have a disability. Mayobe a rep has carpal tunnel and needs keyboard navigation. Mayobe someone has dyslexia and needs high contrast and clear typography. Mayobe a team member has a temporary injury -- a broken wrist, a concussion -- and needs to work differently for a few weeks. An accessible CRM serves all of these situations without requiring accommodations or workarounds.
If you sell to enterprises, government agencies, or educational institutions, accessibility compliance is increasingly a procurement requirement. Organizations subject to Section 508 (US federal agencies) or the European Accessibility Act cannot purchase software that fails basic accessibility standards. An inaccessible CRM disqualifies you from these deals before you even get to a demo.
Accessible design is good design. High contrast text is easier to read in sunlight. Keyboard shortcuts make power users faster. Clear visual hierarchy reduces cognitive load for everyone. Screen reader compatibility forces developers to write semantic HTML, which improves SEO and performance. Every accessibility improvement benefits all users, not just users with disabilities.
The curb cut effect: features built for accessibility benefit everyone. Curb cuts were designed for wheelchairs. They are used by parents with strollers, delivery workers with carts, and travelers with luggage. Keyboard navigation was designed for screen reader users. It is used by power users who want to work faster.
Accessibility is not a checkbox you tick once. It is an ongoing practice that requires continuous testing:
If you are evaluating CRMs, ask these five questions about accessibility:
Accessibility is not hard. It is not expensive. It just requires giving a damn. We built SalesSheet to be accessible from day one because everyone deserves software that works for them. If your current CRM does not meet that bar, it might be time to switch.
Sin tarjeta de crédito. Comienza a vender de forma más inteligente hoy.
Comenzar Prueba Gratis