Accessibility
Last updated
This page has an awkward job, because the product has a real accessibility problem and pretending otherwise would be worse than admitting it.
The problem with what this site makes
Styled Unicode characters are not accessible. A screen reader reads a character's Unicode identity, and these characters are mathematical symbols rather than letters, so 𝐴 is announced as "mathematical italic capital a", not as "A". A styled sentence becomes a recitation of character names with the meaning buried inside it. Some readers skip the characters entirely instead, which loses the words altogether.
This is not a bug that will be fixed. The screen reader is behaving correctly; these genuinely are mathematical symbols, encoded so a physics paper could distinguish a bold vector from an ordinary variable. Unicode's own documentation recommends against using them in general text as a substitute for real formatting.
We say this on the style pages, in the guides, and in the bio builder, which warns you when every line of a bio is styled.
What follows from it
The advice we give, consistently: anything a person needs in order to act should be in plain characters. A username someone has to find. A date. A price. An instruction. Decorative styling is for the parts of your text where appearance matters more than certainty, and that is a smaller set than it first appears.
Three styles here are exceptions. Strikethrough, underline and slash through work by attaching a mark to your original letters rather than replacing them, so the text underneath stays intact: searchable, and read as real words by a screen reader. They are the only accessible decorative option on the site, which is not something you would guess from how such tools are usually presented.
The site itself
Separately from what it produces, the site is built to be usable:
- Every interactive control is reachable and operable by keyboard, with a visible focus outline
- Copy actions announce their result to screen readers through a live region
- Tap targets are at least 44 by 44 pixels
- Text contrast meets WCAG AA against its background
- `prefers-reduced-motion` is respected; there is very little motion to begin with
- The layout works from 320 pixels wide upward and reflows without horizontal scrolling
- Headings follow a correct outline, and landmarks are marked up so a screen reader can skip between sections
- Nothing depends on colour alone; the platform-support indicators carry text labels as well as colour
Known gaps
- The symbol grids are long. Keyboard users must tab through many buttons to reach the end of a category, and there is no skip-within-grid control yet.
- Some symbols render as empty boxes on devices lacking the relevant font. That is a device limitation rather than a site fault, but the effect on a user is the same.
Telling us about a problem
If something here does not work with your assistive technology, the contact page will reach the person who built it. Include what you were using. That detail is usually the whole diagnosis.