Feedzy RSS Feeds Accessibility, VPAT, and WCAG Compliance FAQ
This article answers common questions from institutional buyers, procurement teams, and accessibility reviewers evaluating Feedzy RSS Feeds for accessibility compliance.
Does Feedzy provide a formal accessibility statement or VPAT?
Feedzy RSS Feeds does not currently provide a formal accessibility statement, Voluntary Product Accessibility Template (VPAT), Section 508 conformance report, or third-party WCAG compliance certification.
The plugin is developed following standard WordPress development practices, but this does not constitute a formal accessibility certification or legal compliance declaration. If your organization requires an official VPAT or compliance document before purchase, one is not available at this time.
📝 Note: If you need to check whether an accessibility statement has become available since this article was last updated, contact the Feedzy support team before purchasing.
Is Feedzy certified as WCAG or Section 508 compliant?
Feedzy RSS Feeds has not undergone a formal third-party accessibility audit and is not certified as WCAG 2.x or Section 508 compliant. No audit report or compliance certification is available to share with procurement teams.
What does Feedzy control and what does your theme control?
The accessibility of your RSS feed display depends on more than the plugin itself. There are two layers to consider:
What Feedzy controls:
- The HTML markup generated by the Feedzy block, shortcode, or widget
- Link structure and feed item output
- Alt text handling for images sourced from feed data
What your theme and site configuration control:
- The overall page layout and heading hierarchy
- Font sizes, color contrast, and spacing
- Focus styles for keyboard navigation
- Page builder markup wrapping Feedzy output
- Custom Feedzy templates added to your theme (see How to move Feedzy templates to your theme)
- Custom CSS applied to feed output
- Content of the imported feed items (alt text, link text, and headings in source feed content)
Because of this shared responsibility, the final accessibility experience of a Feedzy-powered feed display depends heavily on your specific theme, template configuration, and site setup — not on Feedzy alone.
How can I evaluate Feedzy for accessibility before purchasing?
The most reliable way to evaluate Feedzy for accessibility is to test the exact implementation you plan to use. Here is a recommended approach:
- Set up a staging or local site using the same WordPress theme and page builder you plan to use in production.
- Install Feedzy RSS Feeds (the free version is available from WordPress.org) and configure a test feed using the same display method you intend to use — block, shortcode, widget, or Elementor widget.
- Run your organization's accessibility tests against the rendered feed output. Common checks include:
- Keyboard navigation and focus order
- Screen reader output (headings, link text, image alt text)
- Color contrast of feed item text and links
- Responsive behavior and zoom compatibility
- Output from lazy-loaded feed items (if using the lazy load feature)
- Use the same Feedzy template you plan to deploy, including any custom templates, since template choice affects the generated markup.
- Involve your accessibility reviewer or testing tool (for example, axe, NVDA, JAWS, VoiceOver) so results reflect your organization's specific requirements.
What pre-purchase options are available for validation?
If you need to evaluate Feedzy Pro features before committing:
- Free version testing: The free version of Feedzy RSS Feeds is available from WordPress.org and can be used to test core feed display functionality at no cost.
- 30-day money-back guarantee: Feedzy Pro includes a 30-day money-back guarantee, which gives you time to test Pro features — including specific templates, import configurations, and display methods — in your own environment before deciding.
⚠️ Important: The 30-day money-back guarantee is a purchase refund option, not a substitute for an institutional accessibility approval document. If your procurement process requires a formal VPAT before purchase, check with your procurement or accessibility team before proceeding.
What should I do if my organization requires a VPAT?
If your procurement process requires a VPAT or formal accessibility conformance report before approving a purchase, note that one is not currently available for Feedzy RSS Feeds. You should:
- Consult your procurement or accessibility team to determine whether the plugin can be evaluated using hands-on testing instead of a formal document.
- Contact Feedzy support to ask whether the status has changed: themeisle.com/contact/.
- Use the free version for testing to generate your own informal accessibility assessment before your team makes a purchase decision.