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.
The web is accessible by default, and in this talk, I cover the four principles of accessibility. We’ll start with a little history lesson on how POUR began and then we will take a walk through the four principles of accessibility, or “POUR”. Perceivable, Operable, Understandable, and Robust.
These four principles in WCAG 2.2 will be covered and explained to users of all levels. All recommendations that are made for accessibility best practices are based on the four principles of accessibility.
We will also cover some common areas where failures of accessibility lie and how decisions affect accessibility with some real-world examples of how the four principles of accessibility weren’t achieved and examples of how they can be achieved.
|Deceptive Patterns and FAST||IM Tech Meetup||June 2023|
|Deceptive Patterns and FAST||Devnexus 2023||April 2023|
|Deceptive Patterns and FAST||Orlando Code Camp||March 2023|
|Deceptive Patterns and FAST||HalfStack Phoenix||February 2023|
|Deceptive Patterns and FAST||CodeMash 2023||January 2023|
|Deceptive Patterns and FAST||Modern Frontends Live!||November 2022|
|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|