Accessibility at Campus Connect

Version: 2026-09-30
Accessibility contact: info@campusdelivery.app, subject line "Accessibility"

This is an accessibility statement from Connect Technologies LLC, doing business as Campus Connect. It covers the Campus Connect app for iPhone and Android and campusdelivery.app in a browser, for a student ordering a delivery, a courier carrying one, or a visitor reading about the service. "You" below means whichever of those you are.

1. Definitions

• Assistive technology: software or hardware you use to read or operate a screen differently than by looking at it and tapping it directly, including a screen reader (VoiceOver, TalkBack), voice control, switch access, or a larger system text size.
• WCAG: the Web Content Accessibility Guidelines, the public standard this statement measures Campus Connect against.

2. Our commitment, and what we do about it

Campus Connect is committed to making the app usable by people with disabilities, and to improving it as we learn where it falls short. The measures we take:

• We aim for WCAG 2.2 at level AA across the app and the website: a spoken label for every button and control, enough color contrast in light and dark mode, text that can be resized, and flows that can be completed without seeing the map.
• Accessibility is part of how the app is built and reviewed: we aim for every control to have a spoken name and role in the code, the courier's one-handed controls have enlarged tap areas, and a change to a screen is checked against the rules below by the automated check the night after it ships.
• An automated check runs every night over the screens listed in section 8 and fails the run when a control has no spoken name, a field has no label, or text falls below the required contrast.
• The contact in section 4 reaches the person who builds the app.

3. Conformance status

The Web Content Accessibility Guidelines (WCAG) define requirements for designers and developers to improve accessibility for people with disabilities. They define three levels of conformance: Level A, Level AA, and Level AAA. Campus Connect is partially conformant with WCAG 2.2 level AA. Partially conformant means that some parts of the content do not fully conform to the accessibility standard. Section 7 lists what we know does not conform yet, and what to do instead.

4. Feedback

We welcome your feedback on the accessibility of Campus Connect. Please let us know if you encounter accessibility barriers:

• Email: info@campusdelivery.app, subject "Accessibility". Tell us what you were trying to do, the screen you were on, your phone, and any assistive technology you use. You do not need to explain a disability.
• In the app: open Help and ask for a person.
• Post: Connect Technologies LLC, 418 Broadway, Ste R, Albany, NY 12207.

We try to respond to feedback within 5 business days. If something stops you from placing or delivering an order, we will help you finish it another way while we fix it.

5. Compatibility with browsers and assistive technology

Campus Connect is designed to be compatible with:

• iPhone with VoiceOver, Android with TalkBack, and the larger text size and bold text settings of both;
• a current version of Chrome, Safari, Firefox or Edge on a laptop or phone, with the screen reader built into that device.

The phone app has not yet been tested on a device with VoiceOver or TalkBack. It is built on the same components as the browser version, so labels checked on the web carry over to VoiceOver and TalkBack; reading order and gesture navigation on a phone remain to be verified, and this section will be updated when they are.

Campus Connect is not designed for browsers older than those above, or for Internet Explorer.

6. Technical specifications

Accessibility of Campus Connect relies on the following technologies to work with the particular combination of web browser and any assistive technologies or plugins installed on your computer or phone:

• in a browser: HTML, WAI-ARIA, CSS and JavaScript;
• on a phone: the accessibility interfaces of iOS and Android, reached through React Native.

These technologies are relied upon for conformance with the accessibility standards used.

7. Limitations and alternatives

Despite our best efforts to ensure accessibility of Campus Connect, there may be some limitations. Below is a description of known limitations, and potential solutions. Please contact us if you observe an issue not listed below.

• The campus map is visual. The map that shows delivery spots and your courier's position is drawn by Mapbox, and its controls are Mapbox's own, which we cannot relabel. Every delivery spot can also be found by typing its name instead of finding it on the map, and a courier's progress toward a delivery is also shown as written status text, not only as a moving pin.
• Screens the nightly check does not cover yet. Chat, help, friends, account settings and these legal pages are not in the automated check (section 8), so a missing label there is found only by hand or when you tell us, and some may still have a gap the check has not caught.
• Touch targets outside the courier's route. The courier controls used during a pickup or handoff have a tap area of at least 44 points. We have not measured every other screen against that size, so some controls elsewhere may be smaller. Body text is set to follow your phone's larger text setting.
• The rules WCAG 2.2 added. The automated check runs the WCAG 2.0 and 2.1 rules; the 2.2 additions (such as the focus appearance and dragging-movement rules) are checked by hand, so meeting them is a goal we verify screen by screen rather than a guarantee.
• The order confirmation screenshot is read automatically. If it cannot be read, you can type the order details in yourself instead of retaking or resending the screenshot.
• The marketing pages at campusdelivery.app are built separately and are not covered by the check in section 8.

8. Assessment approach

Campus Connect assessed the accessibility of the app by self-evaluation. We have not yet had an independent, human accessibility audit; the check below and the fixes above are our own team's work.

An automated check (axe, the engine behind Chrome's Lighthouse audit) runs the WCAG 2.0 and 2.1 level A and AA rules every night over selected screens at a phone-sized viewport: the first screens, Home, choosing a delivery spot, the price, sign-in, tracking, and the rating after delivery for a student, and the first screens a courier and ops see. It fails that night's run if a button has no spoken name, a field has no label, or text falls below the required contrast against its background. Nothing of ours is excluded from it. A round-trip review of the student, courier and ops screens by hand found and fixed unlabeled onboarding dots, unlabeled pictures, and menus that did not announce as dialogs, and every contrast failure the check has found has been fixed.

9. Formal complaints

If you are not satisfied with our response to an accessibility problem, write to the postal address in section 4, marked "Accessibility complaint". A person reads it, and we aim to reply in writing within 10 business days with what we will change and by when. This does not limit any right you have under the Americans with Disabilities Act or New York law, and you may also raise the matter with the U.S. Department of Justice at ada.gov.

10. Date

This statement was last updated on 2026-09-30. Its structure follows the W3C accessibility statement generator, and the sentences defining WCAG conformance levels and "partially conformant" are the generator's own.