简体中文
EnglishWebsite review
This review may include AI-generated content and is not individually verified. Domain, certificate and other facts come from the observed data on this page.
What is Moritz Glantz?
Moritz Glantz is a UX engineer and web accessibility specialist based in Karlsruhe, Germany, who presents himself as having over 20 years of experience imagining, shaping and building accessible digital products for the web. His site is both a professional profile and a personal workshop: he takes on client work, writes occasionally about accessibility and related topics, and builds small digital tools.
What the site shows
- A professional identity: accessibility and UX engineering are the core services, with a "Work with me" path for potential clients, plus "Trusted by" and testimonial sections.
- Project highlights: an Accessibility Cheatsheet, a WCAG Color Contrast Tester, a Morse Code Generator, a tracking-free QR-Code Generator and a Relax Sound Board.
- A blog: recent posts include Girocodr (payment QR codes without typing IBANs), a German-language piece questioning whether Germany's Barrierefreiheitsstärkungsgesetz has achieved anything, and Streamicorn, a PeerTube app for Apple TV.
Who it is useful for
The strongest fit is a product team, developer or designer who needs accessibility expertise and wants to judge that expertise before making contact. The tools are the practical proof: a WCAG color contrast tester is something a designer can open mid-task, and the accessibility cheatsheet works as a quick reference rather than a full course. The blog suits readers who want commentary on accessibility law and small, self-contained side projects rather than long tutorials.
A useful next step
If you are evaluating him for a project, start with the project highlights and one or two blog posts, then check whether the writing matches the kind of accessibility problem you have — for example, auditing a component library, fixing contrast and focus behavior, or preparing for European accessibility requirements. If you only need a quick check, the contrast tester and cheatsheet are the fastest entry points.
What accessibility and UX engineering services does Moritz Glantz offer for hire?
The site presents Moritz Glantz as a UX engineer and web accessibility specialist based in Karlsruhe, Germany, with over 20 years of experience shaping and building accessible digital products for the web. The hire offer is framed broadly—"Work with me"—rather than as a fixed menu of packages, so the practical read is a freelance or contract engagement covering accessibility and UX engineering work on web products.
What the page indicates you can hire him for
- Web accessibility work: auditing, remediation guidance, and building to accessible standards, given the stated specialization.
- UX engineering: turning design intent into working, accessible front-end implementations rather than design-only deliverables.
- Accessible product development: involvement from early imagining and shaping through to building, which suits teams needing accessibility expertise across a project lifecycle rather than a one-off check.
A "Trusted by" section and testimonials suggest client-facing project work, though the page evidence does not name the clients or describe specific past engagements. Treat the exact scope, formats (audit report, workshop, embedded engineering time) and rates as things to clarify directly.
The clearest signal of how he works
The project list is the most concrete evidence of his approach: an Accessibility Cheatsheet, a WCAG Color Contrast Tester, a Morse Code Generator, a tracking-free QR-Code Generator, and a Relax Sound Board. These are small, self-contained browser tools. For a prospective client, that pattern suggests someone who solves accessibility problems with practical, lightweight utilities—useful if you want a partner who can build internal tooling or prototypes, not only produce documentation.
Who this fits
| Your situation | Likely fit |
|---|---|
| Team with an inaccessible product needing fixes and guidance | Strong—accessibility is the stated core specialty |
| Design team needing accessible front-end implementation | Strong—UX engineering is the second core specialty |
| Wanting a large agency with many parallel workstreams | Less clear; this reads as an individual practitioner |
| Needing purely visual/brand design | Not indicated on the page |
Next step
Before reaching out, write a short brief: the product, the standards you must meet (for example WCAG 2.2 AA), whether you need an audit, remediation, or ongoing engineering, and your timeline. That lets a specialist respond with a concrete scope rather than a general availability note. If your work touches German or EU accessibility requirements, his base in Germany and German-language blog posts are worth noting as a practical advantage for regulatory context.
What is the Accessibility Cheatsheet and how can it help me build accessible websites?
The Accessibility Cheatsheet is one of the tools Moritz Glantz lists under Project Highlights on Moritz Glantz, the site of a Karlsruhe-based UX engineer and accessibility specialist. It is a reference resource: instead of reading long WCAG documentation, you keep a condensed sheet of the rules and patterns you need while writing markup, reviewing components or checking a design. The site presents it alongside other small utilities such as a WCAG colour contrast tester, a tracking-free QR code generator and a Morse code generator, so it fits the pattern of practical, self-contained aids rather than a full auditing platform.
How it fits into a real workflow
A useful way to think about a cheatsheet is as a first-pass tool, not a verdict. It helps you remember requirements early — when you are choosing heading levels, labelling a form field, or deciding whether a custom widget needs keyboard handling — so fewer issues reach review. It cannot tell you whether your specific page passes, because that depends on your content, your components and how assistive technology actually behaves in context.
Concrete uses:
- During development: keep it open as a quick reminder of success criteria and common patterns while writing HTML and ARIA.
- During design review: check contrast, focus order, target sizes and text alternatives before a component is built.
- During onboarding: give new team members a short shared vocabulary for accessibility instead of pointing them at the full specification.
- During handover: use it as a checklist when a feature moves from design to code to QA.
What it does not replace
For a definitive audit, combine a cheatsheet with automated testing and manual checks with a keyboard and a screen reader. Automated tools catch only part of the problem set; a cheatsheet is only as good as the discipline of the person applying it. If your organisation needs formal conformance, the authoritative source remains the W3C's own guidance at W3C.
A practical next step
Pick one page you own and run it against the cheatsheet categories you find hardest — usually forms, dynamic content or custom widgets. Fix what you find, then verify with a keyboard-only pass and one screen reader. That cycle teaches more than reading any single reference end to end.
How does the WCAG Color Contrast Tester work and why should I use it?
The WCAG Color Contrast Tester on Moritz Glantz is a small browser-based tool for checking whether a foreground/background color pair meets the WCAG contrast thresholds. You enter or pick two colors, and it calculates the contrast ratio between them and tells you how that ratio maps to the WCAG success criteria. The site lists it among other small utilities such as an accessibility cheatsheet, a Morse code generator, and a tracking-free QR-code generator, so it is positioned as a quick, focused helper rather than a full design system.
What it does in practice
- Computes the contrast ratio from the relative luminance of the two colors, which is the same math the WCAG guidelines use.
- Reports whether the pair passes the normal-text and large-text thresholds, and the non-text/UI-component threshold.
- Lets you adjust colors and see the result immediately, so you can nudge a shade until it passes rather than guessing.
Why it is worth using
Contrast is one of the most common accessibility failures on real sites, and it is also one of the cheapest to fix. A tester like this gives you a yes/no answer before a design reaches review, a client, or production. It is useful when you are:
- Choosing link, button, or form-border colors against a background.
- Checking placeholder text and disabled states, which often sit just below the required ratio.
- Reviewing a brand palette that was approved visually but never measured numerically.
- Verifying text over images or gradients, where you need to test the lightest and darkest parts separately.
How it fits with other tools
The tester answers a single question well. For broader audits you would pair it with a browser extension or automated scanner, and for manual checks you would still test focus visibility, keyboard order, and screen-reader output. The site’s own accessibility cheatsheet is the natural companion for those wider checks.
A practical next step: pick the three color pairs you use most often — body text on background, link on background, and button label on button fill — run each through the tester, and note the ratios. If any fall short, adjust the lighter or darker color by a few percent and re-test. That small loop usually resolves the majority of contrast issues before they ever reach a user.
What are the tracking-free QR-Code Generator and Morse Code Generator used for?
Both are small, single-purpose browser tools on Moritz Glantz. They solve narrow, practical problems rather than offering a general utility suite.
Tracking-free QR-Code Generator
This creates QR codes without the analytics, redirect layers or account requirements common to many free generators. That matters when the code points somewhere sensitive or permanent: a Wi-Fi password for guests, a link printed on a poster or business card, a payment or contact detail, or an internal URL. A code you generate once may stay in the physical world for years, so avoiding a third-party redirect that could later expire, change destination or collect scan data is a real advantage.
Typical users are privacy-conscious individuals, small businesses, event organisers and anyone printing codes where they cannot easily reprint them. The trade-off is that tracking-free tools usually skip the features hosted services bundle in — scan counts, dynamic destination editing and campaign dashboards. If you need to change where a printed code points after the fact, a static generator will not do that; you would need a redirect service, which reintroduces the tracking question.
Morse Code Generator
This converts text to Morse code (and often back again). It is useful for learning and practising the code, preparing amateur radio transmissions, creating puzzle or escape-room material, teaching signalling history, or producing audio and visual patterns for games and props. Hobbyist radio operators, teachers, students and makers are the natural audience.
Its limitation is scope: a generator handles encoding and playback, not the skill of copying Morse by ear at speed. For serious radio use, expect to pair it with dedicated practice software or on-air time.
How to choose between them
| Need | Better fit |
|---|---|
| Printable code with no third-party dependency | Tracking-free QR-Code Generator |
| Learning, teaching or props involving dots and dashes | Morse Code Generator |
| Scan analytics or editable destinations | Neither — use a hosted dynamic QR service |
A useful next step: before generating a QR code, decide whether the destination will ever need to change. If the answer is no, a static, tracking-free code is the safer long-term choice; if yes, plan for a redirect service and accept its trade-offs.
What topics does Moritz Glantz cover in his blog posts?
Moritz Glantz's blog covers web accessibility and UX engineering, with posts that range from legal and policy commentary to practical tools and open-source app development. The site describes him as a specialist for web accessibility and UX engineering with over 20 years of experience, and the blog reflects that mix of hands-on building and critical analysis.
Recurring themes
- Accessibility law and policy. One post examines Germany's Barrierefreiheitsstärkungsgesetz (Accessibility Strengthening Act), asking whether the law has actually delivered improvements. This suits readers who need to understand compliance obligations or want a skeptical take on whether regulation changes real-world accessibility.
- Practical payment and utility tools. A post on "Girocodr" covers generating QR codes for IBAN bank transfers, so people can pay without typing long account numbers. That is useful for anyone building or choosing lightweight payment helpers, and it shows an interest in reducing friction in everyday digital tasks.
- Open-source media and streaming. A post on "Streamicorn," a PeerTube app for Apple TV, covers watching videos from selected PeerTube instances, searching, and resuming playback. This appeals to people interested in federated, non-corporate video platforms and living-room viewing.
- Accessibility tooling. The project highlights list an accessibility cheatsheet, a WCAG color contrast tester, a Morse code generator, a tracking-free QR code generator, and a relax sound board. These are small, focused utilities rather than large products, which suggests the blog favors concrete, self-contained solutions over broad theory.
How to use this
If you are deciding whether to follow the blog, match it to your role. A front-end developer dealing with contrast ratios and WCAG checks will get the most from the accessibility tools and law commentary. Someone interested in independent, privacy-respecting media or payment tools will find the app posts more relevant. For a broader view of professional web accessibility practice, you can also compare with established resources such as W3C Web Accessibility Initiative or The A11y Project. A useful next step is to open the blog index and read the Barrierefreiheitsstärkungsgesetz post first if you work in a German context, since it frames the legal side that the tools then support.
Germany
User reviews (0)