Skip to main content
WireKit
Copy for LLM

Rating

The <x-wirekit::rating> component displays an interactive rating control. It uses role="radiogroup" with individual radio buttons for each icon, providing full keyboard and screen reader support. The default icon is a star, but you can choose from several built-in shapes.

Basic Usage

Default 5-Star Rating

Preselected Value

3 Out of 5

Custom Max

10-Star Scale

Size Variants

Three Sizes

Readonly

Display Only
Average rating

In readonly mode the rating is a record of a score, not a control that happens to be switched off — so it renders as a picture: role="img" with one accessible name ("4 out of 5 stars"), nothing focusable inside it, and no form field.

That last part matters more than it sounds. A display-only rating used to emit a hidden input with a generated name, so a page showing 24 product ratings shipped 24 stray form fields that a surrounding <form> would submit.

Pass aria-label when "4 out of 5 stars" does not say enough on its own — with several ratings on a page, none of them says what scored 4:

<x-wirekit::rating :value="4.2" readonly aria-label="Average customer rating" />

An interactive rating is unchanged: it is a real radiogroup, because picking a score is choosing one of five.

Fractional Stars

Readonly mode supports fractional values for displaying average ratings:

Fractional Ratings
3.78 average
4.5 stars
2.2 stars

Fractional values only work in readonly mode. Interactive ratings always snap to whole icons.

Icon Shapes

The icon prop lets you swap stars for other shapes. All shapes support interactive mode, readonly mode, fractional fill, and all size variants.

Available icon shapes

Fractional Icons

Custom icons also support fractional fill in readonly mode:

Fractional hearts
Love score

Custom Colors

The filled icon color uses the --color-wk-warning token because amber/yellow is the universal standard color for star ratings (Amazon, Google, IMDb, etc.). The token's name refers to its semantic role in the design system (warning notifications), but the amber hue happens to be the perfect match for rating icons.

You can recolor ratings per instance by overriding --color-wk-warning with any value — including other WireKit tokens:

Custom rating colors
Default (amber)
Red hearts
Blue stars
Green circles

You can also reference other design tokens instead of hardcoded hex values:

{{-- Use the accent color (indigo by default) --}}
<x-wirekit::rating name="r" :value="4" style="--color-wk-warning: var(--color-wk-accent);" />

{{-- Use the success color (green) --}}
<x-wirekit::rating name="r" icon="circle" :value="3" style="--color-wk-warning: var(--color-wk-success);" />

{{-- Use the danger color (red) for hearts --}}
<x-wirekit::rating name="r" icon="heart" :value="5" style="--color-wk-warning: var(--color-wk-danger);" />

This way your ratings stay consistent with your theme — when you change your accent or success color, the ratings update automatically.

To change the color globally, override --color-wk-warning in your theme. For per-scope customization, use the scope prop with personalization:

// config/wirekit.php — personalize a specific scope
'personalizations' => [
    'rating' => [
        'love-meter' => [
            'base' => '[--color-wk-warning:#e11d48]',
        ],
    ],
],
<x-wirekit::rating scope="love-meter" icon="heart" name="love" :value="4" />

Width & Layout

The rating component auto-sizes to its number of icons and the size prop. It does not stretch to fill its container — it has a natural inline width based on max × icon size.

Form Submission

A hidden <input type="hidden"> submits the numeric rating value under the given name.

Livewire Integration

<x-wirekit::rating> keeps its current rating in internal state seeded from the value prop, so when binding with Livewire pass the bound property as :value alongside wire:model to seed the initial rating:

<x-wirekit::rating wire:model.live="score" :value="$score" />

Without :value the control shows 0 stars until the user picks a rating; wire:model keeps it in sync afterward. This is the framework-agnostic seeding pattern WireKit's stateful controls share — it works in plain Blade forms too.

Optimistic UI

Pass the name of the Livewire method the rating should call and the new score appears immediately, then confirms or undoes itself when the server answers:

<x-wirekit::rating
    name="score"
    label="Score"
    :value="$score"
    optimistic="rate"
/>

Load wirekit-optimistic.js alongside whichever bundle you already use — below it, in your layout:

@wirekitScripts
<script src="{{ asset('vendor/wirekit/wirekit-optimistic.js') }}"></script>

