Skip to content

[v16] Create button in left navigation missing discernible text #20205

@MMasey

Description

@MMasey

Which Umbraco version are you using?

16.0.0+

Bug summary

Buttons in the Umbraco backoffice are missing discernible text or have unclear labels. Example: the Create (+ icon) button in the left-hand navigation tree identifies as #actions_create but is not formatted correctly and provides no context.

Specifics

  • Location: Left-hand navigation tree → Create (+ icon).
  • Instance: Identifies as #actions_create.
  • Issue: Missing discernible text, exposes internal identifier, lacks localization/context.
  • Screenshot:
Image
  • Possible Cause: Localization may not be working, or issue is captured too early. Missing contextual values should be parsed onto the Entity Action API for a GetLabel method.
  • Accessibility References:
  • WCAG Level A: 1.1.1 – Non-text Content
  • WCAG Level A: 2.4.4 – Link Purpose (In Contex

Proposed Fix

  • Ensure all icon buttons (including the Create (+) button) expose a discernible, localized accessible name.
  • The accessible name must not rely on internal identifiers (e.g., #actions_create) and should instead use localized strings that clearly describe the button’s purpose (e.g., “Create content”).
  • Confirm the localization pipeline is correctly applied so the label is available in the user’s chosen backoffice language.
  • If contextual values are required (for example, entity type or location), ensure these are parsed through to the label so it remains meaningful in context.

Acceptance criteria:

  • Screen readers announce the control with a meaningful purpose.
  • Labels are localized and context-aware.
  • Buttons pass WCAG Level A requirements:
    • 1.1.1 Non-text Content
    • 2.4.4 Link/Button Purpose (In Context)

Steps to reproduce

  1. Open the Umbraco backoffice (v16).
  2. Navigate to the left-hand navigation tree.
  3. Locate the Create (+ icon) button.
  4. Inspect the element.
  5. Observe that it identifies as #actions_create and has no discernible or descriptive text.
  6. This can also be reviewed using the free, open source screen reader NVDA, using the Elements List functionality as shown in the screenshot above.

Expected result / actual result

Expected result:

  • All elements should have descriptive, accessible names that convey their purpose.
  • The Create button should be labelled clearly (e.g., "Create Content" or "Add New Item") instead of exposing internal identifiers.
  • Labels should be localized and context-aware.

Actual result:

  • The Create button only identifies as #actions_create.
  • No meaningful text is provided, leading to accessibility failures.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions