Conformance status
The parts of GiveCampus listed below are substantially conformant with WCAG 2.2 Level AA. Some content does not yet fully meet the standard. We are working to close those gaps. We continually build and improve features to help schools raise more money, shipping updates multiple times a day. Because changes can introduce accessibility barriers, we do not claim full conformance at every moment. Our development process includes accessibility checks before release and annual audits by an independent firm. We track every reported issue and prioritize fixes for validated, in-scope issues based on their impact on giving and registration.What we cover
GC Online Giving
Campaign pages and donation formsGC Events
Event landing pages and the registration flowWhat we don’t cover
We do not make accessibility claims about:- Staff-facing administration tools. These are the tools school staff use to build and manage campaigns, forms and events.
- Emails sent through GiveCampus. This includes receipts, confirmations, reminders, and other emails, whether GiveCampus or the school wrote them.
- Pages a school hosts itself. This includes a school’s own website, even when it links to or embeds a GiveCampus page.
- Content embedded from other vendors. Some GiveCampus pages include tools from other companies, such as payment widgets and video players. While we don’t control how those tools are built, we request accessibility documentation (such as ACRs) and advocate for conformance. When someone reports a barrier in one of these tools, we share it with the vendor and advocate for a fix.
What schools control
Schools configure their pages and forms. Content a school adds, such as images, alt text, colors, videos, and custom code, can affect accessibility. We provide guidance to help schools make accessible choices.
How we work on accessibility
AUDITSRunning independent accessibility audits every year
MANUAL TESTINGTesting manually with keyboard navigation and screen readers, including JAWS, NVDA, and VoiceOver
TRAININGTraining our product, design, and engineering teams on accessibility
ISSUE TRACKINGTracking every reported issue and prioritizing validated, in-scope issues by their impact on giving and registration