Which WCAG criterion this fails
- Does not meet 4.1.2 Name, Role, Value (Level A)
How to fix it on WooCommerce
Everything below is done from Appearance > Theme File Editor, or your child theme over SFTP. Take a copy of the theme before editing.
- Give the input a value attribute — that string is both the visible text and the accessible name: value="Subscribe".
- If the button must show only an icon, switch it to a <button> element with the icon inside and an aria-label, which is easier to style than an <input>.
- Never leave value="" and paint the label on with CSS content — assistive technology does not read generated content reliably.
Where this usually lives
searchform.php, and older form plugin markup
Paths given for Storefront, Astra, Flatsome and other WooCommerce themes. A heavily customised theme may differ; the CSS selector in your scan report points at the exact element.
Code
<!-- Before -->
<input type="submit" value="">
<!-- After -->
<input type="submit" value="Subscribe">
<!-- Or, for an icon-only submit -->
<button type="submit" aria-label="Search">
<svg aria-hidden="true" focusable="false">…</svg>
</button>How to confirm it is fixed
Re-run the scan. This rule should drop out of the findings entirely. If the instance count falls but does not reach zero, the same defect exists in another template — product cards and quick-view modals are the usual second home for it.
Effort: low. Rule id: input-button-name (axe-core).