[BUG] [alpha] Settings Page: Number input with stepper: no aria-valuenow when value changes

[Rwhiteman525]

Project

cortex

Description

Number inputs with increment/decrement steppers (e.g. port, line number) may not expose the current value to the a11y tree via aria-valuenow. Screen reader users may not hear the value after using the stepper. Verifiable only in DOM.

Error Message

Debug Logs

System Information

$ bounty info

Screenshots

395.mp4

Steps to Reproduce

Settings Page: Find a number input with stepper. Change value via stepper. Inspect the input for aria-valuenow.

Expected Behavior

Input has aria-valuenow reflecting current value (and aria-valuemin/aria-valuemax if applicable).

Actual Behavior

May be missing; verifiable only in inspector.

Additional Context

No response

[echobt]

✅ Validated

VALID BUG - Accessibility issue confirmed in Settings page number inputs.

Component Location: src/components/settings/SettingsEditor.tsx, specifically the NumberRenderer function (around line 1130).

Bug Confirmed: The number input rendered for settings like Font Size, Line Height, Tab Size, etc. does NOT include the required ARIA attributes:

• Missing aria-valuenow - screen readers cannot announce the current value
• Missing aria-valuemin when min is defined
• Missing aria-valuemax when max is defined

Code Evidence:

<input
  type="number"
  value={props.value}
  min={props.setting.min}
  max={props.setting.max}
  step={props.setting.step || 1}
  // NO aria-valuenow, aria-valuemin, aria-valuemax attributes!
/>

User Impact: Screen reader users cannot hear the current value when using the stepper buttons to increment/decrement number values in the Settings page.

Accessibility Path: User opens Settings → GUI Settings Editor → Any number input (Font Size, Line Height, Minimap Width, etc.) → Uses stepper buttons → Screen reader cannot announce the new value because aria-valuenow is missing.

The video clearly demonstrates this by showing the DOM inspector while changing a number input value - no aria-valuenow attribute is present or updated.

[suxg001]

Claiming this. I’ll patch NumberRenderer in src/components/settings/SettingsEditor.tsx to add aria-valuenow (and aria-valuemin/max when present), verify via DOM inspector, and submit a PR within ~2 hours.

Plan:

• Locate NumberRenderer and set aria-valuenow based on current value
• Pass through min/max props to aria-valuemin/aria-valuemax when defined
• Verify stepper updates aria values

[suxg001]

Fix submitted in CortexLM/cortex-ide:\n- PR: https://github.com/CortexLM/cortex-ide/pull/47\n\nChanges: add aria-valuenow plus aria-valuemin/aria-valuemax to number inputs in SettingsEditor NumberRenderer so stepper updates are reflected in the a11y tree.\n\nVerification: inspect DOM after using stepper; aria-valuenow now updates with current value; aria-valuemin/max present when min/max defined.