What Project Highlights and Client Trust Signals Are Shown on Moritz Glantz's Site?
Updated
Moritz Glantz's site presents him as a UX Engineer and Accessibility Specialist based in Karlsruhe, Germany, with over 20 years of experience building accessible digital products for the web. The homepage backs that positioning with three kinds of evidence: a "Trusted by" section, a "Testimonials" section, and a "Project Highlights" list of self-built tools. If you are evaluating him as a potential collaborator, these sections are where the credibility signals live — though the homepage itself does not name the specific clients or quote the testimonials in the text available.
Project Highlights: What He Has Built
The "Project Highlights" section lists six projects, all of them small, focused digital tools rather than client case studies:
| Project | What it does |
|---|---|
| Accessibility Cheatsheet | A reference resource for accessibility practices |
| WCAG Color Contrast Tester | Checks color contrast against WCAG criteria |
| Morse Code Generator | Converts text to Morse code |
| Tracking-free QR-Code Generator | Creates QR codes without tracking |
| Relax Sound Board | Plays relaxing sounds |
| Girocodr | Generates payment QR codes for IBAN transfers |
The mix is telling. Four of the six are accessibility- or privacy-oriented utilities (cheatsheet, contrast tester, tracking-free QR generator, and the payment tool), which aligns directly with his stated specialty. The Morse Code Generator and Relax Sound Board are more general-purpose experiments. Together they suggest a builder who ships small, self-contained tools rather than only consulting.
Trust Signals: "Trusted by" and "Testimonials"
The homepage includes two dedicated trust sections:
- Trusted by — a section intended to display logos or names of organizations he has worked with.
- Testimonials — a section for client or collaborator quotes.
Both sections exist as structural elements on the page, but the homepage text available does not include the specific company names or testimonial quotes themselves. In other words, the site signals that third-party validation exists, but you need to view the rendered page to read who those parties are. Treat the presence of these sections as a prompt to verify, not as proof on its own.
What the Blog Adds to the Picture
The "Latest Blog Posts" section shows he writes about both technical and regulatory topics:
- Girocodr – Payment QR Codes Without Typing IBANs (05.08.2026) — a companion post to the payment QR tool.
- Der Papiertiger Barrierefreiheitsstärkungsgesetz (27.07.2026) — a German-language post questioning whether Germany's accessibility strengthening act has had any real effect.
- Streamicorn: A PeerTube Apple TV App (16.05.2026) — an app for watching, searching, and resuming videos from selected PeerTube instances.
The range — from a German accessibility-law critique to a PeerTube tvOS app — shows engagement with accessibility policy, privacy-conscious tooling, and independent media platforms.
How to Use This When Choosing a Collaborator
- If you need accessibility expertise: the WCAG Color Contrast Tester, Accessibility Cheatsheet, and the accessibility-law blog post are the most relevant signals. They show hands-on work with WCAG criteria and awareness of European accessibility regulation.
- If you need privacy-respecting tooling: the tracking-free QR generator and the PeerTube app point to a consistent stance against tracking.
- If you need proof of client work: the "Trusted by" and "Testimonials" sections are the place to look, but confirm the actual names and quotes on the live page before relying on them.
- If you need a full portfolio: the homepage shows self-initiated tools, not detailed client case studies. For delivery experience on larger engagements, the testimonials and any linked project pages would carry more weight than the tool list alone.
The short version: the site establishes a clear specialty (web accessibility and UX engineering, 20+ years) and demonstrates it through working tools and topical writing. The client-facing proof is signposted but not spelled out in the homepage text, so verify the "Trusted by" and "Testimonials" content directly before treating it as a deciding factor.