A professional web developer, designer, and accessibility advocate for 23+ years under many different technologies starting with HTML/CSS, Perl, and PHP, Todd has been an avid learner of web technologies for over 40 years starting with many flavors of BASIC all the way to React/Vue.
Currently, an Accessibility Engineer at WebstaurantStore, Todd is also a member of the W3C Silver, ACT, and AGWG groups, as well as many subgroups doing work on WCAG 3.0. When not coding, you’ll usually find Todd tweeting about lobster rolls and accessibility.
Deceptive patterns (also widely known as “dark patterns”) are all over the Web. I’ll speak to the accessibility impact deceptive patterns and “dark” patterns have accessibility-wise, inclusively, moving away from using “dark” patterns as vernacular, and my introduction to taking these patterns and my work in the W3C to have these published in WCAG3.
There is a lot of work being done in the Functional Needs group of the W3C to introduce these to FAST. I’ll talk about FAST, what it means to accessibility, and to users, developers, designers, and everyone in-between in the organization.
I’ll also introduce people to the Framework for Accessible Specification of Technologies (FAST) which advises creators of technical specifications on ensuring their technology meets the needs of users with disabilities.
It primarily addresses web content technologies but also relates to any technology that affects web content sent to users, including client-side APIs, transmission protocols, and interchange formats.
Specifications that implement these guidelines make it possible for content authors and user agents to render the content in an accessible manner to people with a wide range of abilities.
|Deceptive Patterns and FAST||Connect Tech||November 2022|
|Accessibility Overlays: Why You Should Avoid Them||Connect Tech||November 2022|
|Making A Strong Case For Accessibility||MagnoliaJS Conference||September 2022|
|Making A Strong Case For Accessibility||Code PaLOUsa ‘22||August 2022|
|The Four Principles of the A“POUR”calypse: The harbingers of accessibility||KCDC 2022||August 2022|
|Making the Pragmatic Business Case for Accessibility||KCDC 2022||August 2022|
|Making A Strong Case For Accessibility||Beer City Code 2022||August 2022|
|Making A Strong Case For Accessibility||Code on the Beach||July 2022|
|Making A Strong Case For Accessibility||DevNexus||April 2022|
|Headings & Accessibility||WebstaurantStore Internal||February 2022|
|To <button> or not to <Button>||WebstaurantStore Internal||February 2022|
|ARIA Attributes, Part One||WebstaurantStore Internal||January 2022|
|Forms & Labels: WCAG 2.5.3 - Label In Name||WebstaurantStore Internal||January 2022|
|Web Content Accessibility Guidelines and Color Contrast||WebstaurantStore Internal||December 2021|
|Making A Strong Case For Accessibility||Connect.tech 2021||November 2021|
|WCAG and Color Contrast||Web Directions: Access All Areas||October 2021|
|Making A Strong Case For Accessibility||#a11yTO Conf||October 2021|
|Start your A11y Journey: How to Become an Accessibility Advocate||HelloA11Y Global Accessibility Awareness Day 2021||May 2021|
|Start your A11y Journey: How to Become an Accessibility Advocate||Virtual Coffee February Lightning Talk||February 2021|
|Contrasting Accessibility with Color Contrast||BarCamp Philly 2020||December 2020|