I want it to work with a keyboard and a screen reader.
Accessibility in Web Components →JOURNEY TO WEB COMPONENTS / TRACK 03
Production Web Component Architecture
A component is not finished when the demo works. It is finished when the application can depend on its contract.
THE STARTING CONTRACT
Bring one component that already works
This track assumes you can define a custom element, attach a shadow root, use a slot, and dispatch an event. We will take that component into the parts of an application where shortcuts become bugs.
Review the first component track →ENTER THROUGH THE FAILURE
I want to ... then read
I want to use my components in React or another framework.
Advanced Patterns & Integration with Frameworks →I want to make a component pleasant to use: properties, attributes, events and names.
Real-World Examples & Patterns in Web Components →I want to know what is safe to use today.
The Future of Web Components →which carries a dated status tablePrepare the component for production
01 / Join the platform
Accessibility in Web ComponentsBuild custom elements that say what they are, work from the keyboard, and announce changes to screen reader users.02 / Ship the component
Advanced Patterns & Integration with FrameworksPass objects from React to a custom element without getting [object Object], and handle events across the framework boundary.03 / Prove it in the application
Real-World Examples & Patterns in Web ComponentsSee who publishes web components (Google, Microsoft, Adobe and others) and four patterns that make them easy to use, with runnable examples.- The Future of Web ComponentsWhich Web Component features you can use today, which work in only some browsers, and which are still proposals, with a dated status table.