This publication targets WCAG 2.2 AA as the conformance standard for every public-facing page. Accessibility is treated as part of the editorial commitment, not as a compliance overlay — a publication that argues for transparency in financial infrastructure should hold itself to the same standard on the surfaces that carry the argument.

What that means in practice

Every page is structured around semantic landmarks (header, main, footer, nav, article, section) so a screen reader can navigate the site by region without listening to the visual chrome. The first focusable element on every public page is a "Skip to main content" link — visually offscreen by default, slides into view when a keyboard user presses Tab, lets them jump past the masthead directly to the article body. Body text and brand accents are routed through design tokens that meet the AA contrast threshold in both light and dark themes; the theme toggle in the masthead is the reader's lever for whichever variant reads more comfortably. Keyboard navigation reaches every interactive element on the public surface — the masthead, the dropdown, the subscribe form, the markets controls, the screener filters, the audio player, the sign-in flow. Images carry alt text; decorative imagery is marked as such so it stays out of the screen-reader stream. Animations on the homepage, methodology page, and Ask Nodo agent honor the operating-system prefers-reduced-motion setting and stop autoplaying when it is on. Interactive market charts — the screener bar chart, the universe scatter, the sector benchmark, and the historical line chart — carry per-chart ARIA descriptions that summarize what the chart shows, the data range covered, and where the canonical per-company data lives.

Audio briefings ship with synchronized per-word transcripts on every editorial format that carries audio — the weekly Pulse, the monthly Research, and the short-form briefings attached to each Insight. The transcript is produced in the same API round-trip as the audio itself, so a reader can follow along visually or jump to a specific paragraph the moment the audio is published. Whitepapers, distributed as long-format PDFs, do not currently carry an accompanying audio briefing; that gap is named explicitly below. Every video produced — currently the weekly Pulse, with the same commitment extending to any future video format — ships with open captions burned into the frame, derived from the same alignment data that powers the audio transcripts. The text is always visible regardless of platform, player, or whether the viewer has captions enabled in their settings. Form fields are labeled, error states use ARIA-live regions so a screen reader hears the result of a submit rather than discovering it on a second pass, and modals manage focus return so the keyboard doesn't get lost when a dialog closes.

What we do not pretend is solved

The honest section. These are known gaps, named here so a reader who depends on assistive technology knows what to expect before they encounter it.

• Interactive market chart depth. Per-chart ARIA descriptions summarize what each chart shows and point at the canonical data, but the chart SVGs themselves do not expose specific bar values or dot coordinates to a screen reader the way an equivalent HTML data table would. The full sortable per-company data is reachable on the screener and ticker pages; the chart is editorial framing, the table is canonical. A "view as table" toggle on each chart is on the near-term improvement list to close the remaining depth gap.
• Whitepapers. Whitepapers ship as long-format PDFs without an accompanying audio briefing. Pulse, Monthly Research, and original Insights each have an audio briefing produced as part of the editorial pipeline; whitepapers do not. The PDF itself is not re-tagged for accessibility either — figure alt text, reading order, and document structure depend on the document's typesetter. Readers who rely on screen readers or audio access have the thinnest path through whitepaper content; the accompanying article surface on the site covers material points but is not a substitute for the full PDF.
• No published BSL or ASL translation of the audio briefings is available at this time.

How to report an issue

If a surface on The Payments Corner is unusable, harder to use than it should be, or fails the WCAG 2.2 AA standard in a way not named above, write to contact@thepaymentscorner.com with "Accessibility issue" in the subject line. Include the page URL, the browser and assistive technology you are using (screen reader name and version, voice control software, etc.), and a short description of what failed. Substantive issues receive a response within two business days; a fix follows on a timeline appropriate to the surface affected, with the most disruptive defects prioritized.

Standards and review

This statement is written against WCAG 2.2 AA as the target conformance level. The instrument is reviewed continuously rather than on a fixed schedule; the "Last updated" date at the top of the page reflects the most recent material revision. When a gap named above is closed, this page is amended in the same change.

Accessibility is a posture, not a finish line. The honest section above is not an apology — it is the part of the page that earns the rest of it. We name what we have not yet solved, and we ship the next improvement.