Accessibility Statement
Last audit: 2026-05-06 · Last update: 2026-05-07
Our commitment
CutOptim ("cutoptim.com", the "Service") is committed to making its website and web application accessible to as many people as possible, including people with disabilities. We work toward conformance with the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA, and we comply with the European Accessibility Act (EAA, Directive (EU) 2019/882) which entered into force on 28 June 2025.
Conformance status
CutOptim is partially conformant with WCAG 2.2 level AA. "Partially conformant" means that some parts of the content do not yet fully conform to the accessibility standard. We are actively working to remediate the known issues listed below. Public marketing pages, the authentication flow, the dashboard, and content pages (calculators and guides) currently meet the bulk of the AA criteria; the in-browser optimizer (the canvas-based 2D layout view) and PDF exports require additional work.
Non-accessible content
The following are known accessibility limitations as of the last audit: (1) PDF exports (cutting layout, cut-list, quotation) currently set document language but do not yet include tagged-PDF / PDF/UA structure (headings, paragraphs, tables marked up for assistive technology); (2) the 2D cutting layout is rendered on an HTML canvas without an equivalent screen-reader-accessible table mirror; (3) two modal dialogs (admin plan-override, app upsell) do not yet implement keyboard focus-trapping; (4) color contrast across our custom palette has not been formally audited yet, although Tailwind utility classes provide a generally accessible baseline; (5) the global prefers-reduced-motion respect is in place, but a per-component motion-safe migration is still pending. Remediation for each item is tracked internally and prioritized for the next 1-2 release cycles.
Recently improved
On 2026-05-06 we shipped a batch of accessibility improvements including: explicit label-input association on all authentication forms (login, register, forgot password); a keyboard-accessible "skip to main content" link on every page in all 8 supported languages; a global prefers-reduced-motion CSS reset that honors the operating-system "reduce motion" setting; and document-language metadata on all generated PDF exports so screen readers correctly identify the language.
Compatibility with assistive technology
CutOptim is designed to be compatible with the latest versions of major screen readers (NVDA, JAWS, VoiceOver) on Chromium-based browsers, Firefox, and Safari. Keyboard-only navigation is supported throughout the marketing site, authentication flow, dashboard, and content pages. The in-browser optimizer relies on form controls and buttons that are keyboard-accessible; the canvas visualization is currently visual-only (see "non-accessible content").
Compensation alternatives
If a feature is not yet accessible in a way that works for you, please contact us. We can provide: a text-only or screen-reader-friendly version of any cutting layout, cut-list, or quotation PDF on request, normally within 2 business days; verbal walk-through of the optimizer features; and assisted-account setup. There is no charge for these alternatives.
Feedback channel
If you encounter an accessibility barrier, or if you have a suggestion for improvement, please contact us at support@cutoptim.com with the subject line "Accessibility" so the message is routed correctly. You can also use the contact form at cutoptim.com/contact. We commit to acknowledging accessibility feedback within 5 business days and providing a substantive response within 30 days.
Enforcement procedure
In accordance with the European Accessibility Act, if you are unsatisfied with our response to an accessibility complaint, you may escalate the issue to the national authority responsible for accessibility enforcement in your EU member state. Each member state has designated a competent authority; the European Commission maintains an up-to-date list of these authorities on its disability rights pages.
Preparation of this statement
This statement was prepared on 2026-05-07. It is based on a manual code-level audit of the production codebase performed on 2026-05-05, supplemented by a smoke-test verification of the 2026-05-06 accessibility batch. The statement will be reviewed at least annually and updated after each major release that affects accessibility.
Changes to this statement
We may update this statement to reflect changes in the codebase, in the conformance status, or in the relevant legislation. The "Last update" date at the top of the page indicates when the statement was most recently revised.