ADA Compliance

Our Commitment

Accessibility Is a Requirement, Not a Feature

Online Tech Support LLC is committed to making onlinetechsupport.biz usable by everyone, including people who use screen readers, screen magnifiers, keyboard-only navigation, voice control, or other assistive technology.

Under the Americans with Disabilities Act (ADA), a business website is treated as a place of public accommodation, so accessibility is a requirement of this site rather than an optional extra. Our target is WCAG 2.1 Level AA, the standard the ADA and Section 508 both point to. We build to it, test against it, and re-test every time the site changes.

Conformance Status

Where This Site Stands

Every page we publish - the main site, the service-area pages, the legal pages you are reading now, and the client work in the portfolio - is built and verified to WCAG 2.1 Level AA.

That is 176 pages in total: 45 pages on the main site and 131 pages across the portfolio demonstrations (the HVAC, tree-removal, junk-removal, funnel, directory and showcase builds). Each one was audited page by page, and the results of that audit are shown below.

Verification combines five things, because no single method is sufficient on its own:

• Automated audits against the full WCAG 2.1 A and AA rule sets, run in a real browser at desktop and mobile widths.
• Keyboard-only walkthroughs - every link, button, form field, dialog and code block reached with Tab, Shift+Tab, Enter, Space and Escape.
• Focus-visibility checks - each interactive element is given real keyboard focus and its rendered indicator measured, so a control can never be reachable but invisible.
• Contrast measurement of the actual rendered colours on each surface, not assumed values from a palette file.
• Reflow and zoom checks at 320 CSS pixels wide and at 200% zoom, to confirm nothing is clipped and no horizontal scrolling appears.

Accessibility is maintained as part of the normal workflow: page changes are re-audited before they go live, and the fixes stay in the code rather than in a report.

What Is Built In

• Skip to main content is the first focusable element on every page that carries navigation, including the portfolio demonstrations, so keyboard and screen-reader users can bypass the header. It moves focus into the content and leaves the address bar clean.
• Complete keyboard operation. Every interactive element can be reached and operated without a mouse, including the screenshot viewer, which traps focus while open, changes images with the arrow keys, and returns focus to the thumbnail when closed with Escape.
• Visible focus indicators on every interactive element - a minimum 3 pixel outline in a colour that contrasts with the surface behind it, in both the light and dark areas of the site.
• Checked contrast for text and interface components: at least 4.5:1 for body text and 3:1 for large text, icons and control boundaries, measured against the real rendered background.
• Structure that screen readers can navigate: one h1 per page, an unbroken heading hierarchy, labelled landmarks for navigation, main content and footer, and descriptive link text instead of "click here".
• Text alternatives on every meaningful image, and decorative graphics hidden from assistive technology so they are not announced as noise.
• Consistent layout and link order across pages, so the site can be learned once and then used confidently.
• Reflow without loss: pages stay usable at 320 CSS pixels wide and at 200% zoom, with no horizontal scrolling or clipped content.
• Reduced motion is respected. If your device asks for reduced motion, scroll reveals, fades and transforms are switched off.
• No consent wall. This site sets no advertising or analytics cookies and loads no tracking scripts, so no cookie banner ever stands between you and the content.
• Labelled forms with messages that are announced, not communicated by colour alone.
• Status messages in dynamic areas - for example the copy-to-clipboard confirmation and the screenshot captions - are announced politely to assistive technology.

How We Test

Every page is scanned with axe-core against the WCAG 2.1 A and AA rule sets, at desktop and mobile viewport widths, with entrance animations allowed to finish first. Automated tools only catch part of the problem, so each page is then checked by hand for what a rule engine cannot judge: real tab order with real key presses, focus visibility, heading order out of context, dialog focus behaviour, zoom and reflow, and colour contrast computed from the pixels the browser actually paints.

Result of the most recent full pass (September 14, 2026): all 176 published pages - 45 on the main site and 131 in the portfolio - returned zero violations of the complete axe-core rule set, which covers WCAG 2.1 A and AA plus the accompanying best-practice rules: no contrast failures, no heading-order skips, no page missing a level-one heading or a main landmark, no interactive element without a visible focus indicator, and no loose content sitting outside a landmark.

That pass was not a formality - it produced real fixes across the portfolio builds:

• Links in body copy on the HVAC site were colour-only (WCAG 1.4.1) and are now underlined wherever they appear inside running text.
• Five palettes were darkened where a colour was too light for its surface: the location-page eyebrow labels against their list rows, the outlined numerals on the industry rows, the muted trust bars, the gold used for kickers and buttons on the picture-book page, the citrus accent on the food site, the badge colours on the directory site, and two footer lines that blended into their dark bands.
• Keyboard bypass links were added to the junk-removal, salad, old-west and funnel pages, and their focus rings were themed - three of these builds relied on the browser default (or on Bootstrap’s faint translucent glow) as the only focus cue.
• Main landmarks were added where pages had none, and heading levels were corrected where a footer or rate-row heading skipped a level.
• Utility bars and the "added to order" confirmation were given proper landmark and status roles instead of sitting as loose content outside every landmark.

Because these checks are automated, they are a floor rather than a guarantee: a rule engine cannot tell you that an alternative text reads well, or that a tab order feels logical. If you use assistive technology and something is awkward rather than broken, we would still rather hear from you than guess. A report from a real user carries more weight than any checklist.

Please Read

Known Limitations

We would rather name these than let you discover them:

• External links that open a new tab. Links to third-party sites such as the GitHub repository open in a new browser tab and do not yet say so in their link text. We are adding that announcement as pages are updated.
• Third-party services. Sites we link to (GitHub, Google, social platforms) and the fonts served by Google Fonts are outside our control. We do not depend on them for content or functionality.
• Screenshots. The galleries showing our software are images of the running application. They carry descriptive alternative text and captions, and open full size in an accessible viewer, but they are not interactive reproductions of the software.
• Entrance animations. Some cards and galleries fade in as you scroll. While a fade is in progress the text is briefly lighter than its final colour, so an automated scan taken mid-animation reports a contrast problem that is not present once the page settles. Every audit result published here is measured with animations complete.
• Composition canvases. Two portfolio pages are image-composition canvases rather than documents - the logo canvas and the HTML email template. They carry a main landmark and a heading, but they have no navigation to skip, so the "skip to main content" requirement does not apply to them.
• Our Android applications. The apps published on Google Play are held to the same commitment, but they are not covered by the verification described above. If you hit a barrier in an app, tell us which app and device and we will investigate it as a bug.

Tell Us About a Barrier

If any part of this website is not usable for you, or you need information from it in another format, contact us and say what you were trying to do. You do not need to diagnose the problem for us.

• Email contact@onlinetechsupport.biz with "Accessibility" in the subject line.
• Or use the contact form on the home page.
• Or call and ask for the accessibility contact - the number is on your invoice, and the fastest channel is always email.

We aim to acknowledge accessibility reports within 5 business days and to fix reported barriers within 30 days. If you need our reply in a particular format, a larger font, plain text, or read over the phone, say so in your message and we will accommodate it. Alternative formats of any document on this site are available on request at no cost.

If you are not satisfied with our response, you are entitled to complain to the U.S. Department of Justice through ada.gov, or to the civil-rights office in your state.

Statement Details

Standard referenced: WCAG 2.1 Level AA (also published as ISO/IEC 40500), together with the W3C’s guidance on writing accessibility statements.

Date of this statement: September 14, 2026. This statement is reviewed at least quarterly and after any material change to the site. When a limitation listed above is resolved, it moves into the features list in the same update.