Accessibility, Performance and Privacy

The answers a procurement process usually asks for, in one place, with links to the detail.

Accessibility

The stack has an Accessibility Conformance Report (the VPAT format) for WCAG 2.2 Level A and AA, criterion by criterion, with the automated check behind each claim. The one substantive gap is 1.2.5 Audio Description: video sections accept captions but have no audio-description track.

What the platform does for you:

• Text colours are computed against their background when the page renders, so the contrast of a section’s text follows the design settings.
• Images get alt text generated from the nearest heading when none is typed, and the gallery uses the alt text you type.
• Repeated link text such as “Learn more” is made distinct for screen readers.
• Popups, the gallery lightbox, carousels and accordions follow the WAI-ARIA patterns for keyboard use and focus.
• The editor’s audit and whole-site validation flag missing alt text, heading gaps and unclear link text.

What stays yours: whether alt text describes the image, whether headings form a sensible outline, whether link text says where it goes, and captions for your videos. A delivered site needs its own report; the platform’s report covers the markup, not your content. See Accessibility.

Page speed

Pages are checked against Google’s “good” Core Web Vitals thresholds on a mobile profile: Largest Contentful Paint 2.5 s, Cumulative Layout Shift 0.1, Total Blocking Time 200 ms, First Contentful Paint 1.8 s. Each section loads only its own stylesheet, and scripts for maps, lightboxes and popups load only on pages that use them.

What stays yours: image sizes and hosting.

Privacy

• Maps on record pages load Google Maps only when the visitor clicks (a site can choose to load them straight away). Map sections in Promptless WP can be set to click-to-load.
• Forms store each entry, with the submitter’s IP address, in the site’s own database. Nothing is sent to a Promptless service. Webhooks and FlowMint steps send data only where you configure them to.
• The AI connectors run on your computer and talk to your site with an application password you can revoke at any time.

Multilingual and right-to-left

Promptless pages work with WPML, Polylang and TranslatePress: a translation starts as a copy of the original page’s sections. Every front-end stylesheet has a right-to-left version that WordPress loads for right-to-left languages. See Multilingual Sites and Right-to-Left Languages.

Related pages

• Vendor Dependence and Ownership — What keeps working if the Promptless WP licence lapses or a Promptless plugin is removed, which parts are proprietary, and who owns the content.
• Accessibility — What Promptless WP does for WCAG 2.2 A/AA on its own, the one known gap, and what stays your responsibility on each site you deliver.
• Multilingual Sites — How Promptless pages work with WPML, Polylang and TranslatePress, what a translation copies, and what stays the translation plugin's job.
• Right-to-Left Languages — How Promptless pages mirror automatically on Arabic, Hebrew, Persian and Urdu sites, what mirrors, and what you still check in your content.