Accessibility

Last updated: September 27, 2026

We want every writer, judge, and reader to be able to use Midas. We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA, and we treat accessibility problems as bugs.

What we do

• Pages are built to work with a keyboard alone, with visible focus and dialogs that keep and return focus.
• Pages are built to work with screen readers: headings, labels, and status messages are announced.
• The script reader supports keyboard page turning, larger text, a dark page, and a scrolling view.
• Motion respects your system’s reduced-motion setting.
• We run automated accessibility checks on key pages and flows, and test changes by hand with a keyboard.

Known limitations

• Screenplay PDFs. Scripts are uploaded by writers, and a PDF is only as accessible as the file it was exported from. Text-based PDFs work with most screen readers; scanned pages do not.
• Pages run by other companies. Card payment happens on Stripe’s page, PayPal payment in PayPal’s window, the human check on some forms is run by Cloudflare, and podcast episodes play through Apple. We choose providers that publish accessibility commitments, but we do not control those pages.

Tell us about a problem

If something on the site does not work for you, or you need information in another format, write to [email protected] or use Contact and put “Accessibility” in your message. Tell us the page and what went wrong. We will reply, and if a fix will take time, we will work with you on another way to enter, pay, or read in the meantime.