NearArc Accessibility Statement

Effective date: 20 October 2026 · Last updated: 21 October 2026

NearArc is a service provided by Zach Jensz (ABN 95 243 396 633), a sole trader based in Victoria, Australia (we, us, our). We want everyone to be able to use the NearArc platform and take part in NearArc events, including people with disability. This statement explains the standard we are working towards, where we are now, the known gaps, and how to tell us about a barrier so we can fix it. It applies to neararc.com and the NearArc progressive web app.

At a glance

We are aiming for the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AAA, the highest level.
NearArc is in public alpha. We have not yet verified that it meets WCAG 2.2 at any level, so we don't claim conformance, and you may find barriers. We list the ones we know about in section 4.
NearArc works in modern web browsers with the assistive technology you already use. Installing it as an app is optional.
Event organisers are asked to describe venue accessibility. (planned) You can share your accessibility needs for an event, with your consent.
Found a barrier? Use the in-app bug report form, or email support@neararc.com if you can't sign in or the barrier stops you signing in. We respond as soon as practicable.
We can provide information in another format on request.
If you're not satisfied with our response, you can complain to the Australian Human Rights Commission.

1. Our commitment

Accessibility is part of how we build NearArc, not a later add-on. A professional network focused on real-world connections only works if everyone can create a profile, message people, find events and turn up to them.

Zach Jensz is responsible for accessibility at NearArc. We treat accessibility barriers as bugs, and we consider accessibility when we design and release new features, including planned features such as recruiting, paid events and AI features.

2. The standard we use

We use the Web Content Accessibility Guidelines (WCAG) 2.2, published by the World Wide Web Consortium (W3C). WCAG has three levels:

Level	What it means
A	The minimum. Removes the most severe barriers.
AA	The level most laws and guidelines refer to. Removes the most common barriers.
AAA	The highest level. Meets every A, AA and AAA success criterion.

Our goal is Level AAA. Some AAA criteria can't be met for every kind of content, especially content that members and organisers create, such as event descriptions, photos and imported event listings. Where a AAA criterion can't reasonably be met, we will still meet Level AA and say so in section 4.

Our current status. NearArc is in public alpha and changes often. We have not yet completed a full audit against WCAG 2.2, so we do not claim that NearArc conforms to WCAG 2.2 at Level A, AA or AAA. We expect to find and fix gaps as we go. When we complete an audit, we will update this statement with the results and how we tested.

3. What we do

These are the practices we follow when we build NearArc. They are goals, not a guarantee that every page already meets them. Where a practice is not yet consistent across NearArc, we treat that as a bug to fix.

Semantic HTML. We aim to use standard HTML elements, headings and landmarks so screen readers and other tools can understand page structure.
Keyboard access. We aim for every feature to work with a keyboard alone, with a visible focus indicator and a logical focus order, and without keyboard traps.
Sign-in without memory tests. NearArc uses passkeys and one-time codes instead of passwords, so you don't need to remember or type a password. We aim to keep one-time codes easy to paste or autofill, and to give you enough time to enter them.
Text alternatives. We aim to provide text alternatives for meaningful images and icons. We ask members and organisers to add descriptions to images they upload, where that option is available.
Colour and contrast. We aim for strong text contrast, and we don't rely on colour alone to convey information.
Resizing and reflow. We aim for pages to work when zoomed to 400% and on small screens, without horizontal scrolling for normal reading.
Respecting your settings. We aim to respect your device and browser settings, such as reduced motion, dark or light mode and browser zoom.
Clear language and forms. We aim to use plain language, clear labels and instructions, and error messages that explain how to fix the problem.
Time limits and movement. We aim to avoid time limits you can't extend, and content that flashes or moves automatically.
Testing. We run automated checks as we build: contrast checks on the colour tokens we use for actions, statuses and badges, in light and dark; an automated accessibility scan of our component library, in light and dark; and visual-regression screenshots of that library, in light and dark, captured with reduced motion. We also test by hand as we build, including with a keyboard alone.

4. Known limitations

These are the barriers we currently know about. We describe them in plain terms. If you find something not listed here, please tell us (see section 7).

Imported event listings may contain text, images or links from external sources that don't have text alternatives or clear headings. We are working on ways to improve imported content. Workaround: ask the organiser or email us for the details.
Some images uploaded by members or organisers may not have text descriptions, and we don't yet offer a way to add them everywhere. We are working on that.
We don't yet meet every Level AAA criterion in every place, such as reading level (WCAG 3.1.5) or enhanced contrast (WCAG 1.4.6).
External sites we link to, such as external RSVP pages for imported events, are not controlled by us and may not be accessible.

Third-party content. Some content on NearArc comes from members, organisers and external sources. We can't control all of it, but we will help where we can, for example by asking the organiser for an accessible version or removing content that creates a serious barrier.

5. Compatibility

Browsers and the progressive web app

NearArc is a web app. There are no native iOS or Android apps. It is designed to work in current versions of major web browsers, together with the assistive technology built into your device or that you have installed.

