E-mail List Archives
Re: Does providing null ("") for Role, Name, id break Accessibility in any way ?
From: jp Jamous
Date: Jul 29, 2023 1:44PM
- Next message: Birkir R. Gunnarsson: "Re: Does providing null ("") for Role, Name, id break Accessibility in any way ?"
- Previous message: allyssa jessicon: "Does providing null ("") for Role, Name, id break Accessibility in any way ?"
- Next message in Thread: Birkir R. Gunnarsson: "Re: Does providing null ("") for Role, Name, id break Accessibility in any way ?"
- Previous message in Thread: allyssa jessicon: "Does providing null ("") for Role, Name, id break Accessibility in any way ?"
- View all messages in this Thread
While everything is working good, I would fail this if I was testing a page. Also, automated tools would fail it.
The ID may not be the biggest concern, but the Role would be. It would fail Role, Name Value.
I prefer to have values for all of those by default, then the script can change them when the JS execute. Nothing wrong with this approach. However, leaving them empty is bad markup and would fail 1.4.2.
- Next message: Birkir R. Gunnarsson: "Re: Does providing null ("") for Role, Name, id break Accessibility in any way ?"
- Previous message: allyssa jessicon: "Does providing null ("") for Role, Name, id break Accessibility in any way ?"
- Next message in Thread: Birkir R. Gunnarsson: "Re: Does providing null ("") for Role, Name, id break Accessibility in any way ?"
- Previous message in Thread: allyssa jessicon: "Does providing null ("") for Role, Name, id break Accessibility in any way ?"
- View all messages in this Thread