Accessibility Statement

Last updated: Jul 24, 2026

ACCESSIBILITY STATEMENT & ADA COMMITMENT

Africanii, Inc. is committed to ensuring that africanii.com and our iOS and Android mobile applications are accessible to all people, including individuals with disabilities. Every member of our community — regardless of ability — has the right to participate fully in the Platform. This Statement describes our legal commitment, what we have implemented, what limitations currently exist, our remediation plan, and how to contact us for assistance.

 

NON-CONTRACTUAL CLAUSE

This Accessibility Statement is intended to describe Africanii's accessibility practices and commitments. It does not constitute a contract and does not create enforceable rights beyond those required by applicable law.

1. Legal Commitment

Africanii is committed to complying with the Americans with Disabilities Act (ADA), Title III, which requires places of public accommodation, including websites and mobile applications, to be accessible to individuals with disabilities. Africanii seeks to design and operate its digital services in a manner consistent with applicable accessibility laws and guidance, including the Americans with Disabilities Act and related accessibility standards.

Our accessibility programme is aligned with:

  1. DOJ Final Rule of April 24, 2024 (28 C.F.R. Part 35), effective June 24, 2024 — adopting WCAG 2.1 Level AA as the enforceable standard for government websites and reflecting the DOJ's applied standard for commercial websites under Title III.
  2. Web Content Accessibility Guidelines (WCAG) 2.1 Level AA, published by the World Wide Web Consortium (W3C).
  3. Texas Human Resources Code §121.003 — prohibiting disability discrimination by Texas places of public accommodation.
  4. Apple Human Interface Guidelines for Accessibility (iOS) and Google Material Design Accessibility Guidelines (Android).

 

2. Scope

This Statement covers:

  1. Africanii website: africanii.com and all subdomains.
  2. Africanii iOS application (Apple App Store).
  3. Africanii Android application (Google Play).
  4. All Platform features: Marketplace (/marketplace); Events (/events); Business Directory (/business); Community Map (/map); Private Messaging; Account Registration and Settings; Trust & Safety appeal forms.

This Statement does not cover third-party websites or applications linked from the Platform. See Section 9 for our third-party accessibility policy.

 

3. Conformance Status

Target conformance level: WCAG 2.1 Level AA.

Current status: Africanii strives toward WCAG 2.1 Level AA conformance and conducts ongoing accessibility testing and remediation efforts. Accessibility conformance may vary across features, devices, browsers, operating systems, and third-party integrations. Known exceptions are documented in Section 8. A full Voluntary Product Accessibility Template (VPAT) / Accessibility Conformance Report (ACR) is available on request at accessibility@africanii.com.

Most recent formal audit: conducted April 2026 by an independent accessibility specialist (CPACC credential). Audit scope: the 25 most-visited pages of africanii.com, the iOS app core user journeys (registration, listing creation, search, messaging), and the Android app core user journeys.

 

4. Implemented Accessibility Features

  1. Perceivable
  2. Alternative text: meaningful images are designed to include descriptive alternative text where reasonably practicable.
  3. Captions: Africanii-produced video content are intended to include closed captions. User-uploaded videos include a caption-file upload option at the time of posting.
  4. Colour contrast: texts are intended to meet a minimum ratio of 4.5:1 against its background (normal text) and 3:1 for large text (18pt+ or 14pt+ bold), verified via Axe and manual review.
  5. No colour-only information: error states, status badges, and category labels generally use text labels and icons in addition to colour.
  6. Resizable text: texts may be resized to 200% in the browser without loss of content or functionality. No fixed-pixel font sizes are used.
  7. Responsive layout: the Platform is generally designed to flow at widths of 320 CSS pixels or wider without horizontal scrolling (WCAG 1.4.10).

4.2 Operable

  1. Keyboard access: Interactive elements - menus, listings, forms, buttons, modal dialogs, messaging, and checkout are designed to be keyboard-operable to the extent reasonably practicable.
  2. No keyboard traps: users may navigate to and from all components using keyboard alone.
  3. Skip navigation: a 'Skip to main content' link is generally design to be the first focusable element on every page.
  4. Visible focus indicators: To extent practicable focusable elements display a clearly visible focus ring meeting a minimum 3:1 contrast ratio against adjacent colours (WCAG 2.4.11).
  5. Descriptive page titles: pages are designed to have a unique, descriptive title (e.g., 'Marketplace — Africanii').
  6. Descriptive link text: Generally, the links are designed to use meaningful text describing the link destination. We do not use 'click here' or 'read more' as link text.
  7. No seizure-inducing content: Generally, no content flashes more than three times per second (WCAG 2.3.1).

