Accessibility at MagicFinders

Last reviewed September 19, 2026 · K Consulting LLC

We want everyone to be able to use MagicFinders, including people who use screen readers, keyboard-only navigation, magnification, or voice control. Our aim is to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at level AA across the website, our emails, and our text alerts, and to adopt WCAG 2.2 AA where practical.

How we test

We test with automated tools (axe-core) and by walking the site by keyboard and with VoiceOver, and we repeat that after changes. Payment happens on Stripe’s hosted checkout page, which Stripe builds to work with assistive technology. We do not use accessibility overlays or widgets; fixes go into the pages themselves.

Known limitations

As of the date above, these are the gaps we know about and are working through:

• In the alert builder, the live summary that describes your alert can be read out more often than it should while you type or click.
• On My alerts, each alert card is not yet a heading, so jumping between alerts by heading doesn’t work; use the filter chips or Tab instead.
• Some status changes on My alerts and the Account page (for example a filter or sort taking effect, or a button becoming busy) are not yet announced by screen readers.
• Links that open Disney’s booking page in a new tab don’t yet say so in their accessible name.

We will update this page as we fix them.

Tell us

If anything is hard to use, email hello@magicfinders.com and a person will reply within five business days. If you cannot set an alert on the site, email us the restaurant, hotel or event and the dates and we will set it up for you and confirm by email — no charge.