# Accessibility

### Accessibility in Crobox campaigns

Crobox provides a flexible approach to campaign accessibility through configurable components and ARIA attributes. You have control over accessibility settings through a two-level system: technical teams configure accessibility defaults and exposure settings in Component Builder, while campaign editors customize specific attributes during campaign setup.

Key accessibility features include:

* **Configurable ARIA roles and labels** for proper screen reader support
  * Overlay and Notification component types default to `dialog` role
* **Alternative text configuration** for images and media
* **Expose mode controls** for managing which accessibility attributes are editable per campaign

***

### How accessibility configuration works

Accessibility settings are managed through a two-step process:

{% stepper %}
{% step %}
**Component Builder setup**

In the Component Builder, you configure which accessibility attributes are available to campaign editors:

* **Enable expose mode**: Toggle to make accessibility settings visible and configurable
* **Default values**: Set default ARIA roles where needed (Overlay and Notification component types default to `dialog` role upon creation)
* **Expose specific attributes**: Choose which accessibility settings campaign editors can modify
  {% endstep %}

{% step %}
**Campaign content setup**

When building individual campaigns, editors can customize the accessibility attributes you've exposed within the Component Builder:

* **Exposed fields appear in Design and/or Content tab**: Configurable attributes show up as editable fields (like "Component Aria Role")
* **Non-exposed fields use defaults**: Hidden attributes use the default values set in Component Builder
* **Per-campaign customization**: Each campaign can have different accessibility configurations where needed
  {% endstep %}
  {% endstepper %}

{% hint style="info" %}
Only accessibility attributes that are "exposed" in Component Builder will appear as editable fields during campaign setup. This gives technical teams control over which settings campaign editors can modify.
{% endhint %}

***

### Setting up accessibility controls

#### In Component Builder

1. **Configure default accessibility**: Set appropriate ARIA roles, labels, and alternative text
2. **Enable expose mode**: Turn on exposure for attributes that campaign editors should control per campaign
3. **Choose what to expose**: Select which accessibility fields (ARIA roles, alt text, etc.) should be configurable per campaign

#### In campaign setup

1. **Review exposed fields**: Check the Design/Content panel for available accessibility settings
2. **Customize as needed**: Modify ARIA roles, labels, and other exposed attributes for your specific campaign
3. **Test accessibility**: Verify that your configurations work with assistive technologies

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><strong>Technical teams (Component Builder)</strong></td><td><ul><li>Set up default ARIA roles and accessibility structure</li><li>Decide which accessibility attributes campaign editors can modify</li><li>Ensure baseline accessibility compliance for all components</li></ul></td></tr><tr><td><strong>Campaign editors (Campaign setup)</strong></td><td><ul><li>Configure exposed accessibility attributes for specific campaigns</li><li>Write clear, descriptive labels and alternative text</li><li>Test accessibility with target audience and tools</li></ul></td></tr></tbody></table>

***

### When to contact Customer Success

{% tabs %}
{% tab title="Complex accessibility requirements" %}
Industry-specific compliance needs or advanced ARIA configurations
{% endtab %}

{% tab title="Expose mode strategy" %}
Deciding which accessibility attributes to make configurable vs. locked
{% endtab %}

{% tab title="Integration guidance" %}
Connecting accessibility features with your existing tools and workflows
{% endtab %}
{% endtabs %}

{% hint style="info" %}
If you encounter accessibility issues or have specific requirements, please contact your Customer Success Manager. We're committed to making Crobox Campaigns inclusive for all users.
{% endhint %}

### Best practices

{% tabs %}
{% tab title="Component Builder setup" %}

* Use sensible defaults that work for most use cases
* Only expose attributes that campaign editors need to customize
* Test default configurations with assistive technologies
  {% endtab %}

{% tab title="Campaign configuration" %}

* Provide clear, descriptive ARIA labels for your specific content
* Use meaningful alternative text that conveys purpose, not just description
* Test keyboard navigation and screen reader compatibility
  {% endtab %}

{% tab title="Content writing" %}

* Write clear, simple copy that's easy to understand
* Use descriptive headings and button text
* Avoid relying on color alone to convey information
  {% endtab %}
  {% endtabs %}

### FAQs

<details>

<summary><strong>Why don't I see accessibility fields in my campaign setup?</strong></summary>

Accessibility attributes must be "exposed" in Component Builder before they appear in campaign setup.

</details>

<details>

<summary><strong>Can I change the default ARIA role for components?</strong></summary>

Yes, but this is configured in Component Builder, not during campaign setup. Default accessibility settings can be defined in the Component Builder.

</details>

<details>

<summary><strong>What happens if I don't configure exposed accessibility fields?</strong></summary>

The campaign will use the default values set in Component Builder. Only modify exposed fields when your specific content requires different accessibility attributes.

If using a Custom Component, the ARIA attributes may need to be manually added. Contact Support for additional assistance where needed.

</details>