Accessibility Statement

1. Conformance target

Our target standard is WCAG 2.1 Level AA. This is the standard referenced by the U.S. Department of Justice as a benchmark for ADA Title III compliance, by the U.S. Section 508 Refresh, and by many U.S. state procurement regulations.

We are not yet able to assert full conformance and we make no guarantee that every screen meets every Level AA success criterion today. We track known gaps and remediate them as part of normal engineering work.

2. What we do

• Semantic HTML. Pages are structured with landmarks (nav, main, footer), headings in document order, and lists where they belong.
• Keyboard navigation. Interactive elements are reachable in a logical order using Tab; visible focus indicators are preserved.
• Color contrast. Text and UI controls target contrast ratios at or above WCAG AA thresholds (4.5:1 for body text, 3:1 for large text and UI components).
• Form labels. Every form control has an explicit label or accessible name; required fields are marked programmatically as well as visually.
• Status messages. Asynchronous status updates (uploads, job completion) are surfaced via aria-live regions so they are announced by assistive technology.
• Alt text. Decorative SVGs are marked aria-hidden="true"; meaningful images include descriptive alt attributes.
• Modal dialogs. Sign-in / sign-up modals are provided by Clerk, which manages focus trap and dismiss behavior to AA standards. We test them on every release.

3. Known limitations

The following are areas where we know we are not yet at full conformance. They are open work items.

• Translated PDF outputs. Translated PDF documents inherit the structural fidelity of the source PDF. If the source is a tagged, accessibility-ready PDF, the translated output will preserve those tags. If the source is image-only or untagged, the translated output cannot be made accessible by translation alone.
• Course content. Accessibility of the course content uploaded to CoursePortify is the responsibility of the customer. We do not modify accessibility metadata in IMS Common Cartridge packages.
• Long-running progress. Long-running background jobs (translation, evaluation) emit polling-based status updates. We continue to refine these for assistive-technology friendliness.

4. How we test

• Manual keyboard-only walkthroughs of the dashboard, upload flow, checkout flow, and download flow on every material release.
• Automated accessibility scans (axe-core) integrated into our front-end review process.
• Periodic screen-reader spot checks on macOS VoiceOver and Windows NVDA.
• Color-contrast verification on the editorial palette and on any added components.

5. Alternative formats

If you need a CoursePortify page or document in an alternative format — large print, plain text, captioned demo video — please email contact@koneroanalyticsml.com with subject Accessibility request. We will respond within two (2) U.S. business days and provide an accessible alternative.

6. Feedback & complaints

If you encounter an accessibility barrier on CoursePortify or believe our service does not meet your needs, please tell us. We treat accessibility feedback as a customer-blocker bug and prioritize it accordingly.

• Email: contact@koneroanalyticsml.com (subject: Accessibility feedback).
• What to include: the page or feature involved, the assistive technology or browser you were using, and the specific issue. A screenshot or short recording is helpful but not required.
• Response time: within 2 U.S. business days, with a remediation plan and ETA where applicable.

7. Enforcement

If you believe we have failed to address an accessibility concern adequately, you may also file a complaint with the appropriate regulator in your jurisdiction. In the United States, the U.S. Department of Justice handles ADA complaints at www.ada.gov.

8. Changes

We will revise this statement as we improve CoursePortify's accessibility posture. Material changes are dated at the top of the page.