Home› Accessibility Statement

Accessibility Statement

Built to be usable by everyone, including with assistive tech.

Accessibility Statement

Last updated: May 2026

Pogodex is committed to digital accessibility. We work to make the Site usable for the widest possible audience, including readers using assistive technologies (screen readers, keyboard navigation, voice input, magnification). This statement describes our accessibility target, the standards we aim for, known limitations, and how to request accommodations or report accessibility problems.

1. Accessibility standards

Pogodex aims to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA, published by the World Wide Web Consortium. WCAG 2.1 AA is the de facto international standard for web accessibility and is referenced by:

  • The European Accessibility Act (Directive 2019/882), enforceable from June 2025.
  • The U.S. Section 508 (29 U.S.C. § 794d) accessibility requirements as updated.
  • The UK Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations.
  • Italian Law 4/2004 (“Stanca Law”) on accessibility for public-sector and certain private-sector websites.

Although Pogodex is a private fan publication and not strictly required to meet these standards, we adopt them voluntarily as the right operating norm.

2. What we have done

Specific accessibility measures implemented on the Site include:

  • Semantic HTML structure (proper heading hierarchy, lists, tables with headers, ARIA labels where appropriate).
  • Keyboard-navigable interface; all interactive elements reachable via Tab and operable via Enter/Space.
  • Visible focus indicators on interactive elements.
  • Color contrast meeting WCAG AA ratios for normal and large text.
  • Alternative text on informative images (where the image is decorative, alt=”” is used).
  • Resizable text without loss of content or functionality.
  • Forms (where present) with associated labels and clear error messaging.
  • Skip-to-content link for screen reader and keyboard users.
  • No content that flashes or strobes at thresholds known to cause photosensitive seizures.
  • Language attribute set on the html element so assistive tech selects the correct voice.

3. Known limitations

We document known accessibility limitations honestly:

  • Third-party advertising. Display advertising is rendered by external networks (Google AdSense; Mediavine and Adsterra in future or alternative configurations). Ad creative is produced by advertisers and we do not control its accessibility. Some ads may have inadequate alt text or low contrast. We work with the network’s accessibility tooling where available; specifically, AdSense provides controls that limit certain ad types but does not give publishers direct accessibility-review of every creative.
  • Older articles. Articles published before our accessibility audit may have minor issues (missing alt text, inadequate heading hierarchy). We are auditing and fixing these progressively.
  • Embedded user content. Where we embed reader-submitted screenshots or community-shared imagery, accessibility depends on the original source.
  • Live data tools. Some interactive tools (the IV calculator, the CP-at-level lookup) are tested for keyboard and screen-reader access, but complex interactions may have edge cases we have not surfaced.
  • Pokémon-themed visual content. Some Pokémon visual content (sprites, type icons) carries meaning that is harder to convey textually. Where we use it, we provide text equivalents alongside.

4. Browser and assistive technology compatibility

The Site has been tested with:

  • Recent versions of Chrome, Firefox, Safari, and Edge on desktop.
  • Mobile Safari on iOS and Chrome on Android.
  • VoiceOver (macOS, iOS), NVDA (Windows), and TalkBack (Android).
  • Browser zoom up to 200% without loss of content.

If you use a different combination and encounter problems, please report them.

5. Alternative formats

If a specific article or feature is not accessible to you, we are happy to provide an alternative format. Possibilities include:

  • A plain-text version of the article, sent by email.
  • A read-aloud audio version (where the article is short enough to make this practical).
  • A simplified summary.

Email info [at] pogodex [punto] space with the subject line Accessibility request and the URL of the relevant article. We respond within 5 business days.

6. Reporting accessibility problems

If you encounter an accessibility barrier on Pogodex, please tell us. The fastest channel is email to info [at] pogodex [punto] space with subject Accessibility issue and:

  • The URL where you encountered the issue.
  • A description of the barrier (what you were trying to do, what failed).
  • Your assistive technology setup (screen reader name and version, browser).
  • Your contact information if you would like a follow-up.

We treat accessibility reports as substantive; the fix prioritization scales with the severity of the barrier and the breadth of users affected.

7. Accessibility roadmap

Our short-term accessibility commitments:

  • Completing the alt-text audit on legacy articles by end of 2026.
  • Adding skip-link patterns where the current structure has gaps.
  • Improving focus visibility on interactive tool components.
  • Adding text equivalents for Pokémon visual content where it is not yet present.

Longer-term commitments depend on resourcing but include moving to WCAG 2.2 AA when the standard is sufficiently implemented in tooling.

8. Disability rights and complaints

If you believe Pogodex has discriminated on the basis of disability and you wish to escalate, the relevant authority depends on your jurisdiction. Italian readers can contact the Agenzia per l’Italia Digitale (AgID). UK readers can contact the Equality and Human Rights Commission. EU readers can contact their national authority. U.S. readers may have rights under the Americans with Disabilities Act and Section 508. We will work cooperatively with any legitimate authority on substantive accessibility complaints.

Related pages: Contact Us · About Us · Editorial Standards · Privacy Policy · Terms of Service