With web components you can create reusable and framework agnostic HTML elements based on web standards. But this means that accessibility becomes a topic, for example when you create your own form elements. The web is famous for it's various A11Y related features and possibilities for developers to create user friendly and accessible applications. However, with Web components, there are some limitations and specialties you have to keep in mind. The new spec "Accessibility Object Model" describes ways to provide A11Y features for web components but this spec is not yet available in all browsers so you still have to do some tricks. In this talk I want to speak about our A11Y related experiences with the development of a web component library. I want to highlight some restrictions of web components and some ideas of how to workaround them. And I also want to give a short overview of how the upcoming Accessibility Object Model spec will solve these issues.