Skip to main content

Legal

Accessibility Statement

Last updated: June 19, 2026

GeeksProgramming.com is operated by WitNip Inc, a company registered in Delaware, United States, with delivery teams in the United States and India. We want every student to be able to use this site, whether they are looking for Java, Python, C, C++, JavaScript, SQL, or any other kind of help. This statement explains what we are working toward, what is accessible today, the gaps we know about, and how to tell us when something does not work for you.

1. The standard we work toward

We aim for conformance with the Web Content Accessibility Guidelines (WCAG) 2.1 and 2.2 at Level AA. WCAG is the international standard for web accessibility, written for designers and developers. It defines three levels of conformance: Level A, Level AA, and Level AAA. Level AA is the level most laws and policies reference, and it is the level we hold ourselves to. It covers keyboard navigation, screen-reader support, sufficient colour contrast, text that resizes without breaking, visible focus indicators, and clearly labelled forms.

Accessibility is not a one-time project. We treat it as ongoing work and review this statement when we make a significant change to the site, so it stays an honest picture of where we are rather than a promise we made once and forgot.

2. What is accessible today

The following features are in place across the site. Each one maps to a specific WCAG success criterion, so the claim can be checked rather than taken on trust.

  • Semantic HTML with one h1 per page and a logical heading order, so screen readers can navigate by structure (WCAG 1.3.1, 2.4.6).
  • Full keyboard access to every link, button, and form field, with no keyboard traps (WCAG 2.1.1, 2.1.2).
  • A visible focus indicator on every interactive element, in both light and dark mode (WCAG 2.4.7).
  • A "Skip to main content" link at the top of every page for keyboard and screen-reader users (WCAG 2.4.1).
  • Text contrast that meets the AA ratio for primary content in both light and dark mode (WCAG 1.4.3). The known exceptions are listed below.
  • Descriptive alternative text on every meaningful image, and empty alt on decorative ones (WCAG 1.1.1).
  • Explicit labels on every form field on the contact and upload pages (WCAG 1.3.1, 4.1.2).
  • Layout and text that reflow and stay readable at 200% zoom and on small screens (WCAG 1.4.4, 1.4.10).
  • A theme that follows your system light or dark setting, with no flashing or auto-playing motion (WCAG 2.3.1).

3. Known gaps we are tracking

We do not claim the site is perfect. We would rather be clear about what falls short and give you another way to reach us in the meantime. We are aware of the following and are working on each one:

  • Some secondary text, such as small captions, metadata labels, and table headers, can fall below the AA 4.5:1 ratio for small text in a few places. We are raising these to full AA.
  • A small number of older blog posts migrated from our previous site may contain images without alt text or tables without header markup. We are reviewing and fixing these as we find them.

4. How we test

We check accessibility in more than one way, because automated tools alone miss problems a real person would hit. Our process includes:

  • Automated checks during every build, which flag missing alt text, low contrast, and broken heading order before a page goes live.
  • Manual keyboard-only walkthroughs of the pages students use most: the homepage, the service pages, the contact form, and the upload form.
  • Screen-reader spot checks with VoiceOver and NVDA on the same core pages.
  • A self-review against the WCAG 2.1 and 2.2 Level AA success criteria, repeated when we release a significant design change.

5. Accessibility of the help you order

This statement covers our website. The way we deliver help is built around contact, not barriers. You talk to a real expert first at no cost, you pay 50% to start and the other 50% only after you are satisfied, and you can reach your expert by email or WhatsApp at any point. If a standard delivery format does not work for you, tell your expert and we will adjust. For example, we can provide plain-text explanations alongside screenshots, or walk through the code with you on a call instead of relying on written notes alone.

6. How to report a problem

If any part of this site is hard to use, or if an accessibility barrier stops you from getting the help you need, please contact us at help@geeksprogramming.com with "Accessibility" in the subject line. You can also call +1-302-520-2767. Tell us the page, what you were trying to do, and the device or assistive technology you were using if you can. We try to respond within 3 to 5 business days, and we prioritise accessibility fixes ahead of cosmetic ones.

7. Your privacy when you contact us

Anything you send us about an accessibility issue is handled the same way as every other message. Your details are not shared or sold, every expert who handles your work signs an NDA, and personal data tied to a project is permanently deleted 15 days after the project is complete.

8. Dates

This statement was first published on April 10, 2025 and was last reviewed and updated on June 19, 2026.