TNC Accessibility Notice

1. COMMITMENT, SCOPE, AND INCORPORATION

TNC is committed to providing people with disabilities meaningful access to TNC-controlled websites, public pages, T.E.A., accounts, Network Portals, legal documents, communications, forms, files, services, World Connections functions, Events, and other experiences.

This TNC Accessibility Notice supplements the TNC Ecosystem Participation Terms & Conditions, Account & Platform Terms, Privacy Notice, Communications Notice, Electronic Records & Signature Consent, Experience Participation Terms, applicable Network terms, and action-specific instruments.

The Integrated TNC Platform is the single end-to-end TNC-controlled system through which public and authenticated interactions are delivered and administered. The Website, public pages, forms, T.E.A., and authenticated portal interfaces are its public-facing frontend. The governed private CRM backend is its administrative, workflow, record, permission, audit, and command surface. The two surfaces are not separate providers or separate participant relationships. A person receives only the access authorized for that person; public interaction never grants backend access.

2. ACCESSIBILITY BENCHMARK

TNC uses the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA as the primary design and testing benchmark for TNC-controlled web content and applications where reasonably applicable, together with applicable law, platform constraints, user needs, and accepted accessibility practices.

The benchmark is a continuing operational target, not a representation that every page, document, provider, file, Event, or feature is perfectly accessible at all times. TNC must not claim conformance without evidence appropriate to the claimed scope and date.

3. INTEGRATED FRONTEND AND BACKEND ACCESSIBILITY

Accessibility applies to the end-to-end journey, not only the visible page. TNC should design the public frontend, T.E.A., authenticated portal flows, forms, error states, identity and authority verification, documents, communications, payment and acceptance steps, support, and backend-assisted handling so a disability does not create an avoidable barrier.

A Participant receives no backend access merely because the backend supports the request. TNC may use backend records to preserve an accommodation, alternative format, communication preference, or issue history within authorized limits.

4. TNC-CONTROLLED DIGITAL FEATURES

TNC-controlled digital surfaces should support, as applicable:

• keyboard operation without a mouse, logical tab order, visible focus, focus containment, and reliable focus return;
• semantic headings, landmarks, labels, instructions, status messages, error identification, and screen-reader announcements;
• text resizing, browser zoom, reflow, sufficient contrast, noncolor cues, readable spacing, and avoidance of clipped or overlapping content;
• captions, transcripts, audio descriptions, text alternatives, and accessible controls for time-based media where applicable;
• reduced motion, pause/stop controls, timing adjustments, avoidance of harmful flashing, and predictable interactions;
• accessible authentication, multi-factor, CAPTCHA alternatives, recovery, document review, e-sign, payment, upload, download, and receipt flows;
• mobile, desktop, orientation, touch-target, and assistive-technology use; and
• clear decline, withdrawal, correction, support, and recovery paths.

5. LEGAL DOCUMENTS, ELECTRONIC RECORDS, AND FORMS

TNC legal documents and acceptance flows should be readable with assistive technology and available in a retainable format. Structure should use real headings, lists, table headers, logical reading order, descriptive links, sufficient contrast, and text that can be selected and searched where feasible.

A person may request an alternative format, including an accessible Word document, tagged or remediated PDF, HTML, large print, plain text, or another reasonable format.

An inaccessible document or acceptance flow must not be treated as valid consent when the person could not reasonably access the material. TNC should provide an alternative before the consequential action proceeds.

6. COMMUNICATIONS, CAPTIONS, AND LANGUAGE

TNC should provide communication methods compatible with screen readers, keyboard use, zoom, captions, transcripts, relay services, interpretation, and reasonable alternative channels within TNC-controlled systems.

A person may request a communication accommodation, including a different channel, accessible electronic format, captioning, interpretation, slower pacing, written follow-up, support person, or another reasonable method.

Accessibility accommodation is separate from language translation. TNC should identify the controlling language and resolve material ambiguity before a consequential acceptance or action.

7. REQUESTING AN ACCOMMODATION OR ALTERNATIVE FORMAT

A request may be submitted through the applicable portal or TNC contact method. The request should describe the affected function, barrier, preferred method, timing, and information reasonably necessary to evaluate the request. A person is not required to disclose a diagnosis beyond what is reasonably necessary.

TNC should acknowledge the request promptly, identify the responsible person or team, engage in a good-faith interactive process where appropriate, provide an interim method when feasible, document the decision, and communicate the result in an accessible way.

TNC may request reasonable clarification and may propose an equally effective alternative when the preferred method would fundamentally alter the service, create an undue burden, conflict with law, compromise security, or be technically infeasible. Any limitation must be evaluated individually and not assumed.

8. TIMING AND URGENT ACCESS

A person should request an accommodation as early as reasonably possible, but TNC will consider late and urgent requests in good faith.

When a deadline, interview, payment, signature, Event, application, or other consequential action is affected by an accessibility barrier, TNC should pause, extend, or provide a reasonable alternative where required and feasible rather than treat the barrier as a decline, failure, or lack of interest.

9. NONRETALIATION AND EQUAL PARTICIPATION

TNC will not retaliate against a person for making a good-faith accessibility request, reporting a barrier, using an accommodation, or exercising a disability-related right.

An accommodation request, disability, assistive-technology use, accessibility issue, or alternate format must not be used as an adverse signal, ranking factor, eligibility shortcut, public disclosure, marketing attribute, or unrelated relationship inference.

10. EVENTS, VENUES, AND IN-PERSON EXPERIENCES

