Home Tags Posts tagged with "blinking cursor"
Tag:

blinking cursor

Close-up of a man typing on a keyboard, ideal for business themes.
Developer AccessibilityUI Accessibility

How to Stop the Blinking Cursor (Text Caret | ) in Zoom Docs and AI for Web

by Sensory Diversity
written by Sensory Diversity

If you’ve ever found yourself staring at a blinking line while trying to think, you know how distracting it can be. In Zoom Docs and the Zoom AI Companion, that rhythmic flash can feel like a tiny metronome counting down your productivity.

Fortunately, you can “freeze” the cursor using a custom Userscript. This guide will show you how to install Tampermonkey and apply a script to keep your cursor steady and solid.

Part 1: Getting Tampermonkey

Tampermonkey is the world’s most popular userscript manager. It allows you to run small “patches” of code on specific websites to change how they look or behave.

1. Download for Your Browser

Visit the Official Tampermonkey Website or use the direct store links below:

2. Enable Developer Mode (Chrome/Edge Only)

In 2026, many browsers require a quick security toggle to run scripts:

  1. Go to chrome://extensions or edge://extensions.

  2. Switch the Developer Mode toggle (top right) to ON.

Part 2: The “Solid Cursor” Script

Once Tampermonkey is installed, follow these steps to create your theme:

  1. Click the Tampermonkey icon in your browser toolbar.

  2. Select Create a new script.

  3. Delete everything in the editor and paste the following code:

JavaScript
// ==UserScript==
// @name         Zoom Docs & AI - Solid Cursor
// @namespace    http://tampermonkey.net/
// @version      1.2
// @description  Stops the cursor from blinking in Zoom Docs and Zoom AI Companion
// @author       Gemini
// @match        https://docs.zoom.us/*
// @match        https://*.zoom.us/*
// @grant        GM_addStyle
// ==/UserScript==

(function() {
    'use strict';

    const css = `
        /* Targets the custom cursor used in Zoom's editor */
        .ProseMirror-cursor, 
        [class*="cursor"], 
        [class*="caret"] {
            /* Keep it visible */
            visibility: visible !important;
            opacity: 1 !important;
            display: block !important;
            
            /* Stop the blink animation */
            animation: none !important;
            -webkit-animation: none !important;
            
            /* Style adjustment: Make it easier to see since it's static */
            border-left: 2px solid #2D8CFF !important; 
        }

        /* Target the AI Companion chat container specifically */
        .zm-ai-chat-input-box [role="textbox"] {
            caret-color: #2D8CFF !important;
        }
    `;

    if (typeof GM_addStyle !== "undefined") {
        GM_addStyle(css);
    } else {
        const style = document.createElement("style");
        style.textContent = css;
        document.head.append(style);
    }
})();

  1. Go to File > Save in the Tampermonkey editor.

Part 3: How it Works

The script works by injecting a “Global Override” into the Zoom interface.

Most modern text editors (like Zoom Docs) don’t use the default browser cursor; instead, they create a small div element that sits on top of the text and uses a CSS @keyframes animation to fade in and out. By setting animation: none !important, we tell the browser to ignore the “blink” command and keep the element fully opaque at all times.

Customizing Your Theme

Inside the script, you can change the look of your new static cursor:

  • Change Color: Change #2D8CFF to red, black, or any hex code.

  • Change Thickness: Change 2px to 4px if you want a block-style cursor.

Troubleshooting

  • Not working in the AI Chat? If the AI chat box uses a “Native Caret,” the browser manages the blinking internally. If the script doesn’t stop the blink there, it’s because the browser’s engine is overriding the web code.

  • Script not loading? Ensure the Tampermonkey icon shows a green “1” when you are on the Zoom Docs page, indicating the script is active.

Fortunately, you can “freeze” the cursor using a custom Userscript. This guide will show you how to install Tampermonkey and apply a script to keep your cursor steady and solid.

Part 1: Getting Tampermonkey

Tampermonkey is the world’s most popular userscript manager. It allows you to run small “patches” of code on specific websites to change how they look or behave.

1. Download for Your Browser

Visit the Official Tampermonkey Website or use the direct store links below:

2. Enable Developer Mode (Chrome/Edge Only)

In 2026, many browsers require a quick security toggle to run scripts:

  1. Go to chrome://extensions or edge://extensions.
  2. Switch the Developer Mode toggle (top right) to ON.

Part 2: The “Solid Cursor” Script

Once Tampermonkey is installed, follow these steps to create your theme:

  1. Click the Tampermonkey icon in your browser toolbar.
  2. Select Create a new script.
  3. Delete everything in the editor and paste the following code:

JavaScript

// ==UserScript==
// @name         Zoom Docs & AI - Solid Cursor
// @namespace    http://tampermonkey.net/
// @version      1.2
// @description  Stops the cursor from blinking in Zoom Docs and Zoom AI Companion
// @author       Gemini
// @match        https://docs.zoom.us/*
// @match        https://*.zoom.us/*
// @grant        GM_addStyle
// ==/UserScript==

