Accessibility Statement

AnvilGen is operated by Marks Tarasovs, trading as AnvilWorks, in Latvia. We want the Service to be usable by as many people as possible, including people who rely on screen readers, keyboard navigation, captions, magnification, or reduced motion. This statement applies to the website at anvilgen.ai and the signed-in app under anvilgen.ai/app.

We work to the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA, the standard referenced by the Americans with Disabilities Act (ADA) in the United States and, through EN 301 549, by the European Accessibility Act.

Conformance status: partially conformant. Most of the website and app meet the standard; the parts that do not yet are listed in section 4. We say “partially” because that is the honest position for a young product, not because accessibility is optional to us.

• Every page declares its language and uses a logical heading structure that screen readers can navigate.
• All controls can be reached and operated with a keyboard, and keyboard focus is shown with a visible ring on every focusable element.
• Images that carry meaning have text alternatives; decorative images are hidden from assistive technology.
• Buttons, links, and form fields have accessible names, with ARIA labels wherever the visible text alone is not enough.
• Text is sized in relative units and the layout reflows without horizontal scrolling down to a 320-pixel-wide screen and at 200% zoom.
• Motion is reduced or removed for anyone whose device asks for reduced motion (the operating-system “reduce motion” setting).
• Success and error states are conveyed in text, not by color alone.
• Videos the Service produces can include captions, generated from the spoken audio and shown on screen, so your own viewers benefit too.

The following areas are not yet fully accessible. For each we say what to do in the meantime and what we plan.

• No skip-to-content link. Keyboard users tab through the navigation on each page before reaching the content. Workaround: use your browser’s heading navigation or find-in-page. Planned: a skip link at the top of every page.
• Analytics charts. The YouTube analytics graphs are visual; the key figures are also available as plain numbers and in the written summary, which is the accessible route. Planned: a data-table view of each chart.
• Third-party windows. The Stripe checkout and billing portal, and the cloud browser used to connect a HeyGen subscription, are built by those providers and follow their accessibility support, not ours.
• AI-generated images. Thumbnails and presenter images made by the Service are described by their role (for example “thumbnail for video X”), not by their visual content, because no reliable description of a generated image exists yet.
• Video previews play without an audio description track.

The Service is built to work with the current and previous major version of Chrome, Edge, Firefox, and Safari on desktop, and Safari and Chrome on iOS and Android, including their built-in zoom and reduced-motion settings. It is designed to work with screen readers that follow the ARIA standard (such as NVDA, JAWS, and VoiceOver). The Service depends on JavaScript and does not work with it disabled.

Accessibility relies on standard HTML, CSS, WAI-ARIA, and JavaScript, used in the ways the WCAG techniques recommend. We do not use an accessibility overlay or widget; those tools mask problems rather than fix them, and we prefer to fix the code.

This statement is based on a self-assessment carried out on the date shown above, using automated accessibility checks and a review of the site’s code against the WCAG 2.1 AA criteria. It has not yet been audited by an independent third party or tested with a panel of assistive-technology users. We repeat the assessment when we ship significant changes, and at least once a year, and we update this statement to match.

If you hit something you cannot use, or need any information from the Service in a different format, email AnvilWorksYT@protonmail.com with the page address, what you were trying to do, what happened, and the browser and assistive technology you use. We aim to reply within five business days, to give you a way through in the meantime, and to prioritize a fix. Reports of barriers are treated as bugs, not requests.

If we have not resolved your report, you can escalate it. In the European Union, the accessibility of services like this one is overseen by the market-surveillance authority in each country; in Latvia that is the Consumer Rights Protection Centre (Patērētāju tiesību aizsardzības centrs) at ptac.gov.lv. Nothing in this statement limits any right you have under the accessibility or disability law of your own country.

We update this statement as our conformance changes, and the date at the top always shows the latest version. If you want to know whether a specific limitation has been fixed, ask us.