[fields] Fix the error message when a custom field with an <input /> but the field expects the accessible DOM structure (#17237)

Signed-off-by: Flavien DELANGLE <[email protected]>
Co-authored-by: Michel Engelen <[email protected]>

Author: flaviendelangle

packages/x-date-pickers/src/internals/hooks/useField/useFieldV7TextField.ts

@@ -206,9 +206,9 @@ export const useFieldV7TextField = <
           'MUI X: The `sectionListRef` prop has not been initialized by `PickersSectionList`',
           'You probably tried to pass a component to the `textField` slot that contains an `<input />` element instead of a `PickersSectionList`.',
           '',
-          'If you want to keep using an `<input />` HTML element for the editing, please remove the `enableAccessibleFieldDOMStructure` prop from your Picker or Field component:',
+          'If you want to keep using an `<input />` HTML element for the editing, please add the `enableAccessibleFieldDOMStructure={false}` prop to your Picker or Field component:',
           '',
-          '<DatePicker slots={{ textField: MyCustomTextField }} />',
+          '<DatePicker enableAccessibleFieldDOMStructure={false} slots={{ textField: MyCustomTextField }} />',
           '',
           'Learn more about the field accessible DOM structure on the MUI documentation: https://mui.com/x/react-date-pickers/fields/#fields-to-edit-a-single-element',
         ].join('\n'),