> For the complete documentation index, see [llms.txt](https://help.steeple.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.steeple.com/en/centre-d-accompagnement/accessibilite-tous.md).

# Make Steeple accessible to everyone

### Internal communication must be universal

Every employee, regardless of their role or tools, must be able to access Steeple. As a communicator, the role of the contact person is strategic: they are the **guarantor of access to information**.

### Step 1: carry out an accessibility audit

Before taking any action, start with a **snapshot of the situation** to understand how employees can or cannot access Steeple.

#### To audit

* **Work equipment** :
  * Work smartphone?
  * Work computer?
* **Digital access** :
  * Work email address?
* **On-site presence** :
  * Regular visits to the break room, reception, changing room, or other common area?

Tip: centralize this information in a shared file with the team or HR, and classify it by type of access.

### Step 2: set up the right channels

Once the audit is complete, **adapt Steeple’s distribution methods** according to the profiles.

#### For employees with a work smartphone

Automatic pre-installation of the Steeple app via MDM (Mobile Device Management).

#### For employees with a work email

Automatic activation of the Steeple summary email (every morning or every week).

#### For employees with a computer

Set Steeple as the browser homepage.

### Step 3: equip living spaces with touchscreens

For employees without digital access, the alternative is physical display via Steeple screens.

### Steeple phygital

The **phygital**, means combining the best of physical and digital. It is the answer to communication silos between office and field teams.

#### The 3 pillars

* **Interactive touchscreen** in living spaces (break room, reception, etc.)
* **Mobile app** to interact and express yourself
* **Web platform** accessible to all

Result: **a single tool**, accessible to all, that **brings teams together**.

### Best practices for touchscreens

#### Hardware selection

* Capacitive touchscreens **(more durable, easier to clean)** Box
* Android **(Elo)** or **Chrome OS**
* Fixed wall mount or fixed stand depending on needs

#### Recommended sizes

* **43"** for standard spaces
* **55"** for high-traffic areas
* **24"/32"** for secondary locations

#### Ideal location

* At **eye level** (\~150 cm)
* Near the **coffee machine** or in a **high-traffic area**
* No visible cables, no clutter in front

#### Technical requirements

* **Ethernet connection** (preferred over Wi-Fi)
* **Double power outlet**
* **Solid wall** (not drywall alone)
* **Lighting without direct glare**

### Monitor the proper functioning of the screens

To ensure that **every employee has access to information**, it is not enough to install the screens. You also need to make sure they are **turned on, connected, and used**.

In the Steeple admin panel, the **“Screens”** section lets you see at a glance:

* screens that are on
* screens that are off or disconnected
* the last update or activity date

This makes it possible to act quickly, identify underused locations, and track changes in usage over time.

> *A screen that is installed but turned off is a missed opportunity to build connections and share information.*

### Practical field tips

* A clearly visible screen **but poorly placed** is useless
* Always think about **usage** before **aesthetics**
* Prefer **wired connection** in industrial environments
* Install a screen **where employees have time** : canteen queue, break room, changing rooms…

### The Steeple conviction

Internal communication should not be reserved for a connected elite. Phygital is the way to **break down silos**, **bring teams together** and **give everyone a voice**.

### In practice

1. Launch the**accessibility audit**
2. Set up the **appropriate channels**
3. Equip strategic locations
4. Monitor proper operation
5. Ensure **the inclusion of all employees**


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.steeple.com/en/centre-d-accompagnement/accessibilite-tous.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.