Legal

Accessibility Statement

Effective date: June 22, 2026

Emerhub aims for the website at emerhub.com to be usable by everyone, including visitors with disabilities. This statement reflects our current accessibility posture, the known gaps we are working on, and how to report problems we have not noticed.

We target conformance with the Web Content Accessibility Guidelines (WCAG) 2.1 at level AA. The status below reflects an internal audit conducted on June 22, 2026, against the live emerhub.com site.

Conformance status

The site partially conforms to WCAG 2.1 level AA. "Partially conforms" means that some parts of the content do not yet fully conform; specific items are listed below under "Known gaps".

What is in place today:

Skip-to-content links on every public page so keyboard users can bypass the navigation.
Semantic landmarks (<main>, <header>, <footer>, <nav>) on every page so assistive tech can jump between page regions.
Form fields have associated <label> elements, including visually-hidden labels where the visual design relies on placeholders or adjacent headings.
Focus indicators are visible on every interactive element (orange outline) for keyboard users.
All animations honor the prefers-reduced-motion media query.
Mobile menu uses dialog semantics with focus management — Tab is trapped inside the drawer while open, focus is restored to the trigger on close, Escape closes the drawer.
Alt text is set on content images and intentionally empty for decorative images (per WAI guidance).
Heading hierarchy follows H1 → H2 → H3 without skipped levels on every page.
Color contrast meets AA for body text on its primary background pairings.

Known gaps

We are honest about where we still fall short. These items are tracked internally and being worked on:

Some secondary copy uses the muted color --ink-mute (#94a3b8) on white backgrounds — this meets AA for large text but fails for body text at 4.5:1. We are revising those usages.
A few inline elements embedded from third-party providers (HubSpot forms, Elfsight Google Reviews widgets, embedded videos) inherit their accessibility from the provider. Their conformance is outside our direct control; we monitor and raise issues with the vendors.
PDF documents linked from blog posts and legal pages are not all tagged for accessibility. We are auditing the set as part of the WP migration cleanup.
Some imported blog images from the legacy WordPress site lack descriptive alt text. We are filling in the gaps via the Media Library admin and the auto-import alt-text pipeline.

How we test

We assess accessibility through a combination of manual review, automated tooling, and assistive-tech testing. We do not rely on a single tool because each catches different issues.

Automated audits via axe-core and Lighthouse during development and on production deployments.
Manual keyboard-only navigation checks on every new page before launch.
Screen-reader spot checks with VoiceOver (macOS) and NVDA (Windows).
Color-contrast verification via the WebAIM contrast checker during design reviews.

Report an issue

If you find an accessibility barrier on emerhub.com — something that prevents you or someone you know from using the site, regardless of whether it is on the "known gaps" list above — please tell us. We treat accessibility reports as priority bugs.

Email us

accessibility@emerhub.com

Describe the page you were on, the device and assistive tech you were using, and what went wrong. We acknowledge within one working day and aim to ship a fix within ten.

Open mail

General contact

Talk to our team

If the issue is broader (e.g. a service question that the accessibility barrier prevented you from completing), reach the country team that handles your market directly.

Open contact page

Formal complaints

If you are not satisfied with our response to an accessibility report and you are based in the European Union, you can escalate to the relevant national enforcement body under the European Accessibility Act 2025. For other markets, contact your national accessibility regulator. We will cooperate fully with any formal investigation.

Accessibility Statement

Effective date: June 22, 2026

We target conformance with the Web Content Accessibility Guidelines (WCAG) 2.1 at level AA. The status below reflects an internal audit conducted on June 22, 2026, against the live emerhub.com site.

Conformance status

The site partially conforms to WCAG 2.1 level AA. "Partially conforms" means that some parts of the content do not yet fully conform; specific items are listed below under "Known gaps".

What is in place today:

Skip-to-content links on every public page so keyboard users can bypass the navigation.

Semantic landmarks (<main>, <header>, <footer>, <nav>) on every page so assistive tech can jump between page regions.

Form fields have associated <label> elements, including visually-hidden labels where the visual design relies on placeholders or adjacent headings.

Focus indicators are visible on every interactive element (orange outline) for keyboard users.

All animations honor the prefers-reduced-motion media query.

Mobile menu uses dialog semantics with focus management — Tab is trapped inside the drawer while open, focus is restored to the trigger on close, Escape closes the drawer.

Alt text is set on content images and intentionally empty for decorative images (per WAI guidance).

Heading hierarchy follows H1 → H2 → H3 without skipped levels on every page.

Color contrast meets AA for body text on its primary background pairings.

Known gaps

We are honest about where we still fall short. These items are tracked internally and being worked on:

Some secondary copy uses the muted color --ink-mute (#94a3b8) on white backgrounds — this meets AA for large text but fails for body text at 4.5:1. We are revising those usages.

A few inline elements embedded from third-party providers (HubSpot forms, Elfsight Google Reviews widgets, embedded videos) inherit their accessibility from the provider. Their conformance is outside our direct control; we monitor and raise issues with the vendors.

PDF documents linked from blog posts and legal pages are not all tagged for accessibility. We are auditing the set as part of the WP migration cleanup.

Some imported blog images from the legacy WordPress site lack descriptive alt text. We are filling in the gaps via the Media Library admin and the auto-import alt-text pipeline.

How we test

We assess accessibility through a combination of manual review, automated tooling, and assistive-tech testing. We do not rely on a single tool because each catches different issues.

Automated audits via axe-core and Lighthouse during development and on production deployments.

Manual keyboard-only navigation checks on every new page before launch.

Screen-reader spot checks with VoiceOver (macOS) and NVDA (Windows).

Color-contrast verification via the WebAIM contrast checker during design reviews.

Formal complaints