Accessibility

Where mykoradar.com stands against WCAG 2.2 AA, how we checked, what still falls short, and how to tell us about a barrier.

Last updated: 16 August 2026

Conformance status

MykoRadar aims to meet WCAG 2.2 at Level AA. As of 16 August 2026 this site is partially conformant: it meets the standard in most respects, with the exceptions listed below.

MykoRadar is a private project. This statement is published voluntarily and WCAG is used as our own yardstick rather than as a legal obligation.

How we tested

The review was carried out on 16 August 2026 by self-assessment, against the running site rather than the source alone. It covered:

  • Contrast— every text node measured automatically, with the text colour composited against the element’s effective background and compared to the 4.5:1 threshold for body text and 3:1 for large text. The focus indicator was measured against the 3:1 threshold for non-text contrast.
  • Keyboard operation — tab order, presence and visibility of the focus indicator, and the ability to bypass repeated navigation.
  • Structure — one first-level heading per page, heading order without skipped levels, landmark regions, and the document language attribute.
  • Controls and images — accessible names for links and buttons, form field labels, and alternative text.

Representative page types were checked: the section index, a section hub and an article. This is a self-assessment, not an external audit or certification.

What this review changed

  • Secondary text contrast. Three palette shades used only for text measured 1.74:1, 2.44:1 and 3.67:1 against their background. Across nearly seven hundred usages this was the widest accessibility problem on the site. They were darkened to the 3:1 and 4.5:1 thresholds while keeping their hue.
  • Focus indicator. The outline on links and buttons measured 1.68:1 against the background — effectively invisible. It now uses a dedicated colour giving at least 3.86:1 on light backgrounds and on the dark footer alike, at 2px.
  • Bypass blocks.A “Skip to content” link is now the first element on every page. Before this, a keyboard user had to traverse the whole header on every page.
  • Section covers. The department label and standfirst over a coloured panel measured between 2.95:1 and 3.93:1 depending on the section colour. Both are now full white.
  • Photo credits. The licence attribution overlaid on a photograph depended for its contrast on how bright the picture happened to be. It now carries its own translucent backing, giving at least 8.5:1 whatever the image.

Known limitations

  • Latin names. Scientific names inside English prose are not marked with a language attribute, so a screen reader will pronounce them with English phonetics.
  • Image descriptions. Photographs come largely from Wikimedia Commons; some come from other credited repositories or publications. Their alternative text is derived from the subject rather than describing the particular frame, so they convey less to a blind reader than hand-written descriptions would.
  • Long articles. Entries in the culture and travel sections run past eight hundred words without in-page navigation, which makes them slower to scan with a screen reader than a shorter piece would be.

The interactive observation map, the weather charts and the reporting form are on mykoradar.pl and are covered by the Polish statement. They are not part of this site.

Accessibility features

  • A “Skip to content” link as the first element of every page.
  • Full keyboard operation with a visible focus indicator.
  • Content readable with JavaScript disabled.
  • Layout holds at text zoom and down to a 320-pixel viewport.
  • Animation is suppressed when the operating system requests reduced motion (prefers-reduced-motion).
  • No autoplaying audio or video, and nothing flashing more than three times a second.

Reporting a barrier

If something here cannot be operated by keyboard, sits at too low a contrast, or reads badly with a screen reader, write to admin@mykoradar.pl. It helps to include the page address, what went wrong, and what you were using — browser, screen reader, zoom level.

We normally reply within a few working days. There is no formal appeals procedure, because we are not a public body: accessibility reports are handled the same way as factual corrections, described on the Contact page.

Date of this statement

Prepared on 16 August 2026 on the basis of a self-assessment carried out the same day. It will be reviewed at the next substantial interface change, and at least once a year.