You can use NearArc in your browser without installing anything.
You can also install NearArc as a progressive web app (PWA) from your browser, so it opens in its own window like an app. Installing is optional. The installed app runs on your browser's engine, so your browser and device accessibility settings still apply.
NearArc stores some data on your device so pages load quickly (see section 5 of our Privacy Policy).
Signing in uses passkeys, which rely on your device or browser's passkey support. If you have trouble signing in with a passkey because of an accessibility barrier, email support@neararc.com and we will help you get in.

What we test with

We are building a supported browser and assistive technology matrix and will publish it here when it is ready. What we check automatically today is most of our component library, rendered in Chromium on our build machines, in light and dark mode and with reduced motion, with an automated accessibility scan. We also test by hand as we build, including with a keyboard alone.

NearArc may work with other browsers and assistive technology. If something doesn't work with your setup, please tell us.

6. Accessibility at events

Many NearArc events are in person. Accessibility of an event depends on the venue and the organiser, as well as on the NearArc platform.

Organisers. We ask organisers to give clear venue accessibility information on their event page, such as step-free access, accessible toilets, seating, lighting and noise, hearing loops, quiet spaces, and how to reach the venue by public transport. For online events, we ask organisers to say what platform they will use and whether captions or transcripts will be available. Organiser responsibilities are set out in our Event & Organiser Terms.
Imported listings. Many events on NearArc are imported from external sources, and their accessibility information may be missing or out of date. Check with the organiser before you go. If an organiser claims the listing, we will ask them to add accessibility information.
Sharing your needs. When you RSVP (planned), you can choose to share accessibility needs or dietary requirements, with your consent. We use this information only to arrange your accommodations, and share it only with the organiser, venue or caterer who needs it. Our Consumer Health Data Privacy Notice and Privacy Policy explain how we handle it, and how to withdraw consent or ask us to delete it.
Private homes. Some events are held in private homes, which may not be accessible. Organisers should say so on the event page.
Problems at an event. If an event wasn't accessible as described, please tell us using the bug report form or support@neararc.com. If you were treated unfairly or felt unsafe, see our Code of Conduct and Safety Centre.

We do not run most venues and can't guarantee that every event is accessible. We will follow up with organisers who don't provide accurate accessibility information.

7. Tell us about a barrier

If something on NearArc doesn't work for you, we want to know. Your feedback directly shapes what we fix next.

How to contact us

Signed in: use the in-app bug report form.
Not signed in, no account, or the barrier stops you signing in or using the form: email support@neararc.com. You don't need an account.

If you'd prefer, you can ask someone to contact us on your behalf. If you use the National Relay Service in Australia, you can contact us through it using our email address.

What to include

As much of the following as you can. None of it is required.

the page or feature (a link or description is fine);
what you were trying to do, and what happened;
the assistive technology you use, if any, and its version;
your browser, device and operating system;
a screenshot or recording, if it helps and you're comfortable sharing it; and
how you'd like us to reply.

If you use the bug report form, it shows you the technical details it will include, such as your browser, device and operating system, before you send it. We handle bug reports as described in our Privacy Policy and keep them only as long as needed to investigate and fix the issue. Please don't include health information in a bug report unless it helps us understand the problem.

What happens next

We respond as soon as practicable. We don't promise a fixed timeframe, because NearArc is run by one person, but we prioritise barriers that stop you signing in, messaging, or taking part in events.
If we can't fix a problem quickly, we will try to give you the information or help you need another way, such as by email.
We will tell you when a barrier you reported is fixed, if you ask us to.

8. Alternative formats

If you need information from NearArc in a different format, such as plain text, large print, an accessible document, or a plain-language explanation of one of our policies, email support@neararc.com. Tell us what you need and the format that works for you. We will do our best to provide it within a reasonable time, at no cost.

9. If you're not satisfied

Please contact us first so we can try to resolve the problem.

Australia. The Disability Discrimination Act 1992 (Cth) makes it unlawful to discriminate against people with disability when providing goods and services, which can include websites and apps. If you are not satisfied with our response, you can make a complaint to the Australian Human Rights Commission. Complaints are free, must be in writing, and the Commission can help you write one down. Contact the Commission's National Information Service on 1300 656 419, email infoservice@humanrights.gov.au, or visit humanrights.gov.au.

Other countries. If you live in New Zealand, Canada or the United States, you may also have rights under local human rights or disability laws, and may be able to complain to the relevant human rights body in your country, province, territory or state. Nothing in this statement limits those rights.

10. Review of this statement

We review this statement when we make significant changes to NearArc, when we complete an accessibility audit, and at least once a year.

This statement was last reviewed on: 21 October 2026.
How NearArc was assessed: Self-assessment as we build, using our automated checks (see section 5) and manual testing, including with a keyboard alone. We have not completed a full WCAG 2.2 audit, by ourselves or an external specialist, and will update this statement when we do.

11. Contact us

Zach Jensz, Accessibility contact ABN 95 243 396 633 Victoria, Australia Email: support@neararc.com Website: neararc.com

Zach Jensz · ABN 95 243 396 633 · Victoria, Australia · neararc.com