diff --git a/aspnetcore/blazor/forms-validation.md b/aspnetcore/blazor/forms-validation.md
index 53ff7167af13..2dcb6566bf48 100644
--- a/aspnetcore/blazor/forms-validation.md
+++ b/aspnetcore/blazor/forms-validation.md
@@ -31,7 +31,7 @@ public class ExampleModel
A form is defined using the component. The following form demonstrates typical elements, components, and Razor code:
```razor
-
+
@@ -64,18 +64,37 @@ In the preceding example:
A set of built-in input components are available to receive and validate user input. Inputs are validated when they're changed and when a form is submitted. Available input components are shown in the following table.
+::: moniker range=">= aspnetcore-5.0"
+
| Input component | Rendered as… |
| --------------- | ------------------- |
+| | `` |
+| | `` |
+| | `` |
+| [`InputRadio`](#radio-buttons) | `` |
+| [`InputRadioGroup`](#radio-buttons) | `` |
+| | `
+
+
+ Pick one color and one engine:
+
+
+ Imperial Red
+ Ion
+
+ Spacecruiser Green
+ Plasma
+ Starship Blue
+ Fusion
+
+ Voyager Orange
+ Warp
+
+
+
+```
+
+> [!NOTE]
+> If `Name` is omitted, `InputRadio` components are grouped by their most recent ancestor.
+
+::: moniker-end
+
+::: moniker range="< aspnetcore-5.0"
+
When working with radio buttons in a form, data binding is handled differently than other elements because radio buttons are evaluated as a group. The value of each radio button is fixed, but the value of the radio button group is the value of the selected radio button. The following example shows how to:
* Handle data binding for a radio button group.
@@ -766,7 +856,7 @@ The following uses the pre
Radio Button Group Test
-
+
@@ -799,6 +889,8 @@ The following uses the pre
}
```
+::: moniker-end
+
## Binding `` element options to C# object `null` values
There's no sensible way to represent a `` element option value as a C# object `null` value, because:
@@ -904,7 +996,7 @@ Blazor provides support for validating form input using data annotations with th
To validate the bound model's entire object graph, including collection- and complex-type properties, use the `ObjectGraphDataAnnotationsValidator` provided by the *experimental* [`Microsoft.AspNetCore.Components.DataAnnotations.Validation`](https://www.nuget.org/packages/Microsoft.AspNetCore.Components.DataAnnotations.Validation) package:
```razor
-
+
...
@@ -1005,7 +1097,7 @@ A side effect of the preceding approach is that a component visible when the submit button is selected (for example, in a `HandleValidSubmit` method).
```razor
-
+
diff --git a/aspnetcore/toc.yml b/aspnetcore/toc.yml
index e6c6b4402ba0..774ebb065bb9 100644
--- a/aspnetcore/toc.yml
+++ b/aspnetcore/toc.yml
@@ -336,6 +336,10 @@
href: blazor/forms-validation.md#built-in-forms-components
- name: InputNumber
href: blazor/forms-validation.md#built-in-forms-components
+ - name: InputRadio
+ href: blazor/forms-validation.md#built-in-forms-components
+ - name: InputRadioGroup
+ href: blazor/forms-validation.md#built-in-forms-components
- name: InputSelect
href: blazor/forms-validation.md#built-in-forms-components
- name: InputText