1. Our commitment

Firelent’s promise is that anyone can build for the web — and that has to include people who navigate it with a keyboard, a screen reader, reduced motion or high contrast. We design toward WCAG 2.1 level AA for firelent.com and the studio, and we treat the German Barrierefreiheitsstärkungsgesetz (BFSG), in force for consumer digital services since June 2025, as the bar our product has to meet — not a formality to disclaim.

2. What we practice

• semantic structure and labeled controls, so assistive technology gets real information, not styled rectangles;
• keyboard reachability for the studio’s core workflows;
• contrast-checked text on our marketing and product surfaces;
• motion used deliberately — and reduced where your system asks for reduced motion;
• accessibility review as part of design work, not a patch after launch.

3. Honesty about the current state

Parts of our marketing pages are animation-heavy, and some studio panels are still on their way to full keyboard and screen-reader parity. We would rather name that than publish a perfect-sounding statement. Accessibility work is ongoing and prioritized alongside features, and this page will track the state as it improves.

4. Sites built with Firelent

The sites and apps our customers publish are theirs, including their accessibility obligations toward their own audiences. Our part: the components and pages Firelent generates are built to be accessible by default — semantic markup, alt text prompts, contrast-aware themes — so that the easy path is the accessible one. Where a customer’s market imposes specific requirements (for example the BFSG or the European Accessibility Act), meeting them remains the customer’s responsibility.

5. Tell us where it fails

If you hit a barrier anywhere on Firelent — a control you cannot reach, a contrast that fails you, a flow that traps a screen reader — write to support@firelent.com with the page and what happened. Accessibility reports are triaged as bugs, not feedback.