Accessibility Statement

This statement says what has been checked on noiz.bio, how it was checked, and what is known not to work. It covers the pages and services we build and control on noiz.bio and our related subdomains: the marketing site, the dashboard, sign-in and our legal pages.

Noiz is run by one person. There is no accessibility department, no outside audit has been done, and nobody who relies on assistive technology has tested the product yet. What follows is what the code is held to by tests, and what a scripted check of the live site measured on September 21, 2026.

Creator profiles are different, and we want to be plain about it. A profile at noiz.bio/name is designed by the creator who owns it. They choose its colors, its background, its fonts and whether their card has a fill at all, and those choices are rendered exactly as made: we do not override them to meet a contrast target, because a control labeled "None" that still paints something is a control that lies. The result is that an individual profile may not meet WCAG 2.1 AA, and the accessibility of a profile is the responsibility of the creator who designed it. The editor shows a contrast reading beside the color controls so that choice can be an informed one.

The standard we measure against is the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA, plus the target-size criterion of WCAG 2.2. The European Standard EN 301 549 points to the same criteria for web content.

Three things happen, and each of them can be checked:

• Tests that run with every change. They hold properties of the code for good, and a change that breaks one cannot ship. Section 5 lists them
• A scripted check of the live site. A real browser tabs through the pages, measures the controls on a phone, and loads each page narrow and with reduced motion. Section 7 says how, section 5 what it found, section 6 what failed
• Barrier reports. They go to the address in section 10 and are read by the person who operates Noiz

The Web Content Accessibility Guidelines (WCAG) defines requirements for designers and developers to improve accessibility for people with disabilities. It defines three levels of conformance: Level A, Level AA, and Level AAA.

EN 301 549 is the standard behind the European Accessibility Act (EAA). Section 11 says how that law applies to Noiz.

Noiz relies on HTML, CSS, JavaScript and WAI-ARIA. Dialogs, menus, tabs, switches and selects are built on Radix UI primitives, which supply their keyboard behavior and their ARIA roles. Public pages are rendered on the server, so their text is in the document before any script runs; the dashboard needs JavaScript.

Browsers:

The checks in section 7 run in Chromium, the engine of Chrome and Edge. Firefox and Safari are not covered by them.

Held by tests that run with every change:

Measured on the live site on September 21, 2026:

The dashboard has a second script that fails any screen with text under 4.5:1 against its background, in both themes. It is run when the dashboard's look changes, not with every change. The marketing pages have no equivalent yet.

Known limitations, as of September 2026:

If one of these blocks you, or you meet a barrier that is not listed, section 10 says how to tell us.

The evaluation has three parts:

• Automated tests in the repository: they run with every change and hold the properties listed first in section 5. A change that breaks one does not ship
• A scripted check of the live site: a Chromium browser presses Tab through each page and compares every control focused and unfocused, measures every button, link and field at 390 pixels wide, loads each page at 320 pixels, loads it again with reduced motion requested, and reads each page's headings, landmark and language
• Reports: barriers reported by visitors and creators are acted on as they arrive, through the address below

Noiz is built on native HTML controls and WAI-ARIA, which is what screen readers, voice control, switch devices and screen magnifiers read. That is a design decision, not a test result: NVDA, JAWS, VoiceOver, TalkBack and Narrator have not been used on Noiz. They have not each been tested individually, and we would rather say so than list them as supported.

If one of them fails on a page we built, that is a defect. Please report it (section 10), and say which one and on which page.

Settings in your browser and system that Noiz responds to:

If you meet a barrier on Noiz, tell us. Reports are read by the person who operates Noiz, and a barrier on a page we built is treated as a defect:

If you are not satisfied with our response to your accessibility feedback, you have the right to file a complaint with the relevant authorities:

The numbers in sections 5 and 6 come from a script, so they can be measured again. When a release changes how the site is operated or perceived, the check is run again, the numbers here are replaced, and this statement is re-dated. A limitation that is fixed leaves section 6 in the same change that fixes it.

Beyond that there is no program, no schedule and no roadmap to promise: what is on this page is what exists.

Our platform may include content from third parties or user-generated content that is outside our control:

• User Profiles: Content created by users may vary in accessibility
• External Links: Links to external websites are not covered by this statement
• Embedded Media: Third-party embeds may have their own accessibility considerations
• Payment Processing: Stripe checkout pages follow their own accessibility standards

What a creator publishes is theirs. The one aid we give them is the contrast reading beside the editor's color controls.

For accessibility-related inquiries:

This statement was last updated on September 21, 2026.