Built for everyone.

What we've built in

Accessibility is not a feature we add later. It is part of how every page is built. The current implementation includes:

• ✓Skip-to-main-content link. Press Tab on any page and a green "Skip to main content" link appears at the top-left, letting keyboard users jump past the navbar in one keystroke. This is the WCAG 2.4.1 "Bypass Blocks" technique - standard practice across Stripe, Apple, GitHub, and the W3C's own examples.
• ✓Semantic HTML. Every page uses real <nav>, <main>, <section>, <footer> landmarks so screen readers can announce structure correctly.
• ✓Keyboard navigation. Every interactive element - tools, modals, accordions, the rule expansion toggle on the Spam Score page - is reachable and operable with Tab, Enter, Space, and Esc. No mouse required.
• ✓Visible focus indicators. Focused elements show a clear outline so keyboard users always know where they are on the page.
• ✓ARIA states where needed. Expandable regions use aria-expanded, modals use role="dialog" + aria-modal, mobile drawers are properly announced.
• ✓Color contrast. Body text and primary actions meet or exceed the 4.5:1 contrast ratio required for AA. Light and dark themes are both audited.
• ✓Resizable text. All text scales up to 200% without breaking layout. The spam-score editor and result panels remain usable at high zoom levels.
• ✓Form labels. Every input has an associated label or accessible name. Error messages are announced to assistive technology.

What we're still working on

Honest list. We don't claim full conformance because we have not yet completed a third-party WCAG audit. The areas where we know more work is needed:

• ~PDF reports generated by the Pro tier (when shipped) need a tagged-PDF accessibility pass. We will not ship Pro PDF reports until this is complete.
• ~Some tool result tables on the DNS Checker and Header Analyzer pages have dense data layouts that we plan to improve with explicit table headers and row scoping.
• ~Screen reader testing currently covers VoiceOver (macOS / iOS) and NVDA (Windows). We have not yet tested with JAWS or TalkBack and welcome feedback.
• ~Reduced motion preference is partially honored. Some non-essential animations (the live-typing score updates) do not yet respect prefers-reduced-motion: reduce. On the roadmap.

About the "Skip to main content" link

Standards we follow

• ·WCAG 2.1 Level AA - the international Web Content Accessibility Guidelines published by the W3C.
• ·EU Accessibility Act (2025) - we treat this as the working bar for the European market.
• ·ADA Title III (United States) - we follow current case-law guidance on commercial websites.
• ·India RPwD Act (2016) and DPDP Act (2023) - for our Indian users we follow the accessibility provisions of the Rights of Persons with Disabilities Act and the privacy provisions of DPDP.

Reporting an accessibility issue

If you find a page or feature on EmailSheriff that does not work with your assistive technology, or if a contrast / keyboard / screen-reader issue is blocking you, we want to know. Email [email protected] with the page URL, the assistive technology you use (screen reader, keyboard, switch device, etc.), and what you were trying to do. We treat accessibility reports as priority bug tickets.

Independent verification

This statement is a self-assessment. We have not yet engaged an external auditor. We aim to complete a third-party WCAG 2.1 AA audit within twelve months of our paid-tier launch, and we will publish the audit report on this page.