Accessibility

Invoicing is not optional work. If you cannot use this site, you cannot get paid through it, so accessibility is a functional requirement rather than a nice extra. This page says where things actually stand, including the parts that are not good enough yet.

What we aim for

WCAG 2.2 Level AA, and the accessibility requirements of the European Accessibility Act. We have not commissioned an independent audit, so treat this as a self-assessment by the person who wrote the code, not a certification.

What is in place

• Every page is navigable by keyboard, and focus indicators are visible rather than styled away.
• Text meets AA contrast against its background. Small labels were specifically checked, because that is where contrast usually fails.
• Motion respects your system setting. If you have reduced motion enabled, the animated hero, the scroll reveals and the ambient background all stop, and the resting state of every animated element is the visible one, so nothing can leave content stranded invisible.
• Headings run in a real hierarchy, form fields have proper labels, and buttons announce their expanded or collapsed state where they toggle something.
• The layout reflows to narrow screens and survives zooming to 200% without content being cut off.
• Pages are server-rendered, so content is present without waiting on JavaScript.

Known weak spots

Being specific here is more useful than a blanket claim of compliance.

• The animated homepage hero. It is decorative and hidden from assistive technology, and it disappears entirely under reduced motion, but on a low-powered device it can still make the first paint feel heavy. Every other route uses a static backdrop.
• Generated PDFs. Invoice PDFs are not yet tagged for screen readers. The on-screen invoice is fully readable, so the information is always reachable, but the downloaded file is not as accessible as the page that made it. This is on the list to fix.
• Screen reader coverage. Testing has been done with keyboard navigation and automated tooling. It has not been through a full manual pass with JAWS, NVDA and VoiceOver, so real-world reports are genuinely valuable.
• Dense tables. The invoice list and reports carry a lot of columns, and while they are marked up correctly they are tiring to traverse cell by cell.

Telling us about a barrier

Email hello@invoiceforever.com or use the contact page. Tell us the page, what you were trying to do, and what assistive technology you use if that is relevant. It reaches a person directly and you will get a reply.

Accessibility problems are treated as bugs, not feature requests, and go to the front of the queue. If something blocks you from invoicing and the fix will take a while, say so and we will find you a way through in the meantime.

If we do not resolve it

If you have raised a barrier and are not satisfied with the response, you can escalate to the consumer protection or accessibility enforcement body in your own EU member state. We would much rather hear about it first and fix it.