Update check failure - Update Service component

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?