Built to be used by everyone.

Last updated: October 9, 2026

We want pixelent.ai, and the front offices we build for clients, to work for people who use screen readers, keyboards, magnification or voice control. We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA.

What we do

• Semantic HTML with one main heading per page, labeled landmarks and a skip link.
• Every control reachable and usable by keyboard, with a visible focus outline.
• Text and controls designed for sufficient color contrast on both dark and light sections.
• Animations that stop when your device asks for reduced motion.
• Form fields with visible labels, and status messages announced to screen readers.
• Pixel, our chat agent, announces new messages to screen readers and closes with the Escape key.

How we test

We test with automated checks and by hand with a keyboard and a screen reader. We have not had a third-party accessibility audit, and we don't use overlay widgets.

Known limitations

• The calculators use sliders. Each one shows its value as text, and the analysis gives you the same numbers in a written report.
• Some third-party booking pages we link to are run by other companies and may not meet the same standard.

Tell us

If something doesn't work for you, email hello@pixelent.ai with the page and what happened. A person will reply, and we'll offer the information another way while we fix it.