Fieldset
A fieldset that groups related controls under a legend, with one disabled toggle that natively cascades to every control inside.
Preview
Controls
Device view renders in an isolated frame so real responsive breakpoints apply. Switch to Full for overflowing popovers.
Installation
php artisan ui:add fieldset
Registry contract
Install confidence
php artisan ui:add fieldset
writes only the generated targets below. The CLI validates each file hash before writing and
prompts before replacing local changes unless --force is used.
- Version
- 1.0.0
- License
- open
- Stability
- stable
- Contract
- v2
- Foundation
- ≥ 1.0.0
| Type | Generated target |
|---|---|
| blade | resources/views/components/ui/fieldset/fieldset.blade.php |
Registry dependencies
None.
Package dependencies
composer: jml/brok:^1.0
Guidance
Form structure and labelingCollect and organize related user input.
Use when
- Use to collect, group, and clearly label related input so users understand what is being asked and can recover from errors. Do not create dense unlabeled forms; start from one thing per page or one conceptual question per step when the task is unfamiliar or high stakes.
Avoid when
- Avoid using fieldset as a default simply because it is available in the library. Choose it only when its interaction cost, visibility, and behavior match the job to be done.
- Task length
- medium
- Interaction cost
- medium
- Interruptiveness
- none
- Input precision
- constrained
- Mobile / touch risk
- medium
- Accessibility risk
- high
- Needs background context
- No
- Comparison needed
- No
Preferred alternatives
- Focused question pages
- A smaller set of directly labeled fields
Anti-patterns
- Dense unlabeled forms
- Collecting information without a task need
API
manifest knowledge + registry-derived coverageProps
| Prop | Type / values | Default | Description |
|---|---|---|---|
| disabled | false|true | false | Documented catalog control used by the preview workbench. |
| legend | mixed|null | null | Declared by @props in the registry Blade source. |
Slots
default— Primary Blade slot rendered by the component.x-ui.fieldset.fieldset— Installed subcomponent from the registry item.
Data slots
fieldset
fieldset-legend
Capabilities
Behavior
- Uses server-rendered Blade and semantic HTML.
- Declares registry capability flags: a11y, responsive, rtl, darkMode, localized.
Usage
<x-ui.fieldset legend="Notifications" class="mx-auto w-full max-w-md">
<x-ui.field name="notify_email" label="Email">
<x-ui.input name="notify_email" type="email" placeholder="you@example.com" />
</x-ui.field>
<label class="flex items-center gap-2 text-sm text-foreground">
<x-ui.checkbox name="weekly_digest" />
{{ __('Send me the weekly digest') }}
</label>
</x-ui.fieldset>
Accessibility & localization
data-slot
Keyboard focus-visible
Localized labels
- Accessibility target: wcag-2.2-aa-target.
- Uses semantic HTML and a stable
data-slotattribute for styling/scripting hooks. - Focus-visible rings use the
ringtoken so keyboard focus is always visible. - Disabled and invalid states are conveyed to assistive tech, not by color alone.
- Targets WCAG 2.2 AA; verify contrast in light, dark, admin and customer surfaces above.
- Labels go through
__()and the component uses logical properties (ms-*,text-start,start-*) so it mirrors correctly — flip the preview to RTL to confirm.
Source
The exact, editable file ui:add writes
into your app — copy it or own the whole thing. Previews
render this same code; there are no preview-only components.
Changelog
Current version: v1.0.0. See the site changelog for the full release history.