Accessibility

It is really important to make web components fully accessible. Sometimes is might be tricky.

When architecting web components, be sure to include these considerations so everyone can use your components.

As the Web Components are a relatively new standard, there are still some gaps in regard to accessibility.

About the most common mistake when making accessible components, id, and label associations.

Short answer: yes, but there's a couple of known issues around forms, labelling, and focus behavior.

A look at getting native dialogs to play nicely with shadow DOM.

Encapsulation makes children of a shadow root private to any siblings or ancestors of the shadow host.

Managing focus in the DOM has never been particularly easy, and shadow DOM just makes things that much trickier.

If you want to use shadow DOM without breaking accessibility, then this is one of the things you will have to grapple with.

Building accessible web components on the example of an input element pattern with a label and help text.

Proposal that aims to provide JavaScript API to allow developers to modify the accessibility tree for an HTML page.

When you define a new tag, the browser really has no way of knowing if you’re trying to build a button, or a slider.

Building proper UI Web Components can be quite a task, especially if you want them to be accessible.

The AOM will make accessibility a first class citizen of the extensible web – exactly what it should be.

Live stream recording with engineers and product owners from Adobe, IBM, SAP, Vaadin, and ING.

Web components render as HTML, and either that HTML works or it doesn’t.