How to design an accessible form

A presentation at Munich Accessibility Meetup in October 2018 in Munich, Germany by Núria Peña

Slide 1

Slide 1

How to design an accessible Form MUNICH ACCESSIBILITY MEETUP @nuriapenya #a11yMUC

Slide 2

Slide 2

I NEED A. Sign Up Form. Way of communication and exchange between users and service. The user provides input which can be processed to generate a new output. Examples: create account, join newsletter, complete transaction, sign up for event

Slide 3

Slide 3

Slide 4

Slide 4

Let’s reflect. Take some time to think about the form we just showed. What issues do you see? What could be done differently?

Slide 5

Slide 5

Slide 6

Slide 6

Everyone should be able to fill this form VISUAL MOTOR COGNITIVE HEARING

Slide 7

Slide 7

ACCESSIBILITY. How can design help?

Slide 8

Slide 8

Structure.

Slide 9

Slide 9

$ STRUCTURE Layout A form with parallel columns can easily lead users disorientation and distract them. Different users will misinterpret how to fill out multi-column forms in a variety of different ways.

Slide 10

Slide 10

$ STRUCTURE Layout Single-column forms are better than multi-column ones, as they don’t disrupt a users vertical momentum. Field length as a hint for the answer

Slide 11

Slide 11

$ STRUCTURE Keep it short Eliminating unnecessary fields reduces user cognitive effort and increases completion rates.

Slide 12

Slide 12

$ STRUCTURE Grouping If the form has a pretty complicated structure, it can be visually divided into semantic groups, with added space or headings between them.

Slide 13

Slide 13

Inputs.

Slide 14

Slide 14

$ INPUTS Labels & Placeholders Labels tell users what information belongs in a given form field and placeholders an example of the information required. Label Placeholder Email Email e.g. lukeskywalker@gmail.com Form field e.g. lukeskywalker@gmail.com The label increases the hit area of the field

Slide 15

Slide 15

$ INPUTS Placeholders Relying on placeholders alone, makes it difficult for people to remember what information belongs in a field, especially for users with visual and cognitive impairments. “Wait… what was I doing?”

Slide 16

Slide 16

$ INPUTS Placeholders Ideally, the label and hint are placed outside the form field and are always visible to the user.

Slide 17

Slide 17

$ INPUTS Focus By default, browsers put an outline around the element in focus so users, especially those who use a keyboard, know where they are. input:focus { outline: 2px solid #003D5E; }

Slide 18

Slide 18

Validation.

Slide 19

Slide 19

$ VALIDATION Error Message Every little bit helps! How a person with Deuteranopia would see it

Slide 20

Slide 20

Slide 21

Slide 21

ACCESSIBILITY. Development Insights.

Slide 22

Slide 22

ACCESSIBILITY. Testing.

Slide 23

Slide 23

In a nutshell…

Slide 24

Slide 24

Key Takeaways. • Clear Structure & Reduced Complexity • Appropriate Labelling • Don’t rely on Colour alone • Proper-sized Target Areas • Test, Test, Test

Slide 25

Slide 25

Thank You! Q&A

Slide 26

Slide 26

BRAINSTORMING. What do you want next? sli.do @A11yMunich /Munich-Accessibility-Meetup #a11yMUC

Slide 27

Slide 27

Poll of ideas 1 Open a browser on any laptop, tablet or smartphone 2 Go to slido.com 3 Enter the event code #A11Y