Skip to content
WCAG 2.1 AA Compliant

Accessibility Statement

SEOMate is committed to making our SEO tools accessible to everyone, including people with disabilities. We strive to exceed WCAG 2.1 AA standards in everything we build.

Last updated: August 25, 2026

AA
WCAG 2.1 Level
100%
Keyboard Navigable
4.5:1
Min Contrast Ratio
358px
Min Viewport
Our Commitment

Accessibility for All Users

SEOMate believes that SEO tools should be accessible to everyone, regardless of ability. We design and build every tool, page, and feature with accessibility as a core requirement — not an afterthought. Our goal is to ensure that all users, including those who rely on assistive technologies, can use our tools effectively and independently.

We follow the Web Content Accessibility Guidelines (WCAG) 2.1 at the AA conformance level. These guidelines explain how to make web content more accessible to people with disabilities, including visual, auditory, physical, speech, cognitive, and neurological disabilities.

Features

Accessibility Features

What we've implemented to make SEOMate accessible.

Keyboard Navigation

Every tool and page is fully navigable using only a keyboard. Tab, Enter, Escape, and arrow keys work as expected throughout the site.

Screen Reader Support

All interactive elements have proper ARIA labels and roles. Content is structured with semantic HTML for optimal screen reader compatibility.

Color Contrast

All text and interactive elements meet WCAG 2.1 AA contrast ratios (4.5:1 for normal text, 3:1 for large text) in both light and dark modes.

Focus Indicators

Clear, visible focus outlines are present on all focusable elements. Focus states use brand colors with sufficient contrast against backgrounds.

Reduced Motion

We respect the prefers-reduced-motion CSS media query. Animations and transitions are disabled or minimized for users who prefer reduced motion.

Responsive Design

All pages are fully responsive from 358px to 1920px+. No horizontal overflow, no broken layouts, no tiny tap targets on mobile devices.

Standards

Compliance Standards

The accessibility standards we conform to.

WCAG 2.1

Level AA

Web Content Accessibility Guidelines 2.1 at the AA conformance level.

Compliant

Section 508

US Federal

Section 508 of the Rehabilitation Act for federal accessibility standards.

Compliant

ADA

Title II & III

Americans with Disabilities Act requirements for web accessibility.

Compliant

EN 301 549

EU Standard

European accessibility standard for ICT products and services.

Compliant
Implementation

Technical Measures

Specific technical implementations for accessibility.

Semantic HTML5 elements used throughout (header, nav, main, footer, section, article)

Skip-to-content link as the first focusable element on every page

Proper heading hierarchy (h1 → h2 → h3) with no skipped levels

All form inputs have associated label elements

Images and icons include alt text or are marked as decorative

Color is never the sole indicator of meaning or state

Touch targets are minimum 44x44px on mobile devices

Text can be resized up to 200% without loss of functionality

No content flashes more than 3 times per second

Page language is declared in the HTML lang attribute

Transparency

Known Limitations

We're transparent about areas still being improved.

Some third-party embedded content (if any) may not fully conform to WCAG 2.1 AA.

Older browser versions may not support all accessibility features optimally.

We are continuously improving accessibility and some pages may have minor issues being addressed.

Feedback

Report an Accessibility Issue

Found an accessibility barrier? Let us know so we can fix it.

Email Us

Send details of the issue to our team.

hello@toolly.site

Feedback Form

Use our feedback page to report issues.

Submit Feedback →

GitHub Issues

Open an issue on our GitHub repository.

Report on GitHub →

Response time: We acknowledge accessibility reports within 48 hours and work to resolve issues within 5 business days.

Our Ongoing Commitment

Accessibility is an ongoing journey, not a destination. We continuously audit, test, and improve our tools with both automated tools and manual testing. Every new feature is checked for accessibility before release.

Last updated: August 25, 2026