Accessibility Statement

1. Our Commitment

RANKTYPE LLC is committed to making its digital presence accessible to people with disabilities. We treat accessibility as an ongoing program — not a one-time project — and we plan, design, build, test, and maintain ranktype.com with that commitment in mind. We apply the same principles to materials we produce for clients as part of paid engagements, subject to the scope agreed in the applicable Statement of Work.

This statement explains what we are targeting, what we have done, what we know is still imperfect, how we test, and how to reach us if you run into a barrier.

2. Standards and Frameworks

The Site targets the following standards:

• WCAG 2.2, Level AA — the current consensus standard for web accessibility, recommended by the W3C as of October 2023.
• Section 508 (36 C.F.R. Part 1194, Revised 508) — required for U.S. federal agencies and their vendors; incorporates WCAG 2.0 AA, and we apply 2.2 AA.
• ADA Title III — as interpreted by the DOJ and federal courts for websites of places of public accommodation; our U.S. civil-rights baseline.
• EN 301 549 (V3.2.1) — the European Union harmonized accessibility standard; incorporates WCAG 2.1 AA, and we apply 2.2 AA.
• AODA (Ontario, Canada) — Integrated Accessibility Standards Regulation, WCAG 2.0 AA, for organizations subject to AODA.

Where a standard references an earlier version of WCAG, we apply the more recent 2.2 AA criteria as our working baseline.

3. Conformance Statement

ranktype.com partially conforms with WCAG 2.2 Level AA. “Partially conforms” means that some parts of the content do not fully conform to the accessibility standard. This is the conformance phrasing recommended by the W3C Web Accessibility Initiative.

This statement is based on:

• automated testing (listed in Section 5),
• manual testing with assistive technologies (listed in Section 5),
• a component-level self-review conducted on April 18, 2026, and
• user feedback received since the prior review.

This self-assessment does not replace an independent audit. Our plans for independent conformance testing are described in Section 6.

4. Measures We Have Taken

The Site is built and maintained with these practices:

Structure and semantics

• Semantic HTML (landmarks, lists, headings, buttons vs. links).
• Logical, hierarchical heading structure — one h1 per page; h2 / h3 nested without gaps.
• ARIA used only where native HTML is insufficient, following the “first rule of ARIA.”
• lang attribute set on the html element.

Perceivable content

• Descriptive alt text for meaningful images; empty alt="" for purely decorative images.
• Color contrast of at least 4.5:1 for normal text and 3:1 for large text and UI components.
• Information is not conveyed by color alone; additional cues (icons, text, underlines) accompany color.

Operable interface

• Full keyboard operability — every interactive element is reachable and usable without a mouse.
• Visible focus indicators with at least 3:1 contrast against the adjacent background.
• Skip-to-content link at the top of every page.
• No keyboard traps; modal dialogs trap focus while open and return focus on close.
• No time-limited interactions that cannot be extended or disabled.
• Target size of at least 24 × 24 CSS pixels for interactive controls (WCAG 2.2 SC 2.5.8).

Understandable content

• Plain, scannable writing in client-facing copy.
• Consistent navigation and consistent identification of repeated components.
• Form fields have associated <label> elements; required fields are announced; errors are programmatically associated and described in text.

Robust delivery

• Valid HTML, verified with the W3C validator.
• Responsive design — content reflows without horizontal scrolling at 320 CSS pixels wide and remains usable at 200–400% zoom.
• Respects user preferences for reduced motion (prefers-reduced-motion) and color scheme (prefers-color-scheme) where applicable.

5. How We Test

5.1 Automated Tooling

We run the following automated checks on the Site on every release and on a scheduled monthly cadence:

• axe-core (via CI) — WCAG 2.2 A / AA rule set, executed against each page template.
• Google Lighthouse — accessibility score plus best-practices and performance signals relevant to accessibility (color contrast, tap targets, viewport).
• WAVE (by WebAIM) — spot checks on production pages.
• W3C HTML validator — catches parse errors that commonly break assistive technology.
• pa11y (or equivalent) — a gated smoke test in CI.

Automated tools catch roughly 30–40% of WCAG issues. They are a floor, not a ceiling.

5.2 Manual Testing with Assistive Technology

On a quarterly cadence — and for any significant template or navigation change — we manually test the Site with the following combinations:

• NVDA (latest) — Firefox and Chrome on Windows.
• JAWS (latest stable) — Chrome on Windows.
• VoiceOver — Safari on macOS and iOS.
• TalkBack — Chrome on Android.
• Dragon NaturallySpeaking or Voice Control — Chrome / Safari.
• Keyboard only (no mouse, no trackpad) — all supported browsers.
• Switch Control — macOS / iOS.

5.3 Browser and OS Support

We verify accessibility on the latest two major versions of the following browsers:

• Chrome (Windows, macOS, Android)
• Safari (macOS, iOS)
• Firefox (Windows, macOS)
• Microsoft Edge (Windows)

5.4 Lived-Experience Testing

