Hosted checkout: accessible names and color contrast fail automated accessibility audit

[VictorCuerdo]

Summary

The Polar-hosted checkout currently exposes three serious axe-core accessibility violations in Polar-owned markup:

• button-name: an interactive control has no accessible name.
• color-contrast: secondary checkout text does not meet the required contrast ratio.
• link-name: an anchor has no accessible name.

Reproduction

1. Open a live Polar hosted checkout containing monthly and yearly subscription products.
2. Test at desktop (1280 px) and mobile (390 px) widths in current stable Chrome.
3. Run axe-core 4.12 against the top-level checkout document after the email/cardholder form and secure payment iframe have mounted.

The same three rules fail at both widths. The checkout remains functionally usable; this report is about semantics and contrast in the hosted UI.

Why this belongs upstream

The affected document, styles, and controls are served by buy.polar.sh. Integrators can link to the hosted checkout but cannot change its DOM, accessible names, or color tokens.

Expected result

Every interactive control and link has a programmatic accessible name, and foreground/background color pairs meet WCAG AA contrast. Automated axe runs should have no critical or serious violations in the hosted checkout document.

[SecuredByIshani]

Hi, I'd be interested in working on this issue if it's still available. I've reviewed the issue description and would be happy to investigate the accessibility violations and work on fixing them. Could I please be assigned to this issue? Thanks!

[prath47]

@pieterbeulque are you guys accepting PRs from contributors ??
I would like to make some contributions.