Accessibility
Updated
Fakenamely should work for everyone: with a keyboard, a screen reader, a phone, or the page zoomed in. The target is WCAG 2.2 level AA. This page says what has been checked, and what has not.
How the site was checked
On 17 November 2026 we ran an automated audit with axe-core 4.10.2 on 24 pages that cover the main page layouts on the site, at a desktop width of 1280 pixels and a phone width of 390 pixels. The rule set was WCAG 2.0, 2.1 and 2.2 at levels A and AA.
- Automated rules: every page passes the axe-core rules for WCAG 2.0, 2.1 and 2.2 at levels A and AA, at both widths.
- Colour contrast: axe-core found no text below the WCAG AA contrast minimum on any page. It could not measure some text, such as the cookie banner, which sits on top of the page, and it does not test the borders of controls or icons.
- Structure: each page has one main heading, no heading is empty and no heading level is skipped.
- Reflow: no page scrolls sideways at 320 pixels wide.
- Skip link: the first Tab stop on every page is a "Skip to content" link, and it moves focus to the content.
What the audit found
The first run did not pass, and every problem it found was fixed the same day before this page was published. A second run of the same script passed on all pages. This is what the first run found:
- Low-contrast text on all 24 pages. Grey secondary text measured between 4.34 and 4.47 to 1 on the site's tinted panels, the green "Fictional test data" line 3.17 to 1, and the breadcrumb links 2.56 to 1. All three colours were darkened.
- Code samples and wide tables that scroll sideways could not be scrolled with a keyboard on five of the pages. They can now take keyboard focus.
- Two pages scrolled sideways on a 320-pixel screen: the New York address page, because of a wide table, and the API page, because of a long link label.
Before the audit there was no way to skip the header with a keyboard. A skip link was added to every page, and the audit now checks it.
What is not covered yet
- No pass with a screen reader has been made yet. Automated rules catch only part of what a screen reader user meets.
- Keyboard use was checked only for the skip link and for scrollable regions. Menus, buttons and form controls have not been tabbed through page by page.
- The audit covered 24 pages that use the main layouts, not every page. The press kit, the practice pages, the licence and terms pages and the smaller generators were not in it, and a problem on a single page may have been missed.
- Text the tool could not measure, such as the cookie banner, has not been measured by hand.
- Advertising, when it is shown, comes from Google AdSense. We cannot fully control what an ad contains.
Pages in the audit
- Profile generator (home page)
- Fake name generator
- Random address generator
- UK phone number generator
- A country page (Germany)
- A US state page (California)
- A city address page (New York)
- A single-field generator (phone number)
- Username generator
- A browser tool (password generator)
- Bulk export
- API documentation
- Country directory
- Sample customer dataset
- Guides index
- A guide (most common last names)
- FAQ
- About
- Data and methodology
- Responsible use
- What's new
- This statement
- Privacy policy
- Contact
Tell us about a problem
If something on the site is hard to use, email hello@fakenamely.com with the address of the page and what happened. We will fix what we can, and help you get the data you need in the meantime. Fixes are recorded in the change log.