Skip to content
TAA

Article

Three Sites, One Audit: Accessibility and Voice

This week I ran a deep accessibility and copy audit across three static sites, fixing contrast ratios, touch targets, and first-person voice throughout.

, Marcel R. G. Berger, 6 min read

  • hire app developer
  • build-in-public
  • astro
  • accessibility
  • static-site
  • solo-developer
Share

No app release this week. No new version number to point at. What I shipped instead was a concentrated audit across three static sites built on Astro, fixing things that had been quietly wrong for a while: contrast ratios that failed WCAG AA, touch targets too small for a thumb, and copy that kept saying “we” when it should have been saying “I”. Not glamorous. But the kind of work that matters if you want to hire an app developer whose own sites hold up under scrutiny.

The Audit: What I Actually Fixed

Contrast, Touch Targets, and Semantic Markup

The accessibility pass touched all three sites. The pattern was the same everywhere: things that looked fine visually turned out to fail when I ran them through a contrast checker or measured the tap areas in the browser DevTools.

The most concrete example was an accent colour that had been sitting at a 4.04:1 contrast ratio against white text. That passes WCAG AA for large text but fails for body-sized text and interactive elements. The fix was to shift the hue slightly to #CC2162, which brings the ratio to 5.30:1 and stays above 4.5:1 even on hover states. One hex value changed, contrast problem gone. That sounds trivial. It took me longer than I want to admit to find the right value that worked in both light and dark contexts without looking wrong.

Touch targets on mobile were another recurring issue. Footer links and language-switcher buttons were rendering at around 32 pixels tall on small screens. Apple’s Human Interface Guidelines say 44 by 44 points as a minimum. Android’s Material guidance says the same. I had followed this rule in the app UIs I build, and then ignored it on my own web properties. I set a minimum height of 44 pixels on every interactive element in the footer and header across all three sites. The fix itself is three lines of CSS per site. Finding every element that needed it was the actual work.

The navigation landmark was missing a label on one site. The header was wrapped in a <nav> tag but had no aria-label. Screen readers announce it as “navigation”, which is fine until there are two navigation regions on the same page. Adding aria-label="Main navigation" costs nothing and removes the ambiguity.

Alt text on video thumbnails was another gap. The thumbnails had empty alt attributes, which means a screen reader user gets no information about what the video contains. I pulled the alt text from the video title, stripped the hashtags that had leaked in from the source data, and applied the correct label pattern in German and English separately. In German the word is “Vorschaubild”, in English “Thumbnail”. Small detail, but getting it right in both languages matters when the site serves both audiences.

Voice: From “We” to “I”

This one surprised me a little when I found it. Several pages on two of the sites were written in first-person plural. “We build”, “our approach”, “we believe”. That copy had been there for a while and I had stopped seeing it.

The problem is that it is simply not accurate. I work alone. There is no “we”. When a business owner reads “we offer” on a one-person consultancy site, and then later finds out it is one person, that feels like a small misdirection even if it was never intentional. I went through every page where the provider voice was involved and rewrote it in first-person singular. Customer-facing questions (“how do we start?”) and shared-journey language stayed as they were, because “we” there refers to the client and me working together, which is accurate.

The German versions needed the same treatment, and German makes this slightly more fraught because the formal “Sie” address and the first-person “ich” have to coexist correctly. A sentence like “Wir entwickeln Ihre App” becomes “Ich entwickle Ihre App”. Grammatically simple. But you have to read every sentence in context to make sure the subject is actually the provider and not some shared “we” that makes sense to keep.

I also updated how the GitHub data fetching logic on this site counts open-source repositories. The original query listed any public repo with a licence file. That was wrong. One of the apps I ship has a proprietary end-user licence agreement, not an open-source licence. The fix was to count only repositories with a proper SPDX licence identifier on the OSI-approved list. One conditional check, but it means the number shown on the site is now accurate.

Domain Migration: Canonical URLs and OG Images

The third site also went through a domain change this week. The canonical domain shifted, which means the CNAME record, the site field in the Astro config, all JSON-LD structured data, the FAQ answers, robots.txt, and llms.txt all needed updating to the new domain. Email addresses deliberately stayed on the old domain because those are not affected by the web canonical.

The open-graph image also needed to be regenerated with the new domain baked in. OG images on this site are generated at build time from a template, so regenerating meant updating the base URL in the config and triggering a fresh build. The image itself did not change visually, just the embedded URL metadata.

I will be honest: this is the kind of migration that looks like a five-minute find-and-replace until you start doing it. JSON-LD in particular sits in multiple files across multiple page templates, and each one has to be checked individually because the structure is not always identical. I caught one instance I had missed on the first pass only because I ran a grep across the whole repo before pushing.

An Honest Note on This Kind of Week

Weeks like this one are useful but not satisfying in the way a shipped feature is satisfying. I fixed real problems. The contrast ratios are better. The touch targets are correct. The copy is honest. None of it shows up in a version number.

What it does show up in is the quality of the foundation. If you are considering having a custom app or site built, the boring stuff matters: accessibility compliance, accurate structured data, honest copy, correct canonical URLs. Those are not afterthoughts. They are part of what a site is supposed to do.

If that kind of attention to detail is what you are looking for, you can read more about how I work on the services page or reach out on the contact page.

The portfolio site at marcelrgberger.com now correctly routes business enquiries to The App Architect contact page, in both the desktop navigation and the mobile header.

Share