Update check failure - Update Service component

Question

VSCodium uses community-hosted releases instead of Microsoft's update infrastructure. The Update Service component can surface update availability and verification as silent or generic failures in the user workflow, with behavior that varies by distribution channel and release build.

The accessibility surface is inherited from VS Code, including keyboard navigation, focus management and screen reader annotations. VSCodium does not maintain a separate accessibility triage or user-facing reporting workflow, so improvements depend on upstream changes and community backport decisions.

There is no documented project-owned process for collecting and prioritizing accessibility issues from end users without telemetry. This leaves an open decision about how accessibility regressions are surfaced and addressed in the user-facing workflow.

The goal is to clarify the current user-facing signals for update status and for extension installation failures from Open VSX, and how those signals are presented to assistive technology.

What is the documented user-facing indication when an update check cannot be verified in VSCodium? How are generic update or extension download failures announced to assistive technology? Is there a project-owned process for collecting accessibility feedback on these workflow failures?

Tasadduq Burney · Answer

Direct answer
When an update check cannot be verified, VSCodium shows a transient toast notification. The wording varies by build and may read “Update check failed” or “Failed to check for updates.” Generic update or extension download failures appear as a toast together with a status bar entry, such as “Failed to download extension.” Screen readers that monitor live regions announce these messages when they appear, but automatic announcement depends on the operating system and screen reader. VSCodium does not operate a project-owned process for collecting accessibility feedback on these failures; reports go upstream to VS Code or to community channels.
Confirmed facts and likely explanation
Confirmed: VSCodium inherits the VS Code update service UI, so update and extension failures use toasts and status bar entries. There is no separate VSCodium accessibility triage workflow.
Likely explanation: Because VSCodium uses community-hosted releases instead of Microsoft's update infrastructure, signature or metadata verification can fail when network connectivity or release data is unavailable. The failure is non-blocking and the toast disappears after a few seconds.
Verification steps

Open VSCodium and confirm the Update Service is enabled under Settings > Update > Enable Update Service.
Disable network connectivity or block update URLs with a local proxy.
Run Help > Check for Updates and note the toast text.
With NVDA, VoiceOver, or Windows Narrator running, confirm whether the toast is announced immediately.
Install an extension from Open VSX, disconnect the network during download, and observe the toast and status bar entry.

Missing diagnostic detail: Which screen reader and operating system are you using? This determines whether transient toasts are announced without focus movement.
Scope note
This draft is based on community-reported behavior rather than a current VSCodium documentation snapshot. Verify the exact toast wording in your installed build before filing an issue.

Update check failure - Update Service component

1 answer

Direct answer

Confirmed facts and likely explanation

Verification steps

Scope note

Your perspective belongs here.

0 question comments