A better HTML input experience (custom elements and the AOM) (2017)
The article highlights accessibility challenges with custom web elements, advocating for the HowTo: Components project and the Accessibility Object Model (AOM) to improve semantic meaning and support for assistive technologies.
Read original article
The article discusses the challenges and future of accessibility in custom web elements, emphasizing the importance of semantic meaning for assistive technologies like screen readers. Unlike built-in elements, custom elements lack implicit semantics and keyboard support, making it difficult for developers to ensure accessibility. The author highlights a project called HowTo: Components, which aims to educate developers on best practices for creating accessible custom elements, inspired by the ARIA Authoring Practices Guide. The article also addresses the styling limitations of built-in elements, which often lead developers to create custom controls that may not be accessible. The author advocates for the Accessibility Object Model (AOM) proposal, which would allow custom elements to define their semantics directly in the accessibility tree, simplifying the process of ensuring accessibility. The article concludes with a call to action for developers to contribute to the HowTo: Components project and to explore the potential of AOM in improving accessibility standards for custom elements.
- Custom elements lack implicit semantics and keyboard support, posing accessibility challenges.
- The HowTo: Components project aims to educate developers on creating accessible custom elements.
- The Accessibility Object Model (AOM) proposal could simplify defining semantics for custom elements.
- Developers often create custom controls due to styling limitations of built-in elements.
- The article encourages collaboration to improve accessibility standards in web development.
Related
A simple guide to HTML <head> elements
The article is a detailed guide on essential HTML elements for web documents, covering meta, link, title, and their impact on document perception. It includes social media markup, browser configurations, and author information.
Show HN: Plain Vanilla – a tutorial website for vanilla web development
The article discusses web development using only HTML, CSS, and JavaScript, emphasizing Web Components and modern CSS. It encourages experienced developers to explore this simpler, standards-based approach for building applications.
The UX of HTML (2023)
Vasilis van Gemert emphasizes the importance of user experience in HTML, advocating for teaching interactive elements first to engage learners and improve accessibility, shifting focus from semantics to practical UX applications.
People with Disabilities Use the Web
The Web Accessibility Initiative (WAI) by W3C promotes web accessibility for individuals with disabilities, providing resources, user stories, and tools to encourage inclusive design aligned with international standards.
How Chrome Accessibility Works
The document details Chrome's accessibility features, emphasizing platform-specific APIs, the automatic provision of accessibility in standard UI toolkits, and challenges with custom controls and multi-process browser adaptations.
5 commentsIt's now all done with properties on ElementInternals:
https://developer.mozilla.org/en-US/docs/Web/API/ElementInte...
They also decided not to ship AccessibleNode's which is unfortunate because it removed the clearest path for canvas+wasm based UIs.
showing native elements is fine and safer. and browser should just plug the backdoors they found over the years to style them, since they are all technically click jacking attacks.
and all FEv will hate this comment because they don't even know what's a click jacking attack.
Related
A simple guide to HTML <head> elements
The article is a detailed guide on essential HTML elements for web documents, covering meta, link, title, and their impact on document perception. It includes social media markup, browser configurations, and author information.
Show HN: Plain Vanilla – a tutorial website for vanilla web development
The article discusses web development using only HTML, CSS, and JavaScript, emphasizing Web Components and modern CSS. It encourages experienced developers to explore this simpler, standards-based approach for building applications.
The UX of HTML (2023)
Vasilis van Gemert emphasizes the importance of user experience in HTML, advocating for teaching interactive elements first to engage learners and improve accessibility, shifting focus from semantics to practical UX applications.
People with Disabilities Use the Web
The Web Accessibility Initiative (WAI) by W3C promotes web accessibility for individuals with disabilities, providing resources, user stories, and tools to encourage inclusive design aligned with international standards.
How Chrome Accessibility Works
The document details Chrome's accessibility features, emphasizing platform-specific APIs, the automatic provision of accessibility in standard UI toolkits, and challenges with custom controls and multi-process browser adaptations.