How to fix aria progressbar name on BigCommerce

Steps for BigCommerce

1. In your BigCommerce admin go to Storefront → My Themes → your active theme → Edit Theme Files (or download via Stencil CLI).
2. Search template files (`.html` Handlebars partials under `templates/`) and JavaScript files (`assets/js/`) for `role="progressbar"` or `<progress`.
3. Edit the relevant template or JS file to add `aria-label="…"` or `aria-labelledby` to the element. Stencil Handlebars partials support standard HTML attributes — just add them inline.
4. If the progress bar is injected by a third-party script (e.g., a page-builder widget), add a JavaScript snippet via Storefront → Script Manager that targets the element and sets the attribute after page load.
5. Push the changes via Stencil CLI (`stencil push`) or save in the theme editor, then verify using browser DevTools Accessibility tab.

<!-- OPTION A: aria-label (no visible label nearby) -->
<div
  role="progressbar"
  aria-label="Password strength"
  aria-valuenow="60"
  aria-valuemin="0"
  aria-valuemax="100"
  style="width:60%;"
></div>

<!-- OPTION B: aria-labelledby (visible label exists) -->
<p id="upload-label">File upload progress</p>
<div
  role="progressbar"
  aria-labelledby="upload-label"
  aria-valuenow="40"
  aria-valuemin="0"
  aria-valuemax="100"
  style="width:40%;"
></div>

<!-- OPTION C: native <progress> with <label> -->
<label for="checkout-progress">Checkout: step 2 of 4</label>
<progress id="checkout-progress" value="50" max="100">50%</progress>

What is aria progressbar name?

A progress bar (any HTML element with `role="progressbar"`, including native `<progress>` elements) must have an accessible name — a short label that tells users *what* is progressing. This name is provided via an `aria-label` attribute directly on the element, or by pointing to a visible label using `aria-labelledby`. When neither exists, the progress bar is completely anonymous: assistive technologies announce it as just "progress bar, 0%" with no context about what is being tracked — a password strength meter, a checkout step, a file upload, etc.

Screen reader users — including customers who are blind or have low vision — rely on accessible names to understand your store's interface. An unnamed progress bar during checkout, a file upload, or a product review form creates confusion and can cause those shoppers to abandon the task entirely, costing you sales and harming your brand reputation. Failing to provide accessible names for interactive or informative widgets violates WCAG 2.1 Success Criterion 1.1.1 (Non-text Content) and 4.1.2 (Name, Role, Value), exposing your store to accessibility complaints and potential legal liability in many jurisdictions (e.g., ADA in the US, EN 301 549 in the EU). Fixing it is a quick code change with zero impact on visual design.

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