4.3 Understandable

  1. Language identification: the correct language attribute is generally designed to be on every page and on foreign-language sections.
  2. Visible labels: To the extent practicable, the form input has a visible, programmatically associated label — not only placeholder text.
  3. Error identification: validation errors identify the specific field and describe the error and how to correct it.
  4. Error prevention: consequential actions (submitting a listing, deleting an account) include a review/confirmation screen.
  5. Consistent navigation: menus, headers, footers, and interface patterns are consistent across all pages.

4.4 Robust

  1. Valid HTML5: pages are generally design to use valid, well-formed HTML5. Automated validation runs on every production deployment.
  2. ARIA landmarks: pages are generally design to include header, nav, main, footer, and aside ARIA landmark roles.
  3. ARIA labels for custom components: the Community Map, listing carousel, modal dialogs, rating widgets, and country-flag selectors are generally design to include appropriate aria-label, aria-describedby, aria-expanded, and aria-haspopup attributes.
  4. Assistive technology testing: the Platform is tested with NVDA + Firefox (Windows), VoiceOver + Safari (macOS and iOS), and TalkBack + Chrome (Android) before each major release.
  5. Browser compatibility: To the extent practicable, current and prior major versions of Chrome, Firefox, Safari, and Edge.

 

5. Mobile Application Accessibility

5.1 iOS

  1. VoiceOver: all interactive elements and images include accessibilityLabel, accessibilityHint, and accessibilityTraits. Custom components (listing cards, map list view, country-flag selector) are fully labelled.
  2. Dynamic Type: all text scales from Accessibility Small to Accessibility XXXL without clipping or overlap.
  3. Reduce Motion: animations are minimised when Reduce Motion is enabled in iOS Accessibility settings.
  4. Switch Control: core user journeys are designed to be accessible using Switch Control.
  5. Touch targets: all interactive targets are at least 44×44 points (Apple HIG; WCAG 2.5.5).

5.2 Android

  1. TalkBack: all interactive elements include contentDescription. Custom views implement the AccessibilityDelegate API.
  2. Font scaling: all text scales with the user's font size preference without clipping or overlap.
  3. Switch Access: all core user journeys are completable using Switch Access.
  4. Touch targets: all interactive elements meet 48×48 dp minimum (Google Material Design).

 

6. Community Map Accessibility

  1. List view alternative: an accessible list view of nearby community content is available as a full alternative to the visual map, where available, accessible alternatives such as list views may be provided. The list view is keyboard navigable and compatible with all tested screen readers.
  2. ZIP-code search: the list view can be used with a manually entered ZIP code or neighbourhood name — precise geolocation consent is not required to browse community content nearby.
  3. Screen-reader map labels: each pin on the visual map has a programmatic accessibility label identifying the content type (listing, event, or business), name, and approximate distance.
  4. Keyboard map navigation: arrow keys pan the map; +/− keys zoom; Enter selects a pin.

 

7. AI Feature Accessibility

  1. Moderation notifications: all AI-assisted moderation decisions are intended to communicate via plain-text email and in-Platform notifications structured for screen-reader compatibility. Notifications do not rely on color or imagery alone.
  2. ADMT opt-out and appeal forms: the opt-out form for automated decision-making and the appeal form for moderation decisions are standard keyboard-accessible web forms with visible labels and error identification. An email alternative (appeals@africanii.com) is intended to be available.
  3. AI chatbot (when deployed): every chatbot interaction may disclose its AI nature at the start of the conversation; the chatbot interface may be keyboard-accessible and screen-reader-compatible; escalation to a human agent may be available at any time.
  4. AI-generated content: all AI-generated listing suggestions and platform text are designed to meet WCAG 2.1 Level AA colour contrast requirements. AI-generated images must include alt text before being posted.

 

8. Known Limitations and Remediation Plan

