Accessibility Statement

Last updated: May 26, 2026

ComputerScienceHomeworkHelp.com is operated by WitNip Inc, a Delaware-incorporated company. Every CS student, including students with disabilities, gets equal access to this site. This statement covers the target standard, the gaps tracked today, the assistive technologies tested, and the path to report a barrier.

1. Target standard

The site targets Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA, the European harmonised standard EN 301 549, US Section 508 of the Rehabilitation Act, the Americans with Disabilities Act (ADA), and the European Accessibility Act (EAA). These standards cover keyboard navigation, screen-reader output, contrast ratios, resizable text, focus indicators, and labelled form fields.

2. What works today

  • Semantic HTML structure with one h1 per page and an ordered heading sequence.
  • Keyboard navigation across every interactive element, including the main nav, FAQs, and the assignment submission form at /submit/.
  • Visible focus rings on links, buttons, and form fields in both light and dark themes.
  • Form fields with explicit <label> elements and autocomplete hints on the submission form.
  • 4.5:1 minimum contrast for body text against background in light mode, verified with axe-core.
  • A "Skip to content" link at the top of every page for screen-reader and keyboard users.
  • Descriptive alt text on every meaningful image, including expert profile photos on the homepage.
  • ARIA labels on the JivoChat widget launcher, the search dialog at /search/, and the file-upload control on the submission form.
  • Manrope font loaded with font-display: optional so text renders in the fallback metric-matched stack within 100ms, preventing layout shift for screen-magnification users.

3. Known gaps

The following items are tracked for remediation:

  • Dark-mode contrast on muted helper text (under --muted-foreground) lands at 4.2:1 against the dark surface, 0.3 below the WCAG AA target of 4.5:1. Light mode passes. Fix scheduled with the next design pass.
  • The JivoChat live-chat widget (operated by Jivosite Ltd.) does not meet WCAG 2.2 SC 2.5.7 (Dragging Movements) or SC 2.5.8 (Target Size). Screen-reader announcements on incoming messages are limited. Email at [email protected] or WhatsApp are accessible alternatives.
  • Inline code samples on the language pages (Java, Python, C++, C, JavaScript, Assembly) use syntax-coloured tokens without per-token aria-label descriptions. Screen readers announce raw source. A semantic code-block component with optional plain-text transcripts is in the backlog.
  • The pricing comparison table at /pricing/ uses a horizontal scroll on viewports under 480px wide; a stacked card layout for the same data is planned.

4. Compatible assistive technology

The site is tested against the following stack:

  • VoiceOver on macOS Sonoma and iOS 18 (Safari).
  • NVDA 2024.4 on Windows 11 (Firefox, Chrome).
  • JAWS 2024 on Windows 11 (Chrome).
  • TalkBack on Android 14 (Chrome).
  • Keyboard-only navigation (Tab, Shift+Tab, Enter, Space, Esc, arrow keys for menus).
  • Voice Control on macOS and Voice Access on Android for hands-free interaction.
  • Browser zoom up to 200% without horizontal scroll on viewports of 1280px and above.

Untested combinations carry no conformance claim. Reports of failures on other assistive tech feed the backlog.

5. How to report a barrier

Email [email protected] with the subject line "Accessibility". Include the page URL, the assistive technology in use, and a description of what blocked the task. The team responds within 5 business days. Accessibility fixes take priority over cosmetic work in the queue.

6. Standards followed

  • WCAG 2.1 Level AA (W3C).
  • EN 301 549 v3.2.1 (European harmonised standard for ICT accessibility).
  • Section 508 of the US Rehabilitation Act (29 U.S.C. § 794d).
  • Americans with Disabilities Act (ADA), Title III digital accessibility expectations.
  • European Accessibility Act (Directive 2019/882), in force June 28, 2025.

7. Date of this statement

This statement was last reviewed and updated on May 26, 2026. The next scheduled review falls in November 2026, or sooner if a substantial site change ships.