Goal OneДоступность
Let’s goal
/legal  Доступность 8 разделов · около 5 минут чтения goal.one

Заявление о доступности

Этот документ опубликован на английском языке. Обязательной является английская версия.

  • Document ID: PLG-AS-2026
  • Version 2.0
  • Effective: October 21, 2026
  • Supersedes Version 1.0 (July 12, 2026)

Юридически обязательной является англоязычная версия этого документа. Translations are provided for convenience only.

G1goal.one — бренд компании Pledgix LLC, названной в этих документах. Там, где упоминаются Pledgix Go, Pledgix One и Pledgix Pro, речь идёт о планах, которые теперь называются Ready, Set и Goal. Юридические условия не изменились.

This statement describes the accessibility of the Pledgix fundraising platform: the standard we work toward, our current status and its known gaps, the accommodations available on campaign pages, and how to reach us if something gets in your way.

1Our Commitment#

Pledgix LLC is committed to making the Pledgix platform usable by people with disabilities. This statement covers pledgix.com, campaign pages (including those served on custom domains), admin.pledgix.com, dash.pledgix.com, and the Pledgix mobile apps. Accessibility is part of how we design, build, and test the platform, and we work continuously to improve the experience for every visitor, donor, and organizer.

2Standard and Conformance Status#

2.1 Standard. We use the Web Content Accessibility Guidelines (WCAG), published by the World Wide Web Consortium (W3C), as our standard. Our target is WCAG 2.2 Level AA (https://www.w3.org/TR/WCAG22/), which includes all the success criteria of WCAG 2.1 Level AA.

2.2 Current status. Based on our most recent internal self-assessment, completed on October 21, 2026, the websites listed above are partially conformant with WCAG 2.1 Level AA. "Partially conformant" means that some parts of the content do not yet fully conform; they are described in Section 5. This status is based on an assessment of the pledgix.com home page, our legal pages, campaign pages, and the donation checkout. It does not describe admin.pledgix.com, dash.pledgix.com or the Pledgix mobile apps, which were not assessed, and the assessment did not cover the success criteria added in WCAG 2.2.

2.3 What this statement does not claim. This statement describes our own assessment. It is not a certification by any third party, and it does not claim that the platform meets every accessibility requirement of every law in every country. We do not rely on an automated "overlay" tool to make the platform accessible.

3Accessibility Features#

Platform-wide measures include:

  • Keyboard operability, with skip-to-content links and visible focus indicators.
  • Semantic HTML with a logical heading hierarchy, ARIA labels and roles, and alternative text for meaningful images in the platform's own interface.
  • A platform interface designed to meet WCAG 2.1 AA color-contrast ratios.
  • Right-to-left layout and full translation for Hebrew, plus Spanish, French, and Russian.
  • Respect for the operating system's reduced-motion preference.

In addition, every campaign page includes an accessibility menu, opened from the round button at the edge of the screen on larger displays or from the "Accessibility options" link in the page footer on mobile devices. It lets visitors adjust the page to their needs:

  • Text size (up to 150%) and text spacing (up to the spacing values in WCAG success criterion 1.4.12).
  • A readable font, high-contrast and inverted color modes, and grayscale or vivid color intensity.
  • Link highlighting, keyboard-focus highlighting, hiding images, pausing animations, a large cursor, and a reading guide.

These settings are built by Pledgix (not a third-party overlay), are stored only on the visitor's device, and apply immediately across the campaign page. They are optional aids. The platform is designed to be accessible without them.

4Compatibility with Browsers & Assistive Technology#

The platform is designed to work with recent versions of major browsers (Chrome, Safari, Edge, and Firefox) on desktop and mobile, and with common assistive technologies, including screen readers (such as NVDA, JAWS, VoiceOver, and TalkBack), screen magnification, speech-recognition software, and browser zoom up to 200%. Our most recent assessment (Section 2.2) used automated testing with axe-core and keyboard testing in the Chromium browser, at desktop and phone screen sizes. It did not include testing with screen readers or other assistive technologies.

5Known Limitations#

Despite our efforts, some content may not yet be fully accessible:

  • Organizer-provided content. Campaign stories, images, and videos are uploaded by campaign organizers. We give organizers tools to add alternative text and captions, but we cannot guarantee that every image has adequate alternative text or that every video is captioned. If you find such content, tell us and we will ask the organizer to fix it or provide the information to you another way.
  • Third-party components. Payment fields (provided by our payment processors), bot-protection checks, embedded media players, and similar third-party components follow their providers' own accessibility practices. We choose providers with accessibility commitments, report issues we find to them, and offer alternatives (see below).
  • Generated documents. Some downloadable documents, such as older donation receipts, may not be fully tagged for screen readers. We can provide an accessible version on request.
  • Phone services. Automated phone (IVR) donation menus may be difficult to use with some assistive technologies. You can ask to complete a donation with a staff member instead.
  • Campaign colors. Organizers can choose the colors of their campaign pages, and some color choices can fall below the WCAG 2.1 AA minimum contrast for text (success criterion 1.4.3). If you find such a page, tell us and we will ask the organizer to change the colors or provide the information to you another way. The high-contrast mode in the accessibility menu (Section 3) may also help.

If any of these prevent you from using the platform, including completing a donation, contact us. We will provide the information or service you need through an accessible alternative, such as completing a donation with you by phone or email.

6Feedback, Contact & Accessibility Team#

We welcome feedback on the accessibility of the platform. If you encounter an accessibility barrier or need assistance, contact our accessibility team:

  • Email: hi@goal.one
  • Mail: Pledgix LLC, Attn: Accessibility, 10 Willow Dr., Suffern, NY 10901, United States

Please describe the page you were on, what you were trying to do, and the assistive technology or browser you were using. You can also ask for this statement, our Terms, or our Privacy Policy in an alternative format.

We aim to acknowledge accessibility feedback within 2 business days and to resolve reported barriers, or provide an accessible alternative, within 10 business days. If a fix will take longer, we will tell you when to expect it and how we can help in the meantime.

7Enforcement & Complaints#

If you contact us about an accessibility barrier and are not satisfied with our response, you may have the right to raise the matter with an authority responsible for disability-rights enforcement where you live. For example:

  • United States: the U.S. Department of Justice, Civil Rights Division (https://civilrights.justice.gov/; information at https://www.ada.gov/), or your state or local human-rights agency (in New York, the New York State Division of Human Rights).
  • Israel: the Commission for Equal Rights of Persons with Disabilities (נציבות שוויון זכויות לאנשים עם מוגבלות), Ministry of Justice.
  • European Union and other countries: the national body responsible for accessibility or equal-treatment complaints in your country.

8Assessment & Review#

This statement is based on an internal self-assessment of the platform against WCAG 2.1 Level AA, most recently completed on October 21, 2026, using automated testing with axe-core and keyboard testing. We review this statement, and re-test the platform, at least once a year and whenever we add significant functionality. This statement was last updated on October 21, 2026.