TNC-controlled Experiences should address reasonable access needs involving venue entry, seating, mobility, service animals, communication, captions, interpretation, lighting, sound, sensory conditions, dietary information, restrooms, transportation information, support persons, and emergency procedures as applicable.

Third-party Venues and providers may have separate duties and limitations. TNC should communicate known material limitations, coordinate within its control, and provide a reasonable alternative where required and feasible.

Recording, photography, media, and publicity decisions remain separate from an accessibility accommodation.

11. THIRD-PARTY CONTENT, PROVIDERS, AND INTEGRATIONS

TNC uses third-party providers for hosting, authentication, communications, payments, scheduling, documents, video, Events, analytics, security, and other functions. TNC does not control every independent third-party surface, but should evaluate accessibility appropriate to the function and risk, communicate known material barriers, and pursue reasonable remediation or alternatives.

A vendor’s accessibility statement is not conclusive proof of the actual experience. Procurement, renewal, and provider review should consider accessibility evidence, support, conformance reports where available, remediation commitments, incident history, and alternative methods.

12. PRODUCT DESIGN, DEVELOPMENT, AND PROCUREMENT

TNC should include accessibility in requirements, design systems, content authoring, development, testing, procurement, release, change management, incident response, and quality assurance.

Design and engineering should avoid interface patterns that create unnecessary cognitive, visual, auditory, motor, speech, or seizure barriers. Components should preserve accessibility across themes, screen sizes, modes, states, and updates.

A new feature or material change should not be released solely because an automated scan passes.

13. TESTING AND QUALITY ASSURANCE

Accessibility verification should combine automated testing, keyboard testing, zoom and reflow review, contrast review, screen-reader testing, reduced-motion review, mobile and desktop review, document inspection, form and error-state testing, and manual review by knowledgeable persons. User testing should be included where appropriate.

Testing must cover the complete task, including entry, identity or authority verification, review, acceptance, payment, file handling, confirmation, receipt, error recovery, withdrawal, and support, not only the landing page.

TNC should preserve the tested version, environment, device, browser, assistive technology, findings, severity, remediation, retest, exceptions, and release decision.

14. REPORTING AN ACCESSIBILITY BARRIER

A person may report inaccessible content, missing labels, keyboard traps, focus failures, contrast issues, clipped text, inaccessible files, missing captions, confusing errors, timing barriers, or another issue through the applicable portal or TNC contact method.

The report should identify the URL, page, document, feature, device, browser, assistive technology, date, and barrier where known. TNC should not require technical expertise or unnecessary personal information.

TNC should acknowledge, prioritize, investigate, provide an alternative when feasible, remediate, retest, and communicate resolution. A report must not be closed merely because an automated tool cannot reproduce it.

15. PRIVACY AND CONFIDENTIALITY OF ACCESSIBILITY INFORMATION

TNC may collect only the information reasonably necessary to evaluate and implement an accommodation, investigate a barrier, preserve the record, and comply with law.

Accessibility information must be limited to authorized persons and must not be silently reused in recruiting, marketing, eligibility, risk, community, or another unrelated context. TNC may preserve a minimal record needed to honor the accommodation and demonstrate compliance.

16. T.E.A. AND ACCESSIBILITY SUPPORT

T.E.A. may explain accessibility options, help route a request, provide alternative wording, identify missing labels or structure, support captions or summaries, and prepare a remediation task within authorized limits.

T.E.A. is not a substitute for required human review, assistive-technology testing, an interactive accommodation process, or a final legal determination. T.E.A. may not deny an accommodation or close an accessibility issue without the required authority.

17. EMERGENCIES, SECURITY, AND ACCESSIBILITY

Security and fraud controls should provide an accessible method and should not impose an unnecessary barrier. When a standard authentication, CAPTCHA, timeout, or device step is inaccessible, TNC should provide an equally effective secure alternative where feasible.

Emergency and safety information should be communicated through accessible methods appropriate to the circumstances.

18. LIMITATIONS AND CONTINUING IMPROVEMENT

Accessibility is an ongoing process. Content, providers, devices, browsers, assistive technologies, laws, and standards change. TNC may identify limitations and should prioritize remediation based on impact, frequency, consequence, feasibility, and legal obligation.

TNC does not guarantee that every third-party item or historical file is immediately accessible, but will provide reasonable support, alternatives, and remediation appropriate to the situation.

19. RECORDS AND RECEIPTS

An accessibility record may preserve: request or issue ID; requester and relationship; affected content or action; date; barrier; preferred method; information voluntarily supplied; interim method; assigned person; analysis; decision; accommodation or remediation; provider involvement; response; retest; resolution; withdrawal; retention; and appeal or escalation.

A visual “resolved” state without evidence of the alternative or successful retest is not completion.

20. CHANGES AND GOVERNING LAW

TNC may update this Notice. Material changes require versioning and notice or reacceptance where applicable. Prior requests, accommodations, findings, accepted copies, and receipts remain preserved.

TNC intends to operate consistently with applicable disability-access law, including Titles I and III of the Americans with Disabilities Act where applicable, Section 508 where contractually or legally applicable, state and local law, and WCAG 2.2 AA as the TNC-controlled technical benchmark.

Kansas law governs unless a controlling instrument or mandatory law lawfully provides otherwise. Exclusive venue lies in the state or federal courts serving Sedgwick County, Kansas.

CONTACT

Questions or requests may be submitted through the applicable authenticated portal or to tsullivan@1290worldconnections.com. Office: (316) 365-5546. Direct: (316) 374-4159.

CONTACT

Questions may be submitted through the applicable authenticated portal or to tsullivan@1290worldconnections.com. Office: (316) 365-5546. Direct: (316) 374-4159.