Skip to content

feature request: line numbers should be reported by screen readers while navagating in the editor #1530

Description

@makhlwf

Issue Checklist

  • I confirm that this feature request has not been previously suggested.
  • I agree to follow the project's code of conduct.
  • I have checked and verified that I am using the latest version of Code on the Go from GitHub or App Dev for All.

Additional terms

  • I understand that feature requests are subject to evaluation and may not be implemented immediately.
  • I agree to provide additional details if needed for a clearer understanding of the requested feature.

Feature description

Originally reported [on Telegram](https://t.me/CodeOnTheGoDiscussions/6859) by [مُحَمَّد شَحَاتَه مَنْصُور](https://t.me/llllatwgj).

Problem

When using a screen reader in the code editor, the current line number is not announced.

Although line numbers are displayed in the gutter to the left of the editor, they are purely visual and are neither focusable nor exposed in a way that screen readers can access. As a result, blind users have no reliable way to determine which line they are currently editing.

Proposed Enhancement

Whenever the caret moves to a different line using the screen reader's line navigation commands (movement by granularity), the editor should notify the screen reader of the new line number.

For example, if the caret moves from line 19 to line 20, the screen reader should announce:

Line 20
Contents of line 20

This behavior should integrate with the screen reader's existing navigation model so that line announcements occur naturally when navigating by line, without requiring the user to move focus to the visual line-number gutter.

Benefit

Announcing line numbers significantly improves orientation within the editor, making it easier for blind developers to navigate code, reference compiler errors, discuss code with others, and work efficiently in large files.

Use Case

make the users aware of the code base and ther progress

Benefits

proviting full over view of the code context while editing or descovering

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Fields

    No fields configured for Feature.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions