Legal · Accessibility

Accessibility Statement

Our commitment to building an inclusive learning platform — what we conform to, what we don't yet meet, and how to reach us if you hit a barrier.

Last reviewed: July 2, 2026
Version: 1.0
Applies to: All visitors & registered users
Questions: accessibility@igurus.org

In short TL;DR

iGurus (operated by iBrothers Group LLC) is partially conformant with WCAG 2.2 Level AA. Most of the platform is accessible, but some features — mainly video captions and the PDF certificate — are not yet fully compliant. Known gaps, workarounds, and our remediation timeline are listed below. If you encounter a barrier, email accessibility@igurus.org — we respond within 5 business days.

WCAG 2.2

AA Target

Partial

Conformant

5-Day

Response

Feedback

Welcome

Indiana

USA Law

Conformance Status

The Web Content Accessibility Guidelines (WCAG) define three levels of conformance: Level A, Level AA, and Level AAA. iGurus targets WCAG 2.2, Level AA.

iGurus is partially conformant with WCAG 2.2 Level AA. Partial conformance means that some parts of the content do not fully conform to the accessibility standard. The non-conformances and known limitations are described in Section 02 below.

Standard targeted: Web Content Accessibility Guidelines (WCAG) 2.2, Level AA — published by the W3C Web Accessibility Initiative (WAI). Reference: w3.org/TR/WCAG22
Scope of this statement: This statement applies to the iGurus web platform at igurus.org and its subdomain pages, including the learner dashboard, course player, checkout, and all public-facing legal and informational pages.
Applicable regulations: ADA Title III (US); Section 508 of the Rehabilitation Act (US federal); EN 301 549 (EU/EEA, references WCAG 2.1 AA as minimum); the Equality Act 2010 (UK).
Operated by: iBrothers Group LLC, Greenwood, Indiana, USA.

Known Limitations

The following accessibility limitations are known and are actively being addressed. Please contact us if you observe something not listed here.

Video player — missing captions

WCAG criterion: 1.2.2 Captions (Pre-recorded) — Level AA
Description: Not all course videos currently have closed captions. New course submissions require captions from instructors; existing courses are being updated on a rolling basis.
Workaround: Enable auto-generated captions in your browser's media player, or contact accessibility@igurus.org to request a captioned version of a specific course.

Video player — keyboard control

WCAG criterion: 2.1.1 Keyboard — Level A; 2.1.3 Keyboard (No Exception) — Level AAA (target)
Description: The embedded video player does not support full keyboard control (play/pause, seek, volume) in all browsers without a mouse. We are in the process of replacing the player with an accessible alternative.
Workaround: Right-click the player and use browser-native video controls, which are keyboard-accessible in all major browsers.

PDF completion certificates

WCAG criterion: 1.3.1 Info and Relationships — Level A (tagged PDF)
Description: Completion certificates are generated as PDFs that are not fully tagged for screen readers. A tagged-PDF alternative is in development.
Workaround: Email accessibility@igurus.org to request an accessible plain-text version of your certificate.

Third-party payment iframes

WCAG criterion: 4.1.3 Status Messages — Level AA (varies by provider)
Description: Payment forms rendered in iframes by Stripe and other gateway partners are outside our direct control. Accessibility within those iframes is governed by each provider's own compliance programme. Stripe publishes its own accessibility statement at stripe.com/accessibility.
Workaround: Contact us at accessibility@igurus.org if you experience a payment barrier and we will assist you in completing your purchase by an alternative method.

This list reflects our self-assessment as of 2 July 2026. A formal third-party audit is planned prior to public launch. If you discover a barrier not listed here, please report it — see Section 05.

Technologies Relied Upon

The accessibility of iGurus relies on the correct support of the following web technologies by users' browsers and assistive technology.

HTML5: Semantic elements — nav, main, header, footer, section, article, aside — provide structural landmarks consumed by screen readers and other assistive technologies.
CSS3: Visual presentation is separated from structure. Focus styles, colour contrast ratios, and responsive layouts (using Flexbox and CSS Grid) are implemented in CSS. The prefers-reduced-motion media query is honoured to suppress non-essential animation.
WAI-ARIA 1.2: ARIA roles, states, and properties supplement native HTML semantics where needed — for example on modal dialogs (role="dialog"), live regions (aria-live), navigation landmarks, and icon-only buttons (aria-label).
JavaScript (ES6+): Interactive components — accordion menus, modal dialogs, toast notifications, and the course player — are built with JavaScript. Keyboard events (keydown / keyup) are handled alongside pointer events. Focus is managed programmatically when components open and close.
SVG: Inline SVG icons used in the UI are marked with aria-hidden="true" where decorative, or with a title element and aria-label where they convey meaning.

Compatibility has been verified against current versions of Chrome, Firefox, Safari, and Edge on Windows and macOS, and with Chrome on Android and Safari on iOS.

Assessment Approach

iBrothers Group LLC assessed the accessibility of iGurus using the following methods.

Self-evaluation: The iGurus development team conducted an internal review of the platform against WCAG 2.2 success criteria using browser developer tools, automated checkers (axe-core, Lighthouse), and manual keyboard and screen reader testing. This assessment covers the pages listed under Scope in Section 01.
Automated testing tools: axe-core (Deque), Google Lighthouse, and WAVE (WebAIM) were used to identify programmatic barriers such as missing alternative text, insufficient colour contrast ratios, unlabelled form fields, and missing ARIA attributes.
Assistive technology testing: Manual testing was performed with: NVDA + Firefox (Windows); VoiceOver + Safari (macOS and iOS); TalkBack + Chrome (Android); keyboard-only navigation (Tab/Shift+Tab/Enter/Space/arrow keys) in Chrome, Firefox, and Safari.
Planned third-party audit: An independent third-party accessibility audit is planned prior to public launch. This statement will be updated with the auditor's name and findings once the audit is complete. ⚠️ ATTORNEY ACTION: Commission this audit before launch.

Feedback & Contact

We welcome feedback on the accessibility of iGurus. Please let us know if you encounter barriers.

How to report an issue

Email accessibility@igurus.org and include:

The URL of the page or feature where you encountered the barrier.
A description of the problem — what you were trying to do and what happened instead.
The browser, operating system, and assistive technology you were using (if known).

We aim to respond within 5 business days and to resolve confirmed issues within 30 days where technically feasible. If an immediate fix is not possible we will provide a reasonable alternative means of accessing the content or completing the task.

Accessibility feedback, barrier reports & accommodation requests

accessibility@igurus.org

Prefer one inbox?

Report an accessibility barrier

Formal Complaints Procedure

If you are not satisfied with our response to your accessibility report, you have the right to escalate to the appropriate enforcement authority.

Before escalating, please contact us directly at accessibility@igurus.org — we prefer to resolve concerns collaboratively and promptly.

United States — ADA: File a complaint with the US Department of Justice Civil Rights Division under Title III of the Americans with Disabilities Act (ADA). Online: ada.gov/complaint. Phone: 1-800-514-0301 (voice), 1-800-514-0383 (TTY).
United States — Section 508: If your access barrier relates to a federally procured context, you may contact the relevant federal agency's Section 508 coordinator or the Access Board at access-board.gov.
European Union: If you are in an EU member state you may contact the national supervisory or enforcement body responsible for the Web Accessibility Directive (EU Directive 2016/2102). Your national authority's contact details are published by the European Commission.
United Kingdom: You may contact the Equality and Human Rights Commission (EHRC) under the Equality Act 2010 — equalityhumanrights.com. In Northern Ireland: Equality Commission for Northern Ireland — equalityni.org.

Date of Last Review

This accessibility statement was first prepared and published on 2 July 2026. It applies to the iGurus web platform at igurus.org.

Review schedule: This statement is reviewed and updated: (a) annually as a minimum; (b) whenever a significant change is made to the platform that may affect conformance; (c) after a formal third-party audit is completed. The date of last review is shown in the hero panel at the top of this page.
Next planned review: By 2 July 2027, or earlier upon completion of the planned third-party audit.
Version history: Version 1.0 — initial statement, 2 July 2026. Self-assessment only; third-party audit pending.

This statement is AI-drafted and requires review by a licensed attorney and a qualified accessibility specialist familiar with ADA Title III, the EU Web Accessibility Directive, and the UK Equality Act 2010 before it is presented as a finalised legal document.