Skip to content

Test: status bar accessibility #96265

@isidorn

Description

@isidorn

Refs: #94677

Complexity: 2


If you are on Windows setup NVDA screen reader.
If you are on Linux setup Orca latest from source (tested that it work on Ubuntu 18, ArchLinux, Fedora 31. Ubuntu 19 showed some issue) docs. Some troubleshooting

Turn on your screen reader, open VS Code. For NVDA press Insrt + End and the status bar content should be read. Make sure that what is read makes sense and captures what you see in the status bar.
For Orca you can orca -s from the command line and configure the keybinding for the read status command. Trigger that command and make sure that the status bar gets read out.

In both cases no duplicated content should be read out, and what is being read should be concise and descriptive enough.

Metadata

Metadata

Assignees

No one assigned

    Labels

    accessibilityKeyboard, mouse, ARIA, vision, screen readers (non-specific) issuestestplan-item

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions