Accessibility statement for the development build. This is not a certification of WCAG conformance.
Planning your event
Start with the labeled prompt field, then edit the plan using the labeled controls. The four preview buttons select the invitation, schedule, story or pin. Review the text fields as well as the visual preview; images do not provide an accessible substitute for that text. Creation cost, validation errors and progress are announced in the interface.
Moving through the app
Use the skip link to reach the main content. Form fields have labels, keyboard focus is visible, and the mobile menu supports keyboard dismissal. Light, dark and system themes are available. Reduced-motion preferences disable decorative motion and smooth scrolling.
What we check
Automated browser checks cover planning, account controls, credit costs and downloads on desktop and mobile. They check contrast, horizontal overflow and common accessibility errors. Preview images and finished files need their own readability review.
Known limits
Manual screen-reader coverage, all browser and assistive-technology combinations, and exported image readability are not fully verified. Rendered graphics are images; add suitable alternative text in the destination where you publish them. Pinned worker fonts cover Latin, Arabic, Japanese kana and CJK characters, and a defined emoji repertoire. Uncovered glyphs fail explicitly. Font coverage does not certify every language, emoji sequence or layout.
Report a barrier
Include the page, browser, assistive technology if applicable, and the step that blocked you. Avoid sending private content. Support shows the current contact status and can copy local diagnostic details for your report.