ARIA 1.2 Specification

Back to Overview Show Timestamps

00:00 --> 00:08

directly what's going on. So for the specification, we have a couple of different sections. It's a

00:08 --> 00:16

very, very complicated specification. I will not even click on the link because I think it's like

00:16 --> 00:22

a little bit too much. And we will talk about all the aspects, but I will like basically pick out

00:22 --> 00:29

smaller things that are interesting for you and that you can use. And the current

00:29 --> 00:38

version is ARIA 1.1 but everyone says like yeah there was a bit of a miss of of how it worked out

00:38 --> 00:47

so please look at ARIA 1.2 which is a W3C candidate recommendation draft since December 2021

00:47 --> 00:59

so about a year and a bit and it might get to a recommendation in april 2023 so

00:59 --> 01:04

that might happen let's cross our fingers and hope for the best

01:04 --> 01:12

but yeah so everything i talk about is already aria 1.2 because aria 1.1 had some

01:12 --> 01:20

things in it that just didn't work as well and they have been corrected now and all of the

01:20 --> 01:26

browsers and assistive technology they all look at aria 1.2 so you know it doesn't make any sense

01:26 --> 01:33

look at aria 1.1 and that's good you know it's good that we have this correction

01:33 --> 01:45

now for aria from from an aria standpoint you always have three distinct pieces of information

01:45 --> 01:55

that you are that every interactive ui component needs um and that is what type it is is it a

01:55 --> 02:04

button? Is it a link? Is it a navigation? Is it a dialogue? Something like that. And the name of

02:04 --> 02:12

that information of that content. So if you have a button that closes, you know, the name of that

02:12 --> 02:21

button should be close. If you have a link that goes to the homepage of Chas, then it should be

02:21 --> 02:27

Chas homepage, the name of the link, stuff like that. So pretty straightforward, actually.

02:29 --> 02:36

Then there are different properties of content. And the properties are mainly there to point at

02:36 --> 02:46

different states and properties. And that means that you can say, for example, this button is in

02:46 --> 02:53

pressed state or this link is the current link. Those are examples we will talk about a little bit

02:53 --> 02:59

really soon. So yeah, so that's basically the properties can be and you can have multiple

02:59 --> 03:09

properties on one thing. So you could, for example, have, thinking of something that is good,

03:09 --> 03:27

a link that is a button that is pressed and also because the website is like getting more information, that button might also be busy.

03:27 --> 03:32

So it would say like button pressed busy, for example.