Our Commitment

Name Font Style (namefontstyle.co.uk) is a free collection of fancy font generators, name styles and symbol tools. We believe creative tools should be open to everyone, so accessibility is part of how we design and build every page — not something added at the end.

This statement applies to all pages on namefontstyle.co.uk, including our font generators, symbol pages, articles and legal pages. It was prepared on 31 October 2026.

The Standard We Follow

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. These guidelines, published by the World Wide Web Consortium (W3C), explain how to make web content more accessible to people with disabilities, and are built around four principles:

As a UK website, we also keep in mind our duties under the Equality Act 2010 to make reasonable adjustments for disabled people.

Compliance Status

We believe namefontstyle.co.uk is partially compliant with WCAG 2.2 level AA. Most of the site — navigation, articles, buttons, forms and layout — is designed to meet the standard. The main exception is the nature of the fancy text our tools create, which we explain honestly in the next sections.

What We've Done

Here are the accessibility features built into our pages and tools.

1. Keyboard Access. Every input, tab, Copy button, favourite star and FAQ can be reached and used with a keyboard. Focus moves in a logical order.
2. Real Buttons And Labels. We use standard HTML buttons and labelled inputs, so screen readers announce what each control does.
3. Clear Structure. Pages use proper headings, a table of contents and landmark navigation so you can jump straight to the section you need.
4. Live Announcements. When styles update or text is copied, results and the "Copied" message use live regions so screen reader users get feedback.
5. Colour Contrast. Our dark ink text on a cream background, and our button colours, are chosen to give strong contrast.
6. Reduced Motion. If you've turned on "reduce motion" in your device settings, our animated ticker and title animations stop.
7. Zoom And Reflow. Pages can be zoomed to 200% and reflow on small screens without horizontal scrolling for normal content.
8. Mobile Friendly. Large tap targets, readable font sizes and tables that turn into easy-to-read cards on phones.
9. No Time Limits. Nothing on the site times out or requires you to act within a set time.
10. Plain Language. We write in plain British English and explain technical terms such as Unicode.

Fancy Text And Screen Readers

Our tools don't change your font. Instead, they swap normal letters for look-alike Unicode characters — for example, "a" becomes 𝒶, 𝐚 or ⓐ. This is what lets fancy text work on Instagram, TikTok and WhatsApp, but it has an accessibility cost.

Screen readers may read these characters by their technical names (such as "mathematical bold small a"), spell them out, or skip them entirely. Combining marks used for underlines or glitch text can also be announced or ignored, and emoji are read aloud by name. Search engines and in-app search may not recognise fancy text as normal words.

We encourage everyone using our generators to style names and short phrases, and keep important details — dates, links, prices and hashtags — in plain text so all readers can understand them.

Known Limitations

We know some parts of the site are not yet fully accessible. These are the main issues we're aware of:

1. Generated Fancy Text. As explained above, the styled text in our results grids and previews may not be read clearly by screen readers. The style name above each result is always in plain text.
2. Large Results Grids. Some tools show hundreds of styles. We load them in batches with a "Load more" button and offer search and category tabs, but browsing many results with a screen reader can still be slow.
3. Decorative Symbols. Example chips and A–Z tables contain symbols and fancy letters that may be announced in unusual ways.
4. Multi-Line Banners. Big ASCII-style banner text is visual art and isn't meaningful when read aloud.
5. Older Devices. Some newer Unicode characters may show as empty boxes on older phones or browsers.
6. Third-Party Content. Advertising, embedded content or services provided by third parties may not meet the same standard, and we don't have full control over them.

We're working to improve these areas and will update this statement as we do.

Tips For Using Our Tools

AbilityNet's My Computer My Way has free, step-by-step guides to making your device easier to use, including changing colours, text size and using your device with a keyboard or voice.

Compatibility And Technology

Our site is built with standard HTML, CSS and JavaScript. It's designed to work with recent versions of popular browsers — Chrome, Safari, Edge and Firefox — on Windows, macOS, iOS and Android, and with common assistive technologies such as VoiceOver, TalkBack, NVDA and JAWS.

Our font tools need JavaScript to generate styles. The articles, guides and legal pages can be read without it.

Feedback And Contact

If you find something on namefontstyle.co.uk that's hard to use, or you need information in a different format, please tell us. We read every message and aim to reply within 5 working days.

If You're Not Happy

If you contact us about an accessibility problem and you're not happy with our response, please reply and ask for it to be looked at again. If you still feel the issue hasn't been resolved, the Equality Advisory and Support Service (EASS) offers free advice in England, Scotland and Wales. In Northern Ireland, you can contact the Equality Commission for Northern Ireland.

How We Test And Review

We check new pages and tools before they go live using a mix of methods:

1. Keyboard Testing. Moving through every control using only a keyboard.
2. Screen Reader Checks. Spot-checking key pages with built-in screen readers on phones and computers.
3. Automated Tools. Running browser accessibility checkers to catch contrast, label and structure issues.
4. Zoom And Mobile Testing. Checking pages at 200% zoom and on small phone screens.

This statement was prepared on 31 October 2026 and was last reviewed on 31 October 2026. We plan to review it at least once a year, and whenever we make major changes to the site.