Automated and manual testing do not replace testing with people who use assistive technology daily. At least once per year we engage testers with disabilities — either through an agency partner or through our own network — to run task-based sessions on the Site. Findings feed the remediation roadmap.

6. Independent Audit

An independent WCAG 2.2 AA audit of the Site is planned. The date and firm have not yet been confirmed. On completion we will publish the summary findings, the conformance level achieved, and the remediation plan on this page.

Self-assessment is a reasonable baseline but is not a substitute for an independent audit — particularly for organizations that market to enterprise and government buyers. Until an independent audit is completed, this statement reflects our self-assessment only.

7. Known Limitations

We have no known WCAG 2.2 AA barriers on the Site at this time. We believe in naming issues instead of hiding them — when a barrier is identified through testing or reported by a visitor, we will publish it here with the affected surface, the specific barrier, a target fix date, and a workaround, and update this page accordingly.

If you encounter anything on the Site that you believe is a barrier, please tell us using the contact information in Sections 13 and 14.

8. Third-Party Components and Procurement

Some functionality on ranktype.com is provided by third-party components (for example, the cookie consent banner). Those components are designed and maintained by their respective vendors, and their conformance with WCAG 2.2 AA is outside our direct control.

To manage this risk we:

• Request a VPAT / ACR (Voluntary Product Accessibility Template / Accessibility Conformance Report) from every vendor before adoption.
• Prefer vendors with published accessibility commitments and a track record of fixes.
• Re-evaluate annually and at each major vendor release.
• Log issues upstream when we find them, and track the vendor’s response.
• Provide workarounds for any barrier a vendor cannot fix in a reasonable timeframe.

9. Content Authoring Standards

Accessibility is easy to break one post at a time. Everyone at RANKTYPE who creates or reviews Site content follows our internal authoring checklist, which includes:

• Writing descriptive alt text for every meaningful image, and leaving decorative images with alt="".
• Using descriptive link text (“read the 2026 paid-social benchmark report”), never bare “click here,” “read more,” or raw URLs.
• Using built-in heading styles in source systems rather than visually formatted text, so the heading hierarchy stays semantic end-to-end.
• Writing in short sentences, short paragraphs, and scannable subheads.
• Providing text summaries of data visualizations and images of text.
• Testing any embedded form, calculator, or interactive content with a keyboard and a screen reader before publication.

10. Staff Training

Everyone at RANKTYPE who designs, builds, or publishes to the Site follows the internal accessibility authoring checklist in Section 9 and is responsible for meeting the testing practices in Section 5. Accessibility is reviewed as part of every design and code review.

11. Accommodations and Alternative Formats

If any information or functionality on ranktype.com is inaccessible to you, or you need content in an alternative format, we will provide an equivalent on request. Common alternatives we can provide include:

• Plain-text or HTML version of any document.
• Transcript of a video or audio recording.
• Descriptive summary of a chart or infographic.
• Information delivered by email instead of the Site.
• Large-print or reformatted version of a document.

To request an accommodation, email accessibility@ranktype.com. Please include:

1. The page URL or a description of the content you are trying to reach.
2. The barrier you encountered (for example, “the cookie banner is not reachable by keyboard”).
3. The assistive technology you are using, if relevant.
4. Your preferred format and how you would like us to reply.

We will never ask you to disclose a diagnosis or provide medical documentation to receive an accommodation on the Site.

12. Response and Remediation Service Levels

We commit to the following service levels for accessibility requests and reported barriers:

• Acknowledge receipt — within 1 business day.
• Substantive response — within 5 business days.
• Critical barrier fix (blocks a core task — contact form, navigation, legal page) — 10 business days, or a workaround provided within 5 business days.
• High-priority fix (significant but non-blocking) — 30 business days.
• Medium / low-priority fix — scheduled into the next quarterly release.
• Alternative-format delivery (document, transcript, summary) — within 5 business days of a complete request.

If we cannot meet any of the above for a specific request, we will explain why and agree a revised timeline with you.

13. Feedback, Complaints, and Escalation

13.1 Talk to us first

We would much rather hear from you directly than have you navigate an external process. Reach us at accessibility@ranktype.com or by any of the methods in Section 14.

13.2 Escalation within RANKTYPE

If a response is not satisfactory or does not arrive within the service levels in Section 12, escalate to the RANKTYPE Head of Operations at legal@ranktype.com or to the postal address in Section 14, marked “Attn: Accessibility Escalation.”

13.3 External recourse

You also have the right to bring your concern to external bodies, including:

• U.S. Department of Justice — ADA Information Line at 1-800-514-0301 (voice) / 1-833-610-1264 (TTY); online complaint at civilrights.justice.gov.
• Your State Attorney General’s office — most U.S. states accept ADA and state civil-rights complaints.
• EU residents — contact your national enforcement body for the Web Accessibility Directive and EN 301 549.
• UK residents — contact the Equality Advisory and Support Service (EASS).
• Canadian residents under AODA-covered organizations — contact the Accessibility Directorate of Ontario or the Canadian Human Rights Commission as applicable.

14. Contact

We accept feedback in whatever format works best for you — email or a letter in the mail.