> For the complete documentation index, see [llms.txt](https://www.designreference.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.designreference.xyz/cognitive-tools/ux-laws-principles/interaction/gestalt-principles/focal-points.md).

# Focal Points

Whatever stands out visually will capture and hold the user's attention first.

Elements with a point of interest, emphasis or difference will capture and hold the viewer's attention.

The focal point principle is a Gestalt rule that explains how our eyes are naturally drawn to any element that looks different from its surroundings. In a sea of similar items, the one that stands out through a change in colour, shape, size, or texture immediately captures the user's attention. This is a fundamental tool in user experience design because it allows you to highlight the most important action you want a person to take, such as signing up for a newsletter or adding an item to a shopping basket.

To create an effective focal point, you must establish a sense of contrast against the rest of the layout. If every element on a page is bright and bold, nothing will truly stand out, leading to a cluttered and confusing experience. By keeping the majority of the interface consistent and understated, you ensure that the one area you have highlighted becomes the clear starting point for the user. This helps people process information faster because they do not have to search for where to click or what to read first.

It is also vital to use this principle sparingly to maintain its impact. Having too many focal points on a single screen creates visual noise and can lead to decision paralysis, where the user feels overwhelmed and ends up doing nothing at all. When applied correctly, a well-placed focal point acts as a visual landmark that guides the user through a digital product with ease and confidence.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.designreference.xyz/cognitive-tools/ux-laws-principles/interaction/gestalt-principles/focal-points.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