(function() {
    'use strict';

    const css = `
        /* Targets the custom cursor used in Zoom's editor */
        .ProseMirror-cursor, 
        [class*="cursor"], 
        [class*="caret"] {
            /* Keep it visible */
            visibility: visible !important;
            opacity: 1 !important;
            display: block !important;
            
            /* Stop the blink animation */
            animation: none !important;
            -webkit-animation: none !important;
            
            /* Style adjustment: Make it easier to see since it's static */
            border-left: 2px solid #2D8CFF !important; 
        }

        /* Target the AI Companion chat container specifically */
        .zm-ai-chat-input-box [role="textbox"] {
            caret-color: #2D8CFF !important;
        }
    `;

    if (typeof GM_addStyle !== "undefined") {
        GM_addStyle(css);
    } else {
        const style = document.createElement("style");
        style.textContent = css;
        document.head.append(style);
    }
})();
  1. Go to File > Save in the Tampermonkey editor.

Part 3: How it Works

The script works by injecting a “Global Override” into the Zoom interface.

Most modern text editors (like Zoom Docs) don’t use the default browser cursor; instead, they create a small div element that sits on top of the text and uses a CSS @keyframes animation to fade in and out. By setting animation: none !important, we tell the browser to ignore the “blink” command and keep the element fully opaque at all times.

Customizing Your Theme

Inside the script, you can change the look of your new static cursor:

  • Change Color: Change #2D8CFF to red, black, or any hex code.
  • Change Thickness: Change 2px to 4px if you want a block-style cursor.

Troubleshooting

  • Not working in the AI Chat? If the AI chat box uses a “Native Caret,” the browser manages the blinking internally. If the script doesn’t stop the blink there, it’s because the browser’s engine is overriding the web code.
  • Script not loading? Ensure the Tampermonkey icon shows a green “1” when you are on the Zoom Docs page, indicating the script is active.

0 comments
0 FacebookTwitterPinterestEmail
AwarenessDeveloper AccessibilityUI Accessibility

The Blinking Cursor (Text Caret) is an Overlooked Accessibility Barrier in Software Development

by Sensory Diversity
written by Sensory Diversity

The Blinking Cursor: An Overlooked Accessibility Barrier in Software Development

For most software developers, the blinking cursor in code editors and Integrated Development Environments (IDEs) is an expected, even unnoticed, part of their daily workflow. Yet, for individuals with sensory processing disorders, visual sensitivities, and other neurodivergent conditions, the inability to disable this constant flicker presents a significant barrier to accessibility.

The Problem with the Blinking Cursor

The blinking cursor has been a staple of text-based interfaces for decades, intended to signal where text input will appear. However, this seemingly minor design choice can be highly disruptive for some users.

  • Sensory Overload: People with sensory processing differences, such as those with autism or misophonia, can find the flickering motion distracting or even distressing. Constantly shifting visual elements can create cognitive fatigue and impede focus.
  • Photosensitive Conditions: Some individuals with epilepsy, migraines, or other neurological conditions may be triggered by repetitive flashing patterns, no matter how subtle.
  • Attention and Processing Differences: Developers with ADHD or other attention-related conditions may struggle with maintaining focus when an element of their screen is repeatedly drawing their eye.
  • Lack of Customization: While many accessibility-conscious applications allow for font size changes, dark mode, and other user-friendly options, most coding environments do not offer a way to disable or adjust the blink rate of the cursor.

Ableist Design in Software Development

The exclusion of an option to disable the blinking cursor is a prime example of ableist design—when technology is built primarily for neurotypical or able-bodied users, disregarding those with different needs. The lack of awareness in mainstream development environments is reflective of the broader issue of ableism in tech, as discussed in the article Agile Development: Ableist Extroverts Setting Agendas (Tameri).

Agile development, for example, often favors fast-paced, highly collaborative processes that do not accommodate neurodivergent thought patterns, sensory needs, or working styles. The unwillingness to implement small but meaningful accessibility options, such as disabling the blinking cursor, reveals a deeper bias: the assumption that all developers work in the same way and have the same needs.

A Call for Change

It is time for software development tools to incorporate better accessibility options, including:

  • Cursor Blink Rate Settings: Users should be able to reduce the blink rate or disable the blinking cursor entirely.
  • Alternative Visual Indicators: Highlighting the cursor location with a static color change or outline could be an effective alternative.
  • Accessibility-First Development: IDE creators and text editor developers should actively seek input from neurodivergent and disabled users when designing features.

Several operating systems allow for some control over cursor blink rates, but IDEs and text editors like VS Code and Sublime Text have yet to offer built-in options for users who find the blinking cursor problematic. Until these features are standard, developers needing an accessible workspace are left with clunky workarounds, such as modifying system settings (where possible) or using third-party extensions—if they even exist for their preferred editor.

IF YOU HAVE A SENSORY DISORDER, AND WANT NO BLINKING CURSOR, PYCHARM IS AMAZING!

Conclusion

The lack of control over the blinking cursor in most development environments is a small yet significant oversight that highlights broader issues of ableist design in software. By incorporating accessibility-conscious choices, developers and tool designers can ensure that coding environments are truly inclusive for all. Until then, many neurodivergent and disabled developers will continue to struggle with an unnecessary and avoidable barrier to productivity.

 

0 comments
0 FacebookTwitterPinterestEmail