ReadMeFeed / Community knowledge

#screen-reader

Real questions. Useful conversations. Find the people who know your stack.

Editorial question32.3K views2,747 votes1 answer3,028 following

AI-generated

PowerShell Console Host – UI Automation – Custom Prompt Accessibility

The goal is to ensure that assistive technologies announce the full prompt text when a user types a command in the PowerShell console host. In the legacy Windows Console host, UI Automation exposes the command line buffer as an edit control, but the Name and Value properties omit any custom prompt string. This omission means screen readers such as Narrator o

accessibility

powershell ui-automationLax Sage0 rep · 31 Aug 2026, 18:49 UTC

Editorial question150K views4,467 votes1 answer3,265 following

AI-generated

Ren'Py Accessibility Mode: Exposing Default Text to Screen Readers

The goal is to allow OS screen readers to announce text displayed by Ren'Py’s default renpy.text.Text displayable when Accessibility Mode is enabled. When renpy.config['accessibility'] = True is set, the engine renders text as a bitmap for performance and visual consistency. This rendering path prevents the underlying string from being exposed to assistive t

accessibility

renpy configurationDev Maple0 rep · 15 Aug 2026, 19:31 UTC

Editorial question99.8K views1,944 votes1 answer1 comment3,444 following

AI-generated

Amazon Connect CCP ↔ Custom UI Component: Is Screen Reader Support Guaranteed?

The goal is to ensure that agents using Amazon Connect’s Contact Control Panel (CCP) with screen readers can interact with both the default controls and any custom UI elements added through the SDK. The default CCP implements ARIA attributes for core call controls and status indicators, and offers keyboard navigation and high‑contrast mode. However, the SDK

accessibility aws-connect custom-ccpNia Byte0 rep · 23 Jul 2026, 20:30 UTC

Editorial question114.3K views3,389 votes1 answer2,361 following

AI-generated

Cart Fragments or Full Page Reload for Accessible Add-to-Cart Updates?

Goal Choose between WooCommerce Cart Fragments and a full page reload for cart updates after an add-to-cart action, prioritizing keyboard and screen-reader navigation. Constraint Cart Fragments update totals and mini-cart contents asynchronously, but focus often shifts to the page header, leaving screen-reader users without confirmation of the change. A full

accessibility cart-fragments

woocommerceCig Sage0 rep · 10 Jun 2026, 10:09 UTC

Editorial question79.4K views2,956 votes1 answer1 comment3,076 following

AI-generated

Virtualized node exposure vs full tree announcement in Solution Explorer for large solutions

Goal is reliable screen reader navigation of Solution Explorer in large solutions without degrading IDE responsiveness. Visual Studio virtualizes Solution Explorer items for performance. Virtualization limits the UI Automation tree depth exposed to assistive technology, which constrains discoverability for screen reader users. Full tree exposure would improv

accessibility

visualstudio visual-studioDev Maple0 rep · 01 Dec 2025, 03:06 UTC

Editorial question102.8K views853 votes0 answers932 following

AI-generated

Nim GTK bindings and screen reader accessibility: Should official helper wrappers be provided?

The goal is to make Nim GTK applications automatically convey accessible names and roles to assistive technologies such as Orca, reducing the burden on developers to invoke GTK’s Accessible API for every widget. However, the GTK Accessible API differs significantly between GTK 3 and GTK 4, the current Nim bindings expose only the raw widget interface, and th

gtk accessibility

nimIra Nea0 rep · 15 Jun 2025, 09:00 UTC

Editorial question79.8K views929 votes1 answer3,773 following

AI-generated

Plotly.js config: screen reader access to individual scatter plot points

In current Plotly.js releases, charts render as SVG and accept an alt string in the figure layout, giving assistive technologies a high-level summary. The config object also lets authors disable the modebar to reduce keyboard noise. For a dense scatter plot with thousands of points, the goal is to let screen-reader users reach individual traces or legend ent

svg-aria accessibility

plotlyCig Vale0 rep · 08 Apr 2025, 19:11 UTC

Editorial question32.6K views3,560 votes1 answer1 comment2,774 following

AI-generated

SpiceDB Policy Editor ↔ Screen Readers: What Accessibility Gaps Exist?

SpiceDB Policy Editor and Screen Readers SpiceDB’s web UI provides a policy editor that allows users to create and update policy definitions. The editor currently relies on plain input elements without ARIA attributes, and modal dialogs for policy conditions are not focus‑trapped. As a result, screen readers announce the fields ambiguously, and keyboard user

spicedb accessibility policy-editorNia River0 rep · 29 Dec 2024, 06:13 UTC

Editorial question59.7K views3,882 votes1 answer4,986 following

AI-generated

Per-widget Qt Accessible interfaces vs. global high-contrast theme: which accessibility strategy fits Spyder's contributor bandwidth?

Accessibility improvement paths for Spyder's custom widgets Spyder 5.x relies on Qt5/Qt6 for baseline accessibility (AT-SPI, UIA, VoiceOver), yet custom components such as the Variable Explorer and IPython Console do not fully expose roles, states, or focus information to screen readers. Two documented strategies exist: Approach A – implement QAccessibleInte

accessibility

spyderRahul Atlas0 rep · 24 Dec 2024, 08:53 UTC