TekFocus AI Academy

Accessibility Statement

Last updated: May 25, 2026

The commitment

TekFocus is committed to making tekfocus.com accessible to all visitors, including visitors with disabilities. We treat accessibility as a baseline requirement, not a marketing feature. Federal, state, local government, and enterprise buyers notice accessibility immediately; the firm's federal track record and our own operating principles both demand that the site meet a defensible accessibility standard.

This statement describes the standard we are working toward, what we have done so far, where the work continues, and how to report an issue.

The standard we follow

We are working toward conformance with the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA, published by the World Wide Web Consortium (W3C). WCAG 2.1 AA is the current de facto standard for U.S. federal procurement (under Section 508 of the Rehabilitation Act as updated), most U.S. state and local government accessibility requirements, and most enterprise accessibility procurement reviews.

"Working toward" is the honest framing. The site has been built against WCAG 2.1 AA from the design and implementation phases forward, but TekFocus has not yet commissioned a formal third-party accessibility audit. This statement will be updated to reflect formal conformance status once an audit is complete.

What we have done

The accessibility decisions baked into the current site include:

  • Color and contrast. The primary content combination — cream paper background with deep ink foreground — was selected for high contrast and verified against WCAG 2.1 AA contrast ratios for normal and large text. Accent colors (purple for headlines and links, gold for high-impact elements) are applied with attention to contrast on standard and focused states.
  • Typography. The site uses Fraunces for display, IBM Plex Sans for body, and IBM Plex Mono for operational accents. Type sizes, line heights, and weights are set to support readability at default browser settings and to scale cleanly when users adjust their browser zoom or font-size settings.
  • Heading hierarchy. Each page uses a proper semantic heading structure — one <h1> per page, descending <h2> and <h3> for sections — so screen readers can navigate by heading.
  • Keyboard navigation. All interactive elements (links, form fields, buttons) are reachable and operable using a keyboard alone, with visible focus indicators on every focusable element.
  • Forms. The contact form uses associated <label> elements, descriptive field names, clear error messages tied to the relevant field, and required-field indication that does not rely on color alone.
  • Images and diagrams. Images carry descriptive alt text. Decorative images are marked as such so screen readers skip them. SVG diagrams (where present) include text alternatives.
  • Page structure. Each page uses semantic HTML landmarks (<header>, <main>, <nav>, <footer>) and skip-to-content patterns to support assistive technologies.
  • Motion and animation. Motion on the site is minimal and respectful — no scroll-triggered effects, no auto-playing media. The CSS prefers-reduced-motion setting is honored where animation is present.
  • Responsive layout. The site is fully responsive and usable at standard mobile, tablet, and desktop widths, and at browser zoom levels up to 200%.

Known limitations

We disclose limitations because honesty is a military veteran habit:

  • Cloudflare Turnstile is used on the contact form for bot protection. Turnstile is designed to be more accessibility-friendly than traditional CAPTCHA challenges (it runs invisibly for most users), but it can occasionally present a visible challenge that may not be fully accessible for users relying on certain assistive technologies. If you encounter a Turnstile challenge that you cannot complete, email info@tekfocus.com directly — we will respond by the same channel any contact form submission would reach.
  • Formal third-party audit. No formal third-party accessibility audit has been completed yet. This statement will be updated when one is.
  • Future content. As TekFocus adds new content over time — additional service-line pages, framework deep-dives, Insights articles, framework diagrams — each new addition is built against the same standard. New content has had less time in front of users than the launch surface.

Reporting an accessibility issue

If you encounter content on tekfocus.com that is difficult to use or inaccessible to you for any reason, please tell us. Specific reports are most useful — but a general note ("I can't navigate this page with my screen reader") is also welcome.

Email: info@tekfocus.com
Subject line: Accessibility — [page name or URL where the issue occurred]

Where you can, please include:

  • The page or URL where you encountered the issue
  • Your assistive technology (screen reader, voice control, switch device, etc.) and browser, if known
  • A description of what was difficult
  • What you were trying to do

We will acknowledge your report within five business days and provide a response — including the remediation timeline where applicable — within fifteen business days.

TekFocus does not retaliate, charge, or condition any future engagement on whether you have reported an accessibility issue. Reporting an issue does not affect any commercial relationship with TekFocus in any way.

Ongoing commitment

Accessibility is treated as continuous work, not a one-time launch checklist. Every meaningful change to tekfocus.com is reviewed against the WCAG 2.1 AA standard before it ships. Periodic accessibility reviews are part of the site's editorial governance cycle. As tooling and standards evolve — including the eventual move to WCAG 2.2 — TekFocus will update this statement and the site itself to reflect current best practice.

Contact

For any accessibility questions, concerns, or improvements you would like to suggest:

info@tekfocus.com
TekFokus, Inc. DBA TekFocus
North Texas / Dallas–Fort Worth