SC 1.3.1 Info and Relationships

Back to Overview
00:00 --> 00:08
All right, let's go to our most favorite thing, which is WCAG stuff.

00:08 --> 00:11
So these are the WCAG success criteria.

00:11 --> 00:18
The first one is that relies to the form fields is info and relationships.

00:18 --> 00:24
So information structure and relationships conveyed through presentation can be programmatically

00:24 --> 00:27
determined or available in text.

00:27 --> 00:32
And that basically means that when you see a form field, you need to know how to fill it out.

00:32 --> 00:38
Like if it's all visible, what you need to do, you have to be able to fill it out.

00:38 --> 00:41
And it needs to be programmatically in the code.

00:42 --> 00:48
So this is for if you have a form field and then you have a button up and a button down next to it.

00:49 --> 00:57
visually you might infer this is the amount of things in this that you want to add to your card,

00:57 --> 01:02
for example. But you have to put that programmatically inside of the code and

01:02 --> 01:09
that's where you need the label, this where you need the technically the ARIA label, stuff like

01:09 --> 01:14
that. This is where this comes from. So that's super important to make sure that, yeah, if it's

01:14 --> 01:18
it's clear visually it also needs to be super clear in the code.