Skip to content

Use consistent terminology for insert key between User Guide and Welcome Screen #13648

@Qchristensen

Description

@Qchristensen

Is your feature request related to a problem? Please describe.

On the "Welcome Screen", there is a line which reads:
"By default, the numpad Insert and main Insert keys may both be used as the NVDA key."

In the User Guide, in section 4.2.1, the second paragraph reads:
"NVDA can be configured so that the numpad Insert, Extended Insert and/or Caps Lock key can be used as the NVDA modifier key. By default, both the numpad Insert and Extended Insert keys are set as NVDA modifier keys."

Describe the solution you'd like

We should be consistent and use either "Main Insert" or "Extended Insert".

The Microsoft Style Guide simply notes the "Insert key" without distinguishing between them: https://docs.microsoft.com/en-us/style-guide/a-z-word-list-term-collections/term-collections/keys-keyboard-shortcuts

Wikipedia gives screen readers a mention but also doesn't offer a disctinction beween the different insert keys: https://en.wikipedia.org/wiki/Insert_key (in fact the text doesn't mention the number pad insert at all, although it is highlighted on the image of a keyboard).

I can't find any reference specifying what to call that insert key near delete, home, end etc. I've heard it called "extended insert" before although I am not sure how many people are familiar enough with either term?

So, I don't mind either way, but we should endeavour to be consistent, whatever we call it.

Describe alternatives you've considered

Doing nothing. That has mostly worked well until now, but it is probably worth neatening it up.

Additional context

Metadata

Metadata

Assignees

No one assigned

    Labels

    component/user-documentationgood first issuegithub features these at https://github.com/nvaccess/nvda/contributep4https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#prioritytriagedHas been triaged, issue is waiting for implementation.

    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