Project
ide
Description
In the Settings page under Extensions, the switch for Full Screen appears visually inside the correct setting row, but it does not appear to be programmatically associated with the visible setting title and descriptive text.
The row clearly presents the visible title Full Screen, the internal setting key zenMode.fullScreen, descriptive helper text explaining that full screen is entered when zen mode is activated, a default value note, and the switch itself. However, the inspected structure suggests the row is assembled from nested generic layout containers, and the visible label text and the switch control do not appear to be connected through a clear accessibility relationship.
Because of this, assistive technology users may encounter the switch without reliably hearing the exact setting name and context it controls.
This is an accessibility issue because a settings switch should expose a programmatic name that matches the visible setting label.
Error Message
Debug Logs
System Information
Cortex IDE: alpha
OS: Ubuntu 25.04
CPU: 13th Gen Intel® Core™ i7-13620H
RAM: 32 GB
Screenshots
Steps to Reproduce
Launch Cortex IDE.
Open Settings.
Navigate to Extensions.
Locate the setting named Full Screen.
Inspect the switch and the surrounding setting row using developer tools or an accessibility tree.
Verify whether the switch exposes an accessible name that matches the visible setting title, and whether the title and description are programmatically associated with the control.
Expected Behavior
The switch for Full Screen should expose a clear accessible name derived from the visible setting title.
The setting title should be programmatically tied to the switch.
If helper text is intended to describe the control, it should also be associated appropriately so assistive technologies can understand the setting in context.
Actual Behavior
The switch appears visually within the correct setting row, but the inspected structure suggests the visible label and the control may not be programmatically linked.
As a result, the switch may not expose the same clear meaning to assistive technologies that is obvious visually.
Additional Context
No response
Project
ide
Description
In the Settings page under Extensions, the switch for Full Screen appears visually inside the correct setting row, but it does not appear to be programmatically associated with the visible setting title and descriptive text.
The row clearly presents the visible title Full Screen, the internal setting key zenMode.fullScreen, descriptive helper text explaining that full screen is entered when zen mode is activated, a default value note, and the switch itself. However, the inspected structure suggests the row is assembled from nested generic layout containers, and the visible label text and the switch control do not appear to be connected through a clear accessibility relationship.
Because of this, assistive technology users may encounter the switch without reliably hearing the exact setting name and context it controls.
This is an accessibility issue because a settings switch should expose a programmatic name that matches the visible setting label.
Error Message
Debug Logs
System Information
Screenshots
Steps to Reproduce
Launch Cortex IDE.
Open Settings.
Navigate to Extensions.
Locate the setting named Full Screen.
Inspect the switch and the surrounding setting row using developer tools or an accessibility tree.
Verify whether the switch exposes an accessible name that matches the visible setting title, and whether the title and description are programmatically associated with the control.
Expected Behavior
The switch for Full Screen should expose a clear accessible name derived from the visible setting title.
The setting title should be programmatically tied to the switch.
If helper text is intended to describe the control, it should also be associated appropriately so assistive technologies can understand the setting in context.
Actual Behavior
The switch appears visually within the correct setting row, but the inspected structure suggests the visible label and the control may not be programmatically linked.
As a result, the switch may not expose the same clear meaning to assistive technologies that is obvious visually.
Additional Context
No response