mirror of https://github.com/formbricks/formbricks.git synced 2026-05-18 06:52:01 -05:00

Files

T

Matti Nannt 2db02dac5e docs: add ACCESSIBILITY.md and accessibility issue template (#8019 )

Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>

2026-05-15 09:53:23 +00:00

2.3 KiB

Raw Blame History

Accessibility

Formbricks is committed to making our platform usable by everyone, including people who rely on assistive technologies.

Standards

We aim to conform to:

WCAG 2.1 Level AA — the web content baseline.
EN 301 549 — the European harmonised standard referenced by the European Accessibility Act (EAA), applicable to us as a Germany-based company.
Section 508 — for users in US public-sector contexts.

Priorities

End-user surveys (packages/surveys) — everything respondents see and interact with. This is our highest priority because survey takers don't choose Formbricks; the organisations running surveys choose for them.
Admin app (apps/web) — survey creation, response analysis, and team management used by Formbricks customers.

In both areas we focus on:

Keyboard navigation with a clearly visible focus indicator
Screen reader support through semantic HTML and correctly scoped ARIA
Sufficient color and contrast
Programmatically associated labels and announced status messages

Supported Environments

Latest two versions of Chrome, Firefox, Safari, and Edge
VoiceOver (macOS/iOS), NVDA (Windows), and TalkBack (Android)

Contributing

When contributing UI changes:

Prefer semantic HTML over ARIA.
Tab through your change end-to-end and confirm focus is visible at every stop.
Label every control. Don't convey meaning by color alone.
Run axe DevTools or Lighthouse on the page you changed.

Reporting Accessibility Issues

If you encounter an accessibility barrier, please open an issue using the accessibility template. For blocking issues in a procurement or compliance context, email hola@formbricks.com.

2.3 KiB Raw Blame History