Over the last two years I’ve been dabbling with various aspects related to the handling of touch events and pointer events – specifically trying to determine which events are being dispatched by browsers as a result of touchscreen interactions, and what the repercussions of this are considering the increasing number of multi-input devices (such as laptops that feature both traditional keyboard/mouse/trackpad as well as a touchscreen, or nominally touch-only devices such as smartphones and tablets, but paired with a bluetooth mouse/keyboard).
At TPG we are committed to advancing accessibility, and we look for ways to drive innovation and change in the way accessibility is approached and implemented. Laws and policies are strong drivers for accessibility, and in this article we talk about U.S. legislation that addresses accessibility in communication and media products and services. We believe these rules will advance accessibility thinking worldwide, and will result in innovative products and services that are designed to provide an accessible and enjoyable user experience for everyone.
By Sarah Horton and David Sloan
Note: This is the manuscript version of the paper we presented at the 7th Cambridge Workshop on Universal Access and Assistive Technology (CWUAAT ’14). The paper appears in the book Inclusive Designing: Joining Usability, Accessibility, and Inclusion, Copyright © 2014 Springer.
Attention to accessibility usually comes into play in the later phases of product development. Accessibility audits are typically performed during quality assurance and user acceptance testing phases. Remediation for any issues identified in the audit usually happens in code. However, the best fix for many complex accessibility issues may be to revisit the overall design approach; yet reworking designs at this late phase has a significant impact on timelines and processes. Any recommendation involving alternative designs is therefore usually unwelcome. Instead, the issues remain unresolved, or are resolved in a fashion that achieves technical accessibility but offers a compromised user experience.
The best approach to accessible user experience is to integrate accessibility into the design and development process. When accessibility is part of the practice of every member of the product development team, and when accessible features and functionality are built into design, content, and code, the result is a product that is accessible and enjoyable for everyone.
Been reading a few new articles on Web Components and accessibility, which lead me to re-read an old post I wrote: Notes on Web Components + ARIA. I noted the demo was broken, presumably as the web component syntax had changed since 2012. So I decided to make a few new tests:
Continue Reading Some stuff that doesn’t work between the DOM and Shadow DOM