> For the complete documentation index, see [llms.txt](https://support.pears.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.pears.io/updates/community-events-2026/event-accessibility-improvements.md).

# Event Accessibility Improvements

As of **January 22, 2026**, the public event registration site dynamically adjusts button text color based on the organization's theme color to ensure proper color contrast.

## What Changed

### More Flexible Color Scheme

The public event registration site previously displayed all buttons with white text regardless of the theme color. This could result in poor contrast for organizations using lighter theme colors.

The system now adjusts button text color automatically:

* **Dark themes** — White text on buttons
* **Light themes** — Black text on buttons

This ensures buttons remain readable across all theme configurations without requiring any action from event creators.

{% hint style="info" %}
**TIP:** Button text color is determined automatically based on the theme color set in Organization Settings. No manual configuration is needed.
{% endhint %}

## Related Documentation

* [Publish an Event](/plan/community-events/publish-an-event.md) — Configure the appearance of public-facing event pages


---

# 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, and the optional `goal` query parameter:

```
GET https://support.pears.io/updates/community-events-2026/event-accessibility-improvements.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.