How to fix aria input field name on WooCommerce

Steps for WooCommerce

1. Install and activate the free WP accessibility plugin (e.g. 'WP Accessibility' by Joe Dolson) to catch common label issues automatically.
2. For theme-level fixes, navigate in WordPress Admin to Appearance → Theme File Editor (or use a child theme) and locate the relevant template: woocommerce/templates/cart/cart.php (quantity inputs), woocommerce/templates/global/form-login.php, or your theme's search form (searchform.php).
3. To override WooCommerce templates safely, copy the file from /wp-content/plugins/woocommerce/templates/ into /wp-content/themes/your-child-theme/woocommerce/ preserving the folder structure, then edit that copy.
4. In the quantity input template (form-quantity-input.php or inside cart.php), find <input type="number" ...> and add: aria-label="<?php printf( esc_attr__( 'Quantity for %s', 'woocommerce' ), $product_name ); ?>"
5. For the site search bar, open searchform.php (or your theme's search widget template) and ensure the <input type="search"> has either a wrapping <label> or aria-label="Search".
6. Update and verify with the WAVE browser extension or axe DevTools.

What is aria input field name?

An "ARIA input field name" is the text label that screen readers and other assistive technologies announce when a user focuses on a form field — a text box, search bar, date picker, quantity field, or any other input that uses an ARIA role like `textbox`, `spinbutton`, `searchbox`, `slider`, or `combobox`. When that label is missing or empty, the field has no accessible name. WCAG Success Criterion 4.1.2 (Name, Role, Value) requires every user-interface component to have a name that programs can determine. A field without a label is essentially invisible to assistive technology users.

Screen reader users — including many customers with visual impairments — cannot understand what to type into an unlabeled field, which means they cannot complete your checkout, search for products, or fill in any other form on your site. This directly costs you sales and excludes a significant portion of your potential customers. Legally, WCAG 2.1 AA compliance (which includes SC 4.1.2) is referenced in accessibility laws and regulations in the US (ADA), EU (EAA), UK (PSBAR), and elsewhere — stores with unlabeled form fields are at real legal risk. Search engines also use accessible markup signals as part of overall quality assessment, so fixing this contributes to long-term SEO health.

See the complete Aria input field name guide for every platform and the full background.