Legal

Accessibility

Flaux accessibility target, current improvements, known limitations and feedback process.

Effective date: August 2, 2026

Last updated: August 2, 2026

Commitment

Flaux is working toward WCAG 2.2 Level AA and regularly reviews the public website, dashboard and internal tools for accessibility barriers.

This statement does not claim formal certification or perfect conformance. It describes the current target, scope and review process.

Scope

The target scope includes flauxbot.com, dashboard.flauxbot.com, legal pages, login, server selection, dashboard pages, Chat Rewards, automation pages, analytics, settings, Premium and cookie consent controls.

The internal developer dashboard also receives core keyboard, focus, structure and contrast fixes even though it is restricted.

What Has Been Improved

The current pass adds a skip link, clearer legal page structure, a table of contents on legal pages, accessible cookie consent controls, persistent Cookie settings, improved main landmarks and reduced motion support for page entrance animation.

Core dialog components already include accessible names, Escape handling and focus behavior, and form field wrappers associate labels, hints and errors with controls.

Known Limitations

A full manual screen reader audit, high contrast audit, 400 percent zoom audit for every dashboard page and formal WCAG certification have not been completed in this repository.

Some provider hosted content, Discord avatars, external support pages and browser or Discord interfaces are outside Flaux's direct control.

Feedback Process

If you find an accessibility barrier, contact Flaux through the official support channel linked in the footer. Include the page, browser, assistive technology if relevant, and what you were trying to do.

Flaux will review reports, prioritize issues that block access to core functionality and communicate practical workarounds where possible.

Review Cadence

Accessibility should be reviewed when major dashboard features, navigation, legal pages or consent controls change. The internal checklist in docs/accessibility-checklist.md should be used for manual review.