References

Beginner-friendly references for web development, with live, editable examples.

The HTML aria-valuemin attribute

ARIA Accessibility All modern browsers Updated
Quick answer

The aria-valuemin attribute defines the minimum allowed value of a range widget such as a slider or spinbutton. Use it with aria-valuenow and aria-valuemax.

Overview

The aria-valuemin attribute defines the minimum allowed value of a range widget.

It describes a range widget — a slider, progress bar or spin button (role="slider", "progressbar", "spinbutton"). Native <input type="range">, <progress> and <meter> elements expose their values automatically, so reach for these attributes only when building a custom widget.

Like all ARIA, aria-valuemin changes only the accessibility tree — what assistive technology perceives — never the element's behavior or appearance. The first rule of ARIA applies: if a native HTML element or attribute conveys this, use that instead, and only reach for ARIA when nothing native fits.

Syntax

<div role="slider" aria-valuemin="0" aria-valuemax="100" aria-valuenow="20"></div>

Values

Value
A number.

Example

Live example
<div role="spinbutton" aria-valuemin="1" aria-valuemax="12" aria-valuenow="6" tabindex="0"></div>

Best practices

  • Follow the first rule of ARIA — use a native HTML element or attribute that conveys this where one exists, rather than adding ARIA.
  • Prefer native <input type="range">, <progress> or <meter>, which expose their values for free.
  • On a custom range widget, set the min, max and current value together and keep the current value updated.
  • Add aria-valuetext when a bare number is not meaningful (e.g. "Medium" rather than "2").

Frequently asked questions

What does aria-valuemin do?
The minimum allowed value of a range widget.
Do I need these on a native range or progress element?
No. <input type="range">, <progress> and <meter> expose their values automatically. Use these for custom widgets only.
When should I use aria-valuetext?
When the numeric value is not self-explanatory — for example announcing "Large" instead of "3".
Do I need aria-valuemin if native HTML already conveys it?
Usually not. ARIA is for what native HTML cannot express; redundant or incorrect ARIA can make accessibility worse. Reach for it only when no native element fits.