User experience (UX)

User experience, or UX, is how well a site works for the people who use it, judged by whether they reach their goal without friction. A Drupal site has two groups of users: editors, who live in the administrative interface, and visitors, who see the front end. The UI is the screens; UX is the result of using them.

What shapes UX in Drupal 11

A site builder shapes the editor experience without writing code:

• The edit form. The core help topic on the edit form lets you order the fields, move unused fields into a Disabled section, and pick the widget that edits each field.
• The menu people see. The administrative menu shows only what the installed modules and the person's permissions allow, so roles shape the experience.
• The editing tools. Core ships CKEditor 5 for rich text and a Media Library whose info file says it makes existing media items easier to find and use.

For visitors, the theme, the content and accessibility shape the experience. Drupal.org says the project treats accessibility barriers as bugs, and its core gates, a checklist for judging whether a core change is ready, include Accessibility and Usability.

Example

An editor complains that the form for your Event content type is long and confusing. Go to Structure › Content types, click Manage form display in the Operations list for Event, and drag the fields into the order editors work in. Drag fields they never fill in to Disabled, check each widget, and click Save. Then create an event yourself to test the form, as the help topic suggests.

Common mistakes

• Judging UX by looks. A polished screen can still hide the one button an editor needs. Ask people to finish a real task and watch where they stop.
• Testing only as an administrator. You see more menu items and fields than an editor does. Test with the role your editors have.
• Assuming core accessibility covers your site. Drupal.org states that its standards guide development and review, not that every interface or site conforms. Custom themes, content and added modules need their own checks.

For marketing and content teams

You are the experts on how the editing screens feel. Collect the repeated complaints: a confusing field name, a missing field, a step that takes five clicks. Hand them to your site builder as specific requests. Field order, widgets and who sees which menu items are settings, not development projects.

With DXPR

The DXPR accessibility page says DXPR Theme provides a skip link and landmarks, and that DXPR Builder gives every element action a keyboard shortcut. See Drupal accessibility with DXPR.

Sources

• Drupal.org: Accessibility (checked 2026-10-26)
• Drupal core 11.4.10 help topic: Configuring the edit form for an entity sub-type
• Drupal core 11.4.10 help topic: Using the administrative interface
• Drupal core 11.4.10 theme: Default Admin info file
• Drupal core 11.5.0-beta1 theme: Default Admin info file
• Drupal core 11.5.0-beta1 Standard profile: system.theme.yml
• Drupal core 11.4.10: Media Library info file
• Drupal.org: Core gates (checked 2026-10-26)