Known Limitation Affected Feature Severity Interim Workaround  
Map pin keyboard navigation does not follow logical geographic sequence Community Map — web High Use the fully accessible List View toggle  
Focus indicator on some form controls in Android app does not meet minimum contrast ratio Android app — checkout forms High Use TalkBack — all inputs are labelled for TalkBack  
Some older PDF documents in Business Directory lack PDF tags Business Directory — web and app Medium Email accessibility@africanii.com for accessible HTML version within 5 business days  
User-uploaded videos do not automatically receive captions Marketplace and Events — user video Medium Caption file upload option available at post time; high-traffic listings prompted by moderators  
Some third-party embedded social media widgets are not keyboard-accessible Home and About pages Low Direct accessible text links provided alongside all embedded widgets  

8.1 Estimated Resolution target

Estimated remediation timelines are planning goals only and may change based on technical, operational, staffing, vendor, or legal considerations.

 

9. Third-Party Content

Africanii does not control the accessibility of third-party content linked from or embedded in the Platform. Before integrating any third-party service, we review its published ACR or request accessibility documentation. We require accessibility provisions in vendor contracts for services embedded in the user experience. Where a third-party component on our Platform is inaccessible, we provide an accessible alternative (direct text link or alternative content). Report inaccessible third-party components to accessibility@africanii.com.

9.1 Africanii does not control and cannot guarantee the accessibility of third-party websites, software, services, content, or embedded functionality

 

10. Grievance Procedure and Contact

If you encounter an accessibility barrier or need content in an alternative format, please contact us:

  1. Email: accessibility@africanii.com (monitored every business day — preferred channel)
  2. Phone: (210) 712-2892 (Monday–Friday, 9 AM–5 PM Central Time)
  3. Mail: Africanii Accessibility Team, 110 East Houston Street, Suite 400, San Antonio, TX 78205

When reporting, please describe: the specific page or feature; your assistive technology and browser or device; the nature of the difficulty; and any error messages.

Response Stage Commitment Delivery Method
Acknowledgement As reasonably practicable Email confirmation with reference number
Substantive response As reasonably practicable Email describing our assessment and proposed solution or timeline
Resolution or accessible alternative As reasonably practicable Email with resolution confirmation or accessible alternative (HTML version, phone assistance)
Complex issues As reasonably practicable Email with estimated resolution date and interim workaround

Africanii seeks to respond to accessibility inquiries and accommodation requests within a reasonable time. Actual response times may vary depending on request volume, complexity, staffing, and operational conditions.

If you are not satisfied with our response, you may escalate to:

  1. US Department of Justice ADA Information Line: 1-800-514-0301 (voice) | 1-833-610-1264 (TTY) | ada.gov
  2. DOJ ADA Complaint Portal: ada.gov/complaint
  3. Texas Governor's Committee on People with Disabilities: hhs.texas.gov/ada

 

11. Ongoing Commitment

  1. Africanii may periodically engage qualified accessibility professionals to evaluate accessibility practices and identify improvement opportunities.
  2. Automated scanning: Axe and Lighthouse run on every production deployment; Accessibility issues may be prioritized and remediated based on severity, feasibility, and operational considerations.
  3. Design review: every new feature or UI change is reviewed against WCAG 2.1 Level AA before code is written.
  4. Manual testing: NVDA, VoiceOver, and TalkBack testing before every major release.
  5. Staff training: all engineers, designers, and product managers complete accessibility training annually. New hires within their first 30 days.

 

12. Accessibility Disclaimer

While Africanii works to improve accessibility and usability, we do not warrant that the Platform will be accessible to every user in every circumstance or compatible with every assistive technology, device, browser, operating system, or third-party service. Accessibility is an ongoing process of evaluation and improvement.

 

 

 

 

EXECUTION & ACKNOWLEDGMENT

Accessibility Statement & ADA Commitment — Effective May 1, 2025

 

This document is duly authorized, adopted, and published by Africanii, Inc., a Texas corporation, effective May 1, 2025, as part of Africanii's platform legal framework governing all users of africanii.com and its iOS and Android mobile applications across all 50 United States and US territories.

 

NON-CONTRACTUAL ACCESSIBILITY STATEMENT

This Accessibility Statement describes Africanii's accessibility goals, practices, and ongoing efforts. It is provided for informational purposes and does not create contractual rights, warranties, guarantees, or independent legal obligations beyond those required by applicable law. Africanii may update this Statement as accessibility features, technologies, legal requirements, and operational practices evolve.