Try it

The demo below runs the real path: the change shows immediately, the outline says it is provisional, and the server's answer either confirms it silently or takes it back.

Optimistic rating — accepted, refused, and a slow answer

The <livewire:demos.…> wrapper above exists only on this site — it supplies the demo methods so the page can show a real round trip. The block under it is what you write.

The prop takes a method name rather than true because the component cannot know the action otherwise: server actions reach a WireKit component through the attribute bag, so it never sees your wire:click. optimistic replaces wire:model.live here rather than joining it — the method you name is what changes the score on the server; pass the current one with :value so the rating knows where it started.

What a screen reader hears Picking a score announces once, hedged — "Saving" — so the new value is audible as provisional. Confirmation is silent: what was announced is what happened. Only a deviation speaks a second time, which is what makes an undo recognizable as an undo.

Where the rating sits in a form that already shows a validation message, the undo stays silent and leaves that message to speak: it tells you what to do, "could not save" does not.

An aborted request announces nothing at all — nothing was refused.

Focus stays exactly where you put it. An undo arrives on the server's schedule, and moving focus then would take you out of your place for a reason you could not predict.

A second pick while one is in flight is refused rather than queued. Queued, the final score would depend on which answer arrived last — network timing, which is both wrong and impossible to test.

The hidden form field follows both the optimistic write and the undo, so a plain HTML form never submits a score that was taken back.

Readonly ratings ignore the prop. A readonly rating is a picture of a score with nothing to operate, so there is no action to anticipate.

Scope. This covers mutations: changing something and showing it right away. Sorting, filtering and pagination are query round trips — nobody can show a result nobody knows yet — and are deliberately not covered.

Props

Prop Type Default Description
optimistic string|null null Livewire method to call, showing the new score before the server confirms it. Ignored when readonly. See Optimistic UI.
optimisticArgs array [] Extra arguments appended to the optimistic action call, after the new value — the row this control belongs to.
label string|null null Accessible group label
error string|null null Validation message. Rendered below the control, announced politely, and wired with aria-invalid + aria-describedby
hint string|null null Helper text below the control. An error replaces it — one message region, so the two cannot stack
name string|null null Form field name
id string|null auto-generated Base element id
value int|float 0 Rating value. Supports fractional values (e.g. 3.78) in readonly mode
max int 5 Maximum number of icons
icon string 'star' Icon shape: star, heart, circle, square, diamond, thumb
size string 'md' 'sm', 'md', 'lg'
readonly bool false Display-only mode (a record of a score, not an interactive control)
scope string|null null Scoped personalization key

Accessibility

  • Outer container: role="radiogroup" with aria-label from the label prop
  • Each star: visually hidden <input type="radio"> with aria-label="N of M stars"
  • Selected state communicated via native radio checked attribute
  • Star SVGs are aria-hidden="true" — the radio input provides the accessible name
  • Hover preview shows which rating would be selected (visual-only, no AT announcement)
  • Readonly mode sets aria-readonly="true" on the radiogroup
  • Live region announces the selected value on change: "N of M stars"

Keyboard Interaction

Key Action
Tab Move focus into the rating group
ArrowRight / ArrowUp Select the next star (increase the rating)
ArrowLeft / ArrowDown Select the previous star (decrease the rating)
Home Select the first star (1)
End Select the last star (max)

The component uses roving tabindex — only the currently selected star (or the first star if none selected) is in the tab order.

Pitfalls

  • Don't use rating as a single-value display. Reach for stars with readonly if the value is read-only — but for narrative copy "Rated 4.2/5" is more screen-reader-friendly than a five-star widget.

Design Tokens

Token Purpose
--color-wk-warning Filled icon color (amber by default)
--color-wk-text-subtle Empty icon stroke color
--color-wk-ring Focus ring color
--ring-wk-width Focus ring width
--radius-wk-sm Focus ring border radius
--transition-wk-duration Hover/selection transition
--font-wk-sans Font family for labels

Customization

Override defaults in config/wirekit.php:

'components' => [
    'rating' => ['max' => 5, 'size' => 'md'],
],

Further Reading

Was this page helpful?

Thanks — that helps.

Voting requires cookies or local storage. What we store