---
title: Interactions
summary: Utility classes that change how users interact with contents of a website.
description: Control how users interact with content - manage text selection and pointer events with simple utility classes.
related: [/ui/utilities/cursors]
---
import Example from '@components/Example.astro';

## Text selection

Change the way in which the content is selected when the user interacts with it.

<Example>
<p class="user-select-all">This paragraph will be entirely selected when clicked by the user.</p>
<p class="user-select-auto">This paragraph has default select behavior.</p>
<p class="user-select-none">This paragraph will not be selectable when clicked by the user.</p>
</Example>

## Pointer events

Tabler provides `.pe-none` and `.pe-auto` classes to prevent or add element interactions.

<Example>
<div><a href="#" class="pe-none" tabindex="-1" aria-disabled="true">This link</a> can not be clicked.</div>
<div><a href="#" class="pe-auto">This link</a> can be clicked (this is default behavior).</div>
</Example>

## Accessibility

- `user-select-none` stops users from selecting and copying text. Never put it on content people may want to copy, such as a code snippet, an address, or an error message.
- `pe-none` blocks the mouse but leaves the element in the tab order, so a keyboard user can still reach and activate it. Add `tabindex="-1"` and `aria-disabled="true"`, as the example above does, or use the `disabled` attribute on a real control.
- `aria-disabled="true"` tells assistive technology the control is off, but it does not stop the click. `disabled` on a `button` or an `input` does both, and is the better choice when the element supports it.
- `user-select-all` selects the whole block on one click, which helps for a token or a key. Keep it off long text, where users expect to select a part.