Accessibility Statement

Plain-English summary

EMERALD STATIC LLC is committed to making emeraldstatic.com usable by the widest possible audience, including people with disabilities. Our target standard is the W3C Web Content Accessibility Guidelines (WCAG) 2.2 Level AA, the same baseline used by the U.S. Department of Justice for ADA Title III compliance and by EN 301 549 for EU public-sector accessibility.

We treat accessibility as a build-time requirement, not a post-launch audit. Every page we ship is keyboard-navigable, screen-reader-friendly, and tested with axe-core and manual screen-reader passes before launch.

If you encounter a barrier on this site, please email legal@emeraldstatic.com and we will fix it. We aim to acknowledge accessibility reports within 2 business days and resolve confirmed issues within 30 days.

Conformance standard and applicable laws

Target standard: WCAG 2.2 Level AA. We measure new and updated content against this standard and use it as the success criterion for our internal QA process.

Applicable laws and frameworks we consider when designing and shipping this site:

• Americans with Disabilities Act (ADA) Title III — applies to places of public accommodation in the United States, which courts have increasingly applied to commercial websites.
• Section 508 of the Rehabilitation Act — applies to U.S. federal procurement; we use it as a working benchmark even though we are not a federal vendor.
• Air Carrier Access Act (ACAA) — not applicable to our services, but referenced for completeness.
• European Accessibility Act (EAA) — applies to private-sector e-commerce and consumer-services sites in the EU from June 2025; we follow its conformance baseline (EN 301 549 v3.2.1, which incorporates WCAG 2.1 AA and partially 2.2).
• UK Public Sector Bodies Accessibility Regulations 2018 — not directly applicable to private-sector sites, but we use it as a reference.

What we have done

Specific design and engineering decisions we have made on this site to support accessibility:

• Semantic HTML structure: landmarks (main, nav, header, footer), correctly nested heading hierarchy, lists for grouped content.
• Keyboard accessibility: every interactive element is reachable and activatable with Tab, Shift-Tab, Enter, and Space. The mobile menu, FAQ accordions, and audit widget all work without a mouse.
• Visible focus indicator on every focusable element, with sufficient contrast against the dark background.
• Color contrast: body text ≥ 7:1 (AAA), supporting text ≥ 4.5:1 (AA), and large text and UI components meet or exceed AA. We test with the WebAIM contrast checker on every theme change.
• Reduced-motion respect: scroll-triggered reveals, animated counters, sparkline draws, and brand-mark animations all honour the prefers-reduced-motion CSS media query.
• Form labels: every input has an associated <label>. Error messages are tied to the field with aria-invalid and aria-describedby.
• Images: meaningful alt text for content images, empty alt for decorative images. Stock photographs include photographer attribution that is hidden from screen readers because it duplicates an existing visible link.
• Skip-link to main content available at the very top of every page.
• Responsive layout that supports 200% browser zoom and reflows down to 320px viewport width without horizontal scrolling.
• Embedded video, where used, has accurate captions and a transcript.

Known limitations

We are open about issues we are aware of but have not yet fully resolved. We aim to fix everything on this list within 60 days of identification.

• The animated rank-climb sparkline on case studies is decorative — its data is also presented as readable text below the chart. Users on screen readers will read the text version, but a separate accessible name on the SVG would be an improvement and is on our backlog.
• Some marketing PDFs we link to from blog content (when we publish blog content) may not be fully tagged for screen-reader use. We tag new PDFs going forward and re-tag older ones as we identify them.
• Stock photography credits — visible at the bottom-left of each image — use a small typeface (9.5px). They are decorative metadata, not primary content; the image alt text remains the primary accessible description. We are evaluating a larger persistent variant.

If you find anything that should be on this list, please tell us.

How we test

Our testing approach combines automation and manual review.

• Automated: axe-core runs as part of our continuous integration pipeline. Pull requests that fail accessibility checks cannot be merged without an explicit override and an issue logged for follow-up.
• Manual: every new page or feature is tested with VoiceOver (macOS) and NVDA (Windows / Firefox) before release. We also keyboard-only navigate every interactive surface.
• User testing: we welcome feedback from people who use assistive technology. If you would like to be part of our beta-feedback group, email us — we offer a small honorarium for time spent reviewing pre-release builds.

We do not currently have a paid VPAT (Voluntary Product Accessibility Template) from an independent auditor. Enterprise prospects who require one can request a self-assessment ACR (Accessibility Conformance Report) summarising our WCAG 2.2 AA compliance posture under NDA.

How to report an accessibility barrier

If you cannot use part of this site, please email legal@emeraldstatic.com with "Accessibility" in the subject line and as much detail as you can share, including:

• The page or URL where you encountered the issue.
• What you were trying to do and what went wrong.
• Your operating system, browser, and any assistive technology you were using (and its version).

We acknowledge accessibility reports within 2 business days. Most issues are fixed within 30 days; complex issues that require design or third-party changes may take up to 90 days, in which case we keep you updated on progress.

Alternative ways to reach us

If you are unable to use email, you can reach us by phone at +1 (912) 915-9764 during U.S. Mountain Time business hours (Mon–Fri, 9am–6pm). Voicemail and TTY/TDD relay calls are returned within 1 business day. We do not currently maintain a separate accessibility hotline.

Postal mail: EMERALD STATIC LLC, 259 E Works St, Sheridan, WY 82801, USA.

Enforcement procedure (for U.S. residents)

If you are not satisfied with our response to an accessibility concern, you may contact:

• The U.S. Department of Justice — ada.gov/file-a-complaint/ — for ADA Title III concerns.
• Your state Attorney General — many states accept and forward accessibility complaints under state consumer-protection law.
• An independent advocacy organisation such as the National Federation of the Blind (nfb.org) or the American Council of the Blind (acb.org).

We will cooperate in good faith with any such enquiry.

Changes to this statement

We review this statement at least annually and update it whenever the underlying conformance evidence changes — e.g. a new standard is adopted, a new feature is added, or an audit is completed. The version number and last-updated date at the top track each change.