Accessibility Statement

1. Commitment

PirateSERP, an SEO research and content tool suite, is built so that people with disabilities can use every tool, page, and account setting. Accessibility is part of how each page is designed, built, and checked.

2. Conformance status

The Web Content Accessibility Guidelines (WCAG), a W3C standard, define requirements that make web content usable by people with disabilities. PirateSERP targets WCAG 2.2 at Level AA.

PirateSERP is partially conformant with WCAG 2.2 Level AA. Partially conformant means that some parts of the content do not fully conform to the standard. The known gaps are listed in Known limitations.

3. Measures in place

• Every page has a unique title, one main heading, and labeled regions for navigation and content.
• Every form field has a visible label, and every icon button has a text name that screen readers announce.
• Controls work with a keyboard and show a visible focus indicator, except where Known limitations says otherwise. A Skip to content link starts each public and tool page.
• Text meets a 4.5:1 contrast ratio against its background in both the light and dark themes.
• Selected tabs, pressed toggles, and expanded sections report their state to assistive technology, and status labels pair color with text or an icon.
• Error messages appear next to the field they describe and are announced to screen readers.
• Deleting data or making other changes that cannot be undone asks for confirmation first.
• Decorative motion stops when your device requests reduced motion, and the home page has a Pause animations button.
• Nothing on a page redirects you on a timer.
• Every chart has a Show data as a table section that lists the plotted values as text.
• Map results in GeoPin Generator and Business Search are also listed as text, with a Show on map button for each result.
• Every network graph has a list of its relationships and a control that opens a node's details from the keyboard. Topical Maps also has a Tree view.
• The HTML of every page, including the documentation site, passes the W3C Nu HTML Checker. The one exception is markup that third-party chart, dropdown, and globe libraries add in the browser, such as non-standard attributes inside chart graphics.

4. Known limitations

The following parts of PirateSERP do not fully conform yet, or have not been verified. If one of them blocks a task, email casey@pirateserp.com and PirateSERP provides the information another way.

• Content from other sources: Web pages you import or analyze, and text that AI models generate for you, can contain accessibility problems that PirateSERP does not control.
• Assistive technology testing: PirateSERP has not yet been tested with screen readers or by people with disabilities. Automated checks find many problems, but not all of them.

5. Compatibility and technical specifications

PirateSERP is tested in current versions of Google Chrome on desktop. It is built on standard web technologies and is designed to work in other current browsers and with assistive technology that supports them.

PirateSERP relies on the following technologies: HTML, WAI-ARIA, CSS, and JavaScript. The tools do not work with JavaScript turned off.

6. Assessment approach

PirateSERP assessed its own accessibility (self-evaluation) using these methods:

• axe-core, an automated accessibility testing engine, checked every page against its WCAG 2.0, 2.1, and 2.2 Level A and AA rules and its best-practice rules, in both the light and dark themes.
• The W3C Nu HTML Checker, the validator behind validator.w3.org, and html-validate checked the markup of every page as rendered in the browser.
• The same two validators checked every page of the documentation site.
• A manual review checked each page's layout, controls, forms, feedback, and motion against written design rules.

7. Feedback

Email casey@pirateserp.com to report an accessibility problem or to request information in a different format. Include the page address, what you tried to do, and the browser and assistive technology you use.

PirateSERP aims to reply within 30 days. Your report goes directly to the person who builds PirateSERP.