วีดีโอ

Thank You

Great session, thanks for the walkthrough

Clearly explained. Thanks!

Thank youuu your breakdown just helped untangle all of the information overload in my brain.

Thanks! You helped me a lot with your Video 💪

Thanks Eric

I just subscribed, as learning more about accessibility and best practices is something I really want to incorporate through my whole front end dev career (pretty new to the tech scene) but I think its easier to build good habits than it is to overwright bad ones. Great video :)

Skip to 5:30 for the start (watching replay)

Great videos about accessibly.

Really cool talk! To add to your points about the authoring experience, I remember at my previous company developers would often complain about how buggy screen readers are. I'm sure in reality the issues are a mix of poor markup, browser bugs, and legitimate screen reader bugs. But regardless of the cause, it seems like a very frustrating experience to develop an accessible (non-trivial) web application if you don't have indepth knowledge of the field. Another thing that I find catches people off guard - rules in the accessibility specs (or not in the spec at all) that try to account for author errors. For example, people wondering why their <table> element is being exposed as a LayoutTable in the AX tree rather than being exposed a "real" table. Or people wondering why presentational semantics for their elements aren't respected. The latter is at least in the spec, but it's definitely buried.

The good news is that the CR candidate is now live

Hi! New subscriber here. Thanks for going over this. Helps a lot.

Good efforts

Good presentation if you have time please make more videos on how to find out defects

can you increase the sound a bit

please make video about interview questions on accessibility testing

The ARIA current element is so true, I wish we had this directly in HTML too. Really interesting talk Eric :)

Great content! Thank you very much!

Thank you Eric!

Thanks very much. your video is quite thorough and explicit. it gives enough details and examples to facilitate understanding.

make a video about web "Decorative Images" step by step, it will help us , thank you

thank you so much Eric!

I would like to point out that the lightning around 12:20 was unpredictable and therefore this video does not follow WCAG 😂

Thanks for all the content you put out Eric, it's been super helpful as I sink further into this topic.

Really great video, thank you so much.

Cortex t-shirt 😎

On our Jira board we have a custom field containing all the WCAG 2.1 success criteria, plus three additional entries: "None" (the default), "Triage" and "No SC". The latter is used in cases like this, or in cases where there is a significant UX problem for users with disabilities. However, to play devil's advocate, I would down-prioritise an issue like this, since it has zero impact on users, and even though the aria is misused, it does not fail any SC. One more point - when looking at an small issue like this it's easy enough to say "this is a trivial thing to fix", but in my experience, these kinds of issues are often created by misconfigured code generators, automated deployments and other scripts, rather than manual markup. It can sometimes be far from trivial to change a templating engine, or code generator, which has been tested and signed-off as working, even if the desired change is small. This is especially true when the org has political, infosec-related, technical or even legal constraints in place to reduce 'tweaking' of production code. These are not excuses, they are just the reality for larger scale deployments in certain sectors. We've had Language of Page issues that go unfixed for months because our content loads inside someone else's . It's trivial to add a language code to a static HTML page you made yourself. It's quite a different matter to run the gauntlet of corporate bureaucraciy *just to get permission* to tweak something that is built and maintained by another team, or (in some cases) another firm.

Great presentation! Always good to refresh my knowledge. Thanks for sharing! 👍

Very nice. I like the German accent.

Thank you for the wonderful video. You describe it very well and made it easy to understand

I'm watching this video 1.5 hour before my IAAP WAS Exam starts. Thank you for providing this quick, straight to the point video.

I could get some of it too! :)

I understood ALMOST the whole thing 🥰

Was happy to see a new episode, but then saw the title :(

Is web accessibility in demand in current market

Thanks Eric. I've been trying to get a handle on 'Time-based media' and what that it's exact definition is and you put it succinctly. Many thanks.

The lightning was a hilarious touch! Great content this was helpful, thank you!!

my goal is to learn more about accessibilty, for example about aria- attrihutes. and i'm planning to learn from that channel

Thanks Eric for the video... Really appreciate your effort.

Super Arbeit wie immer👍🏻

I am Pramit, the Founder of Louie Voice Control. As a Visually Impaired, I always felt the need for an app that will allow user to control favorite apps & phone with just voice commands. Thus Louie was born. See Louie in Action & please share your feedback. rb.gy/dfahp1 As I get more and more good feedback, it encourages my team and me work harder on enhancing the app. Help me create more awareness by spreading the word.

Thank you, captions! I HEARD YOU SAY IE! 🤣 I'd never thought I'd be wrestling with browser inconsistency again ... they don't all treat WebVTT formatting of captions the same. So, it doesn't behave the way you expect it to. Oy.

good introducgory video. you could add some examples, snippets of code or something to make video more interesting. waiting for video about 2.2!

2:01 Does Twitter fail 2.1.4? For example, pressing the N key opens the “New tweet” dialog.

Love this video, and I look forward to more. I'm curious-do you know/are you able to tell us why a developer thought it made sense to apply aria-level in the first place? When I see broken ARIA I can usually guess what the developer's thought process was behind it, but in this case I'm at a loss.

Another terrific video! You are getting some good comments over on the accessibility subreddit as well.

I'm not sure I follow the purpose of the video. I suppose if you want to nit-pick and see if the example exactly fails according to the specific wording of the success critieria, then one might say it's not a WCAG failure. The code fails the Nu Html Checker because of the invalid attribute, but as you said, an invalid attribute isn't in the list of four parsing errors. It probably should be (perhaps 4.1.1 should be updated to include that addition). But I don't know any accessibility expert that would *not* report this as a failure, and as @dennis said, it should be fixed. So back to my original comment, why is it important to have a video to show something people should never do and then justify that it's not a WCAG failure? That would seem to do the accessibility community a disservice.

A good WCAG analysis, but it doesn't matter if it passes or fails; the code is totally wrong and should be fixed.

Awesome explanation Eric. Thank you so much.

Great presentation. I appreciate how you broke down the guidelines in a very easy to understand way.