Felte's main package only cares about handling the reactivity of your form. In this sense, you should be the one taking into consideration the accessibility of it, like the correct use of labels, proper color contrast, focus management, etc.
That said, Felte does set
aria-invalid to the inputs it controls when they contain validation errors. Also, the
reporter packages do have some accessibility considerations built-in:
aria-liveattribute to the tooltip instance itself to announce when an error appears. Tippy itself also adds an
aria-describedbyattribute to your input. If there are errors on submit, it'll focus the first invalid element of your form.
aria-liveattribute to the added nodes containing your validation messages. It also focuses the first invalid input if therer are errors on submit.
@felte/reporter-cvapiwhile not recommended due to its non-friendly behaviour for mobile users, it is accessible by default since it uses the browser's built-in validation mechanism.
@felte/reporter-elementdoes not take any accessibility considerations since its only job is to allow you to give a template on how your validation messages should be presented. You should set an