Accessibility statement
The target is WCAG 2.2 level AA across the site. Today we are partially conformant — below is an honest account of what already works, what doesn't yet, and how to report a problem. This page is published voluntarily: Antoni Zieliński operates as a sole proprietor (a micro-enterprise under Directive (EU) 2019/882 / the Polish accessibility act) and is almost certainly exempt from the EAA's service-provider obligations — that's a factual statement, not a legal filing or legal advice.
1. Conformance status
Target standard: WCAG 2.2, level AA. Current status: partially conformant — most of the register → log in → pick a payment method → unlock a strategy path works with a keyboard and a screen reader, but not every part of the site has had a full manual pass with assistive technology (e.g. NVDA, VoiceOver).
2. What's already fixed
- Registration, login, and checkout form fields have properly associated
labels; success/error messages are announced live (
aria-live), and fields with an error are markedaria-invalid. - Visible keyboard focus on the Card/BLIK payment-method picker, and
stronger (at least 3:1) contrast on field and button borders; the home
page's market filter is real, accessible toggle buttons
(
aria-pressed), not tabs pretending to be tabs. - The animated 3D scene on the home page only redraws while something is actually moving or while it's in view, and a vertical swipe over it scrolls the page instead of spinning the scene.
- The cookie-consent banner is rendered by the server as part of the page itself — it doesn't wait for JavaScript to reveal it.
- The unlock ($2/€2/9 zł) purchase modal traps keyboard focus while open and returns focus to the button that opened it once closed.
- A "skip to content" link at the top of every page; Escape closes Pip's
tooltip and the welcome card; the welcome card's auto-dismiss timer pauses
while it has focus or the pointer over it; the ⌘K/Ctrl+K command palette
follows the accessible combobox pattern; decorative emoji inside link text
are hidden from screen readers; the rest of the page is made
inertwhile an overlay (modal/command palette) is open. - The track-record chart carries a text caption and a year-by-year data table alongside it as an alternative to the chart itself; small trend sparklines carry a text label for assistive technology.
- A site-wide "Turn off animations" toggle in the footer, independent of the operating system's reduced-motion setting.
3. Known limitations (as of today)
- TradingView charts (embedded only after cookie consent or an explicit click) are a third-party widget — we don't have full control over its accessibility; for exchanges TradingView won't embed, we show our own chart built from our own price data instead.
- The track-record chart and trend sparklines are drawn as interactive graphics (canvas/SVG) that aren't themselves fully screen-reader navigable; the text caption + data table next to them (above) is the accessible alternative, not the interactive chart itself.
- Pip's hover explanations for a metric (CAGR, Sharpe, Max Drawdown) work by keyboard and touch in most places, but on the strategy marketplace's card grid the stat labels sit inside the card's own link and are mouse-hover only today — deliberately, to avoid adding several extra Tab stops to every single card.
- We haven't yet run a full manual pass of every page with a screen reader (NVDA/VoiceOver) and at 200% zoom — the list above is our current, honest account, not a conformance certificate.
4. Contact and reporting a problem
If something on this site isn't accessible to you, or you want to report a specific problem: contact@hedgeyourown.com. We aim to respond within 14 days. Telling us the page, device, and assistive technology you're using helps us find the cause faster.
This is published market information, not investment advice and not a personal recommendation. Allocations are generated systematically and are the same for every subscriber. You decide and trade in your own account.