WP SWIPER
WP Swiper translation compatibility with REEID Translate
WP Swiper translation compatibility is documented for 1 visitor-facing content surface from available integration evidence. Manual REEID verification is still pending.
AWAITING VERIFICATION
Documented translation surfaces for WP Swiper.
The listed visitor-facing values are supported by the current integration evidence. REEID manual compatibility verification is still pending.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
DOCUMENTED SURFACES
1 visitor-facing content surface are identified in the current integration evidence.
VERIFICATION STATE
Evidence-backed content scope is documented separately from REEID manual compatibility verification.
EVIDENCE-BACKED SCOPE
How documented WP Swiper content is evaluated
01 · Review documented surfaces
Start with the visitor-facing values explicitly identified in the integration evidence.
02 · Preserve plugin behaviour
Keep WP Swiper structure, configuration, validation, logic and runtime behaviour under plugin control.
03 · Validate multilingual output
Check each documented content surface in the actual integration before treating the workflow as manually verified.
04 · Record verified scope
Promote evidence-backed surfaces to verified compatibility only after REEID testing confirms the integration behaviour.
SUPPORTED CONTENT
Translation scope
image alt text
Image alt text is included in REEID translation scope for this integration.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Adds a Gutenberg slider/carousel block that wraps Swiper.js content.
- Allows each slide to contain nested WordPress blocks (e.g., images, headings, paragraphs, buttons, video, and layout blocks).
- Supports responsive slider/carousel behavior with breakpoint controls.
- Provides slider navigation and clickable pagination.
- Supports accessibility behavior for non-visible slides (removed from accessibility tree and keyboard tab order since version 1.4.6).
- Loads frontend assets only when a WP Swiper block is detected, with an option to load them globally via Settings > WP Swiper.
Dynamic content
Dynamic or runtime content behavior remains limited to what is explicitly documented in the official plugin evidence.
SEO and metadata
SEO and metadata behavior is documented only where it is explicitly established by official plugin information.
URLs and navigation
URL and navigation behavior remains outside translation scope unless explicitly represented by the integration category.
Forms and commerce
Forms and commerce behavior is limited to factual capabilities documented for this plugin.
CONTENT BOUNDARY
Documented content scope and verified compatibility are separate states.
The listed visitor-facing values are supported by available evidence, while WP Swiper remains responsible for plugin-specific structure, configuration and functionality.
Manual REEID verification is still pending for this integration.
LIMITATIONS & QA
Verification notes
- Translation scope is limited to the documented visitor-facing content: image alt text.
COMMON QUESTIONS
WP Swiper and REEID Translate FAQ.
Which WP Swiper content is documented for translation?
The Supported Content section lists the visitor-facing values currently established by the integration evidence.
Has REEID manually verified WP Swiper compatibility?
Not yet. The current page documents evidence-backed content scope while manual REEID verification remains pending.
What happens before WP Swiper becomes verified?
REEID validates the documented visitor-facing values in the actual integration and confirms that plugin-controlled behaviour remains intact.
RELATED GUIDES
Continue through the compatibility library.
WORDPRESS PAGE BUILDERS
Review the documented WP Swiper multilingual content surfaces.
The current integration record identifies evidence-backed visitor-facing content while REEID manual verification remains pending.
Use the Supported Content section as the documented scope until verification is completed.