Accessibility Workshop

We run workshops, teaching business owners how to make a website accessible and reach compliance goals – before a court makes them.

Accessibility laws are changing. Similar to how some store locations must have a ramp or a certain door width, your website, or online store, must follow particular design steps to support assistive technology. Courts are regularly determining that anti-discrimination laws apply to online settings and there may not be undue barriers to using a website or app.

Accessibility Training Workshop

This developer-centric crash course starts at a high level, covering the importance of website accessibility and key conclusions from the explosion of web accessibility lawsuits. You will learn accessibility techniques and standards and how to sustainably integrate accessibility into your development workflows.

It’s not a lecture. It’s a day full of specially built activities designed to inform, challenge, and give you the skills needed to develop and manage an accessible website. We will demonstrate how to test with screen readers allowing you to experience how assistive technology works. We quickly go from learning what the standards are to understanding their purpose and knowing how to implement them.

Each person builds fundamental skills in accessibility that any tech professional delivering web applications must know. The workshop is interactive with live coding and hands-on exercises. This allows you to start applying what you learn right away, ask questions, and contribute your own unique perspective. The objective is that when you leave, you know how to consider accessibility in your development processes and gain confidence that you’re building inclusive applications.

We offer both half-day and full-day workshop options. Choose the one that works best for your organization.

Full-Day Workshop
Topic
Introduction
Accessibility: Who is it for and Why
Types of disabilities & How this affects their use of digital properties
Accessibility Laws and Philosophy
Section 508 and ADA
WCAG Success Criteria
What they are and what they mean for designers and developers
How to Test for Accessibility
Automated, manual, & screen reader testing
How to Code for Accessibility
Web and mobile app coding overview
Lunch
WCAG Perceivable Practices
  • 1.1.1 Images as images and links – there is a difference
  • 1.3.1 Info and Relationships
  • 1.3.2 Meaningful Sequence
  • 1.3.5 Identify Input Purpose
  • 1.4.1 Use of Color
  • 1.4.3 Contrast
  • 1.4.4 Resize Text
  • 1.4.5 Images of Text
  • 1.4.11 Non-text Contrast
  • 1.4.12 Text Spacing
Break
WCAG Operable Practices
  • 2.1.1 Keyboard
  • 2.1.2 No Keyboard Trap
  • 2.1.4 Character Key Shortcuts
  • 2.4.1 Bypass Blocks
  • 2.4.2 Page Titled
  • 2.4.3 Focus Order
  • 2.4.4 Link Purpose
  • 2.4.5 Multiple Ways
  • 2.4.6 Headings and Labels
  • 2.4.7 Focus Visible
  • 2.5.3 Label in Name
WCAG Understandable Practices
  • 3.1.1 Language of Page
  • 3.1.2 Language of Parts
  • 3.2.2 On Input
  • 3.2.3 Consistent Navigation
  • 3.2.4 Consistent Identification
  • 3.3.1 Error Identification
  • 3.3.2 Labels or Instructions
WCAG Robust Practices
  • 4.1.2 Name, Role, Value
  • 4.1.3 Status Message
ARIA
Overview and main considerations
Wrap-Up
Half-Day Workshop
Topic
Introduction
Accessibility: Who is it for and Why
Types of disabilities & How this affects their use of digital properties
Accessibility Laws and Philosophy
Section 508 and ADA
WCAG Guidelines
What they are and what they mean for designers and developers
How to Test for Accessibility
Automated, manual, & screen reader testing
WCAG Perceivable Practices
  • 1.1.1 Images as images and links – there is a difference
  • 1.3.1 Info and Relationships
  • 1.3.5 Identify Input Purpose
  • 1.4.1 Use of Color
  • 1.4.3 Contrast
  • 1.4.4 Resize Text
  • 1.4.5 Images of Text
Break
WCAG Operable Practices
  • 2.1.1 Keyboard
  • 2.1.2 No Keyboard Trap
  • 2.4.1 Bypass Blocks
  • 2.4.2 Page Titled
  • 2.4.3 Focus Order
  • 2.4.4 Link Purpose
  • 2.4.7 Focus Visible
  • 2.5.3 Label in Name
WCAG Understandable Practices
  • 3.1.1 Language of Page
  • 3.1.2 Language of Parts
  • 3.2.2 On Input
  • 3.3.1 Error Identification
  • 3.3.2 Labels or Instructions
WCAG Robust Practices
  • 4.1.2 Name, Role, Value
ARIA
Overview and main considerations
Wrap-Up

Both options will teach you how to make common UI features more inclusive and gain exposure to the mechanics of assistive technology, reducing regulatory risk and technical debt. More importantly, you learn how to think about accessibility and design with empathy. At the end of the day, everyone is ready to apply that empathy in-depth and the lessons extend beyond the development process into your everyday workflows.

Our attendees vary and range from a more non-technical audience such as developers or designers to business owners and content creators. We tailor the training to the crowd, which is ideally between 10 – 25 individuals. This number ensures everyone gets significant one-on-one time and that we have enough volunteers to keep the class at a high energy.

Some of the activities are stretch goals and may not be fully completed at the end of the day. It can be arranged to move the self-critique portion to a second day so that participants can receive more one-on-one time. Regardless, attendees (and their organizations) will receive all of the code, slides, and content from the day, which serves a starter for future frontend work. The training may be recorded.

We’re based in Los Angeles, but have a computer and will travel. The cost of our accessibility workshop ranges depending on the location, number of attendees, and amount of training needed. We give significant discounts for non-profits and any organization that has a good cause.

Contact us for questions about pricing and to schedule your workshop today!