Contact & feedback

Tell us what isn't working.

Feedback is part of the evidence. You do not need to know accessibility terminology or identify a WCAG criterion before reporting a problem.

Report an accessibility barrier on No Default

If something on this site is difficult or impossible to use, tell us what you were trying to do and what happened.

Useful details, if you know them, include:

the page or exercise;
what you expected to happen;
what happened instead;
device and browser;
assistive technology or accessibility settings you were using, if relevant.

You do not need to diagnose the cause. “I couldn't dismiss the keyboard and reach the rest of the exercise” is a useful accessibility report.

Correct or challenge something

No Default discusses standards, testing practice and people's experiences. If a claim is inaccurate, outdated, overgeneralised or poorly framed, please challenge it.

When possible, include the page, the specific statement and a source or explanation for the correction. First-person experience does not require a citation to be worth hearing.

General feedback

Suggestions about missing barriers, confusing explanations, useful Lab ideas and other feedback are welcome too.

What would you like to tell us? An accessibility barrier on No Default A correction or challenge to the content General feedback or suggestion

Page or URL (optional)

What were you trying to do? (optional)

What happened, or what would you like us to know?

For an accessibility report, describe the barrier in your own words. You do not need to diagnose the technical cause.

What did you expect instead? (optional)Device, browser, assistive technology or accessibility settings (optional)

Name (optional)Email, if you'd like a reply (optional)

Before you send: please don't include passwords, authentication codes, health information or other sensitive personal information.

This form is processed by Web3Forms. Your submission will be sent to No Default and processed by Web3Forms to deliver it.

Privacy

Please do not include passwords, authentication codes, health information or other sensitive personal information in a report. Screenshots can contain names, account details and notifications, so check them before sending.

What happens to accessibility reports?

Confirmed issues should be added to the public Accessibility of this site record with enough information to understand the impact and status, without publishing a reporter's personal information.