Legal • accessibility

Accessibility statement.

Noetfield is committed to making this site usable for as many people as possible. This page describes our approach, known limitations, and how to report issues.

Last updated 2025-12-13
Scope noetfield.com
1) Commitment
Our intent 2) Measures
What we implement 3) Compatibility
Browsers & assistive tech 4) Known limitations
What may not be perfect yet 5) Need help?
Request assistance 6) Report an issue
How to contact us
Practical note: Noetfield pages prioritize clarity, keyboard access, strong contrast, and consistent structure. If you hit an accessibility barrier, report it and include the page URL.

1) Commitment

We aim to make Noetfield content accessible and usable across devices, browsers, and assistive technologies. Our target is a board-grade, evidence-first experience that remains readable and navigable for all users.

2) Measures we support

Keyboard navigation
Logical focus order, visible focus states, and a “Skip to content” link on every page.
Semantic structure
Clear headings, landmarks (header/main/footer), and descriptive link text where possible.
Readable content
High contrast, consistent typography, and restrained motion/decoration.
Forms that guide
Labels, required-field validation, and error states that can be interpreted without relying only on color.
Ongoing work: We continuously improve accessibility as we add Gate/Portal/Platform features and new components to the shared shell.

3) Compatibility

This site is designed to work with modern browsers (Chrome, Safari, Firefox, Edge) and common assistive technologies. If you experience issues, we can often provide an alternative format or a workaround.

4) Known limitations

Noetfield is under active development. Some pages or embedded third-party flows may not fully meet every accessibility expectation yet. Examples may include:

  • Third-party form processors or embeds that do not expose perfect ARIA metadata.
  • Early “coming soon” pages with limited interactive controls (still keyboard navigable).
  • Occasional inconsistencies while components are being centralized into shared partials/shell.

5) Need help accessing content?

If you need assistance, we can provide support through the Contact page. Please include the URL and what you are trying to do (e.g., submit a Gate form, open Status, view a policy page).

Go to /contact/ and include: page URL, device/browser, assistive tech (if any), and a short description of the issue.

6) Report an accessibility issue

Report accessibility problems via /contact/. We review issues and prioritize fixes that block core workflows (navigation, readability, forms, and tracking).

Related: Privacy · Terms · Cookies · Policies