Thank you for creating this video, it's very helpful!
@kiri.anderson
7 ай бұрын
Great tutorial - thank you!
@Rohit_yadav27
Жыл бұрын
excellent description thanks
@jamesdaniels6134
2 жыл бұрын
Excellent tutorial. Thanks for putting this together.
@WebAccessibility
2 жыл бұрын
You're very welcome!
@PianoPlayerist
Жыл бұрын
First, thank you very much for this helpful tutorial, I’d appreciate it if you would announce what you are typing as I am a person with vision impairment myself and I’m trying to learn with accessibility so a lot of time you type in on your keyboard and you’re not seeing what codes are you using and I understand that this is a web site accessibility for beginners so thank you
@WebAccessibility
Жыл бұрын
I am sorry about that, I will be more mindful to announce code in the future.
@luv789able
3 жыл бұрын
Awesome tutorial. Keep posting more!
@WebAccessibility
3 жыл бұрын
More to come!
@yadav_sonu_kumartriloki4495
2 жыл бұрын
You're doing a great job.
@WebAccessibility
2 жыл бұрын
Thank you!
@GameArts1
4 жыл бұрын
Nice tutorial!
@goroh83
3 жыл бұрын
First of all, thanks for all your content. It's sad that accessibility doesn't get more attention. I find your videos very helpful, since WCAG documentation can often be overwhelming... My two cents regarding required attribute: I read somewhere(Mozilla Developers Network I think it was) that it's still good to add aria-required="true" even if you arleady have required. THe reason was older browsers that may not recognize 'required' attribute. And a quick quesiton: If I want to include optional for each optional field would the following make sense: First name(optional): Would a screen reader announce aria-required="false" as 'not required' Thanks again for all your content. Keep up the good work!
@WebAccessibility
3 жыл бұрын
Hi Peter, Thank you very much for the encouragement, indeed, there is very little information on web accessibility, which makes developing accessible websites even more difficult. About aria-required - most modern screen readers recognize the `required` attribute, the issue is that some of them would announce "required" twice on inputs, if you use both `aria-required` and `required`. Imagine having to fill in a very long form and having "required" repeated twice on each field. As for older browsers, if they are unfamiliar with the attribute, they probably aren't able to parse HTML5 correctly anyways, so the web experience will be quite bad for them, regardless which attribute you use. Additionally, if you use both attributes, you'd have to control `aria-required` which is more work with minimal returns. However, if you don't want to use HTML5 form validation, which the `required` attribute embeds, then it is strongly recommended you use `aria-required`. As for the second question, I'd just make the "(optional)" text readable for screen readers, i.e. remove the "aria-hidden". So far, NVDA and Windows Narrator doesn't announce "not required" for `aria-required=false`, so I wouldn't rely on it (I don't think any screen reader does, but I haven't tested) For optional inputs, I usually just omit the `required` attribute and add an "optional" text like you did above it works just fine.
Пікірлер: 14