Impact: 60 · Confidence: 95 · Complexity: 85
Description
Problem:
Institutional and enterprise buyers, particularly universities and government agencies, require an accessibility statement or Voluntary Product Accessibility Template (VPAT) to verify WCAG compliance before they can purchase software. Without this documentation, Feedzy is blocked from being approved for use in these institutions.
Desired Behavior:
Provide an official accessibility statement and/or VPAT for Feedzy that outlines its current level of WCAG compliance. This should cover the front-end output generated by the plugin (blocks, shortcodes) as well as the backend user interface if applicable.
Acceptance Criteria:
- Conduct an accessibility audit of Feedzy's front-end and back-end components against WCAG standards.
- Create and publish an official accessibility statement or VPAT document.
- Add a documentation article or landing page section linking to the accessibility details.
Customer Context
A pre-sales customer from an educational institution (alaska.edu) is trying to purchase Feedzy but needs an accessibility statement, VPAT, or WCAG compliance details to get through their internal approval process.
Root Cause Analysis
The root cause is a gap in compliance documentation. Educational institutions and government entities have strict procurement policies requiring software products to prove accessibility compliance (typically via a VPAT or WCAG compliance statement) to ensure equal access for all users. Currently, Feedzy lacks this official documentation, effectively blocking sales to institutions with these requirements.
Reasoning
The customer is from an educational institution and requires a Voluntary Product Accessibility Template (VPAT), accessibility statement, or details on WCAG compliance for Feedzy to pass their procurement approval process. Currently, we do not have this documentation for Feedzy (it was not found in our docs or GitHub issues). Providing a VPAT and establishing an accessibility statement is a common requirement for enterprise, government, and educational sales, making this an actionable compliance/documentation feature request that requires an accessibility audit.
Source: HelpScout #3326644833
Generated by feature-request-triage workflow (ID: feature-request-triage_6a0bb6276366d5.86576525)
Impact: 60 · Confidence: 95 · Complexity: 85
Description
Problem:
Institutional and enterprise buyers, particularly universities and government agencies, require an accessibility statement or Voluntary Product Accessibility Template (VPAT) to verify WCAG compliance before they can purchase software. Without this documentation, Feedzy is blocked from being approved for use in these institutions.
Desired Behavior:
Provide an official accessibility statement and/or VPAT for Feedzy that outlines its current level of WCAG compliance. This should cover the front-end output generated by the plugin (blocks, shortcodes) as well as the backend user interface if applicable.
Acceptance Criteria:
Customer Context
A pre-sales customer from an educational institution (alaska.edu) is trying to purchase Feedzy but needs an accessibility statement, VPAT, or WCAG compliance details to get through their internal approval process.
Root Cause Analysis
The root cause is a gap in compliance documentation. Educational institutions and government entities have strict procurement policies requiring software products to prove accessibility compliance (typically via a VPAT or WCAG compliance statement) to ensure equal access for all users. Currently, Feedzy lacks this official documentation, effectively blocking sales to institutions with these requirements.
Reasoning
The customer is from an educational institution and requires a Voluntary Product Accessibility Template (VPAT), accessibility statement, or details on WCAG compliance for Feedzy to pass their procurement approval process. Currently, we do not have this documentation for Feedzy (it was not found in our docs or GitHub issues). Providing a VPAT and establishing an accessibility statement is a common requirement for enterprise, government, and educational sales, making this an actionable compliance/documentation feature request that requires an accessibility audit.
Source: HelpScout #3326644833
Generated by feature-request-triage workflow (ID: feature-request-triage_6a0bb6276366d5.86576525)