What?

Fixes an issue where validation triggered on blur moves focus to the first invalid field, breaking the natural tab sequence in the DataForm card layout.

Closes #76832

Why?

reportValidity() automatically focuses the invalid input element. When validation runs on blur, this behavior hijacks the user's natural tab navigation and moves focus to the first invalid field instead of the next field in the tab order.

How?

Call reportValidity() only when the invalid input remains the active element by checking:

inputElement.ownerDocument.activeElement === inputElement

This ensures the validation UI is still shown while preventing focus from being stolen during tab navigation.

Testing Instructions

1. Run Storybook locally:
   npm run storybook:dev

2. Open the DataForm validation story:
   DataViews → DataForm → Validation

3. Set the layout to card-collapsible.

4. Clear the Text field so it becomes invalid.

5. Click inside Textarea.

6. Press TAB.

Expected result:
Focus follows the natural tab order (Text → Textarea → Select / Password) instead of jumping back to the first invalid field.

Testing Instructions for Keyboard

1. Navigate through the form using only the TAB key.
2. Ensure that focus moves sequentially through fields even when validation errors exist.
3. Verify that validation messages still appear without interrupting keyboard navigation.