# 1.0.32

- Link: https://blog.curbsoftware.com/changelog/v1-0-32/
- Published: 2026-09-14T06:10:00+00:00
- Author: curbsoftware

## Summary

Six things a person can see, fixed. The composer’s body was unnamed to a
screen 
reader, the app could not be installed from a phone, filled buttons lostcontrast
when hovered, contact initials were hard to read, a Settings link wastoo small to
hit, and on hosts behind a long-caching CDN a bad cached file couldleave the More
screen showing an error. Each edition also gets its owntranslation template, and
bundled translations return.

## Added

 * The app can be installed from a phone again. The web app manifest declared an

SVG, a 32×32 and a 180×180 icon, and neither size Android requires to offer an
install
at all. It now ships 192×192 and 512×512, so a whitelabelled site andthe default
branding can both be installed.

 * The Free package ships its own translation template. One template served both

editions, so a Free translator was offered about 1,640 strings that no Free
site
can render, from files the Free download does not contain.

 * Bundled translations are back for the eight locales the interface ships in,

covering the core screens. WordPress.org language packs still load when
available.

## Changed

 * Filled buttons stay readable while you point at them. They used to lighten on

hover, which on a light label means losing contrast: the Compose button went
from
5.06:1 to 3.48:1, under the 4.5:1 floor, so it was least readable exactlywhen it
was being aimed at.

 * Contact initials are legible. The avatar drew a saturated colour on a 16% tint

of itself, which across the eighteen flag colours ranged from 1.73:1 to
3.90:1 against
the same 4.5:1 floor.

 * The System Health card’s link to WordPress Site Health meets the 24px minimum

pointer target.

## Fixed

 * The message body has an accessible name. It was a contenteditable region with

no label, so a screen reader announced it as an unlabelled text box: the one
control
every user types into was the only one in the product without a name.

 * A stale cached copy of the application bundle can no longer break a screen. The

entry chunk had a fixed filename while a long-caching CDN was set to keep it,
so
a browser could run the previous release’s bundle, ask for scripts that nolonger
existed, and show a fetch error where the More screen should be.

 * The bundled icons are served with a version, so redrawn artwork actually

reaches people.

 * JavaScript translator notes reach translators; the extractor was discarding

them, so a string with a placeholder arrived with nothing explaining it.

 * The free build no longer ships a stale copy of the interface: twenty-one

modules that nothing reached have been removed.

## Upgrade Notes

 * Nothing to do. Bundled translations return automatically, and where a

WordPress.org language pack exists for a locale the pack continues to take
precedence.
