Accessibility

The Promptless stack targets WCAG 2.2 Level A and AA, which also covers WCAG 2.1 A and AA. This page covers what the platform does for you and what depends on the content you or your client add.

Important

The conformance statement covers the platform, not any one website. A large part of WCAG is about content: whether alt text describes the image, whether a video has captions, whether link text says where it goes. Each delivered site needs its own review.

What the platform does automatically

Area	What happens without any setup
Alt text	Images get alt text generated from content you already wrote. A card image uses the card heading, a step image the step heading, a team photo the member’s name and role, a testimonial avatar the author’s name.
Repeated link text	Ten cards that all say “Learn More” do not produce ten identical links. Each link is announced with its card title, for example “Learn More: Timber Frame Weekend”, while the button still shows “Learn More”.
Colour contrast	Text, link, icon and button colours are corrected against the section’s actual background when the page renders. This is the Smart Accessibility Colors setting in Global Settings.
Keyboard use	Every control works with the keyboard. A skip link is the first stop on each page and moves focus to the main content. Dialogs, popups and the gallery lightbox keep focus inside while open, close on Escape and return focus to the control that opened them.
Visible focus	Every keyboard stop shows a focus indicator. A sticky header does not hide the element that has focus.
Motion	Marquees and carousels respect the visitor’s reduced-motion setting, and carousels have previous and next controls. No media autoplays with sound; background videos are muted.
Structure	Pages use landmarks, one h1, and no skipped heading levels. Decorative icons are hidden from screen readers. A call-to-action renders as a link when it goes somewhere, a button when it opens a popup or lightbox, and plain text when it has no destination. Star ratings are read as one phrase, such as “Rating: 4.5 out of 5”.
Editor	The editor your staff use is keyboard operable, usable at 400% zoom, and has a non-drag alternative for every drag action.

The known gap: audio description

WCAG 1.2.5 (Audio Description, Level AA) is the one criterion the platform does not support. It applies to prerecorded video where the pictures carry information the soundtrack does not.

There is no audio description field. A description track was deliberately not added: no major browser speaks one, so it would look like support without reaching anyone.

You can still meet the requirement today:

1. Describe the video in the page. Put a text alternative next to the video. This meets the Level A criterion 1.2.3.
2. Use an audio-described version. Point the video field at a version of the file that already includes description.

Note

A second gap is narrower. The map section’s auto loading mode embeds Google Maps in a frame whose focus indicator the platform cannot draw. If that matters for your site, set the map to click to load: its placeholder is a button with a normal focus indicator.

What stays your responsibility

The platform makes these possible. It cannot make them true.

• Captions. Sections that accept a video have a Video Captions field for a WebVTT (.vtt) file. You provide the file. YouTube and Vimeo embeds use the captions set on those services.
• Alt text for logos. A logo has no heading nearby to borrow from. Without an alt or title, the alt falls back to the file name (“IMG 4471 logo”) or “Partner logo 3”. Fill in the field.
• Images of text. Words inside an uploaded picture are not available to a screen reader.
• Meaningful headings and link text. Heading levels are enforced; whether headings describe their content, and whether link text says where it goes, is up to the writer.
• Form fields. Every field is labelled, but the wording is yours, and so is setting the autocomplete property on fields that collect personal details. It is not applied automatically.
• Documents you link to. The inside of an uploaded PDF or Office file is outside the platform.
• Language changes inside a page. There is no way to mark a passage as another language.
• Anything outside the stack. WordPress admin screens, WooCommerce checkout, and other plugins on the same site need their own review.

Tip

The AI connector’s wordpress_validate_site tool and the editor’s SEO panel report weak alt text, raw URLs as link text and heading problems, page by page. Use them before handing a site over.

The full conformance report

The criterion-by-criterion Accessibility Conformance Report, in the VPAT format procurement teams ask for, is in the plugin repository at docs/accessibility/ACCESSIBILITY_CONFORMANCE_REPORT.md. It gives every WCAG 2.2 A and AA criterion a status and the evidence behind it. When a client asks for a compliance statement, send it together with a review of the delivered site.

Related pages

• FAQ — Short answers to the questions people ask most about Promptless WP, with a link to the page that covers each in full.
• System Requirements — The WordPress and PHP versions Promptless WP needs, what the AI features and connector need in addition, and which themes and plugins it works alongside.