Virtual Happy Hour this month, Jun 28, we'll be getting a sneak preview at our soon to launch SaaS CMS!

Try our conversational search powered by Generative AI!

Make EPiServer Forms Input-fields more accessible by adding optional autofill/autocomplete support


We are currently doing major accessibility work on our customers sites and Forms is kind of bad in this aspect, since the name and id attributes can't have the values like name, given-name or cc-given-name etc.

The reason why Forms is bad in this aspect is obvious, the generic functionality etc.

There is solutions though, using the extended syntax of autocomplete-attribute.
We can override views and extend original elements, of course, but then it's harder to update Forms when you do updates.

My suggestion would be adding "native support" in Forms by adding editor support of optional selection of autocomplete/autofill values with a select/dropdown for all Form Elements that renders input-tags, a grouped select with the attribute values mentioned here:

More info here:

Then you could render:

<input autocomplete="name" name="__field_1285" id="92e4ac48-ec56-4b0a-a5eb-fa9fc94005af" type="text" class="FormTextbox__Input" placeholder="" value="" data-f-datainput="">

If the editor selected name in the grouped select box.

Edited, Apr 21, 2021 13:03

It's actually a very "simple" fix for you that would make it possible to put EPiServer Forms on drugs for customers, when using this on the fields where appropriate...

Apr 21, 2021 13:16

@Jonas, I have tried this on different input elements in Epi forms, but with a name format like name="__field_1285" it does not work for me. After just switching to name="name" for example it starts to work. Any idea if something changed or what I am missing? Thank you.

Here is an example of my full input code:

<input autocomplete="name" name="__field_100638" id="436fbd45-e12c-4f39-9c26-56023a3ac80c" type="text" class="FormTextbox__Input form-control" aria-describedby="__field_100638_desc" value="" data-f-datainput="" aria-invalid="false">

Mar 01, 2023 8:50

@alexandru.dumitru my suggestion is about Optimizely implementing support for the editors  to select a valid value for autocomplete, stating which type of data the input is, if it is a full name, first name, surname, email, etc., per input instance.

For it to really work in the browser you have to rely on other forms you have visited are stored in your browser, so it will autofill if it can identify that field type.

So, create multiple forms with the same value, and test if it is stored after a post, between different forms with inputs with the same autocomplete value.

Aug 08, 2023 15:27

Hi again!

At least in my tests, the suggestions seems correct.

Tested on iPhone yesterday.

You can also test the markup here:

Aug 09, 2023 7:03
* You are NOT allowed to include any hyperlinks in the post because your account hasn't associated to your company. User profile should be updated.