Open Source Accessibility

Slides: �https://tinyurl.com/csunopensource

Introduction

This session will explore how Open Source Software and the broader open source movement are improving accessibility and disability inclusion.

It will also highlight opportunities for individuals and different types of organizations within the accessibility ecosystem to contribute.

​

2

Slides: �https://tinyurl.com/csunopensource

Order of events

Ed Summers & GitHub

Josh Miele & Caos

Jen Mankoff & Allyhood.org

Joe Devon & GAAD

3

Slides: �https://tinyurl.com/csunopensource

What is open-source?�Ed Summers, GitHub

4

Open-source licensing

• Common misconception #1: Public equals open
• Reality: Source code is closed, by default
• Authors must take explicit action to open it
• They do that with a license

Ed | 5

Open-source way of working

• Transparent
• Decentralized
• Self-organizing
• Meritocratic
• Egalitarian

Ed | 6

Getting involved

• Common misconception #2: Only developers are needed
• Reality: Success requires many skillsets
• User
• Participant
• Contributor

Ed | 7

Examples

• WCAG:3 github.com/w3c/wcag3
• NVDA: github.com/nvaccess/nvda
• axe-core: github.com/dequelabs/axe-core

Ed | 8

Resources

• opensource.org
• theopensourceway.org
• opensource.guide

Ed | 9

CAOS

Josh Miele

10

What is CAOS?

CAOS is a nascent global NGO whose mission is to sustainably support open-source communities in:

• the creation of accessible open-source projects
• the creation of open-source accessibility tools and technologies

Josh | 11

Why Open Source?

The known benefits of open source software and communities include:

• Expanded opportunities for education, employment, and economic advancement
• Connections and networking through inclusive and democratic OS communities
• Skill-building through mentorship and collaborative development.

12

Why CAOS

PwD are disadvantaged across the board and around the world. This includes: educational, employment, networking, mentorship, and skill-building opportunities, and more.

What are the barriers that prevent PwD from reaping the benefits sewn by open-source projects and communities?

• Inaccessible community processes
• Inaccessible tools
• leading to inaccessible open-source projects

​

​

13

What is CAOS?

The Center for Accessibility and Open Source will support:

• Sustainable disability inclusion within open-source communities through mentorship and training programs
• Use of accessible tools and processes within open-source communities by developing and sharing best practices
• Accessibility of projects created by open-source communities through advisory and training programs

​

​

Josh | 14

How can you get involved?

Join the growing CAOS community: CAOS-announcements+subscribe@googlegroups.com

​

15

A11yhood.org �Jen Mankoff, CREATE

16

AT in open source communities

Searched for words like “accessibility” in ravelry | github | thingiverse → over 1440 repositories/things

Small (but growing)

• 582 (Github)
• 719 (Ravelry)
• 141 (Thingiverse)

17

Accessibility Topics on Ravelry (Knitters)

18

Accessibility Topics on Thingiverse (Makers)

19

Accessibility Topics on Github (Coders)

20

But nothing brings it all together

Unstructured text / inconsistent metadata and schema

• Discoverability is hard (1442 out of over 427M)
• Only ravelry directly supports search of accessible things

Existing AT Repositories compile some data:

• AbleData; Open Assistive (openassistive.org) collected and catalogued resources only through 2022
• Product listings: e.g., JAN; GPII Unified Listing; Accessible Agriculture; MakeGood -- Don’t combine physical AT and software AT; �not open source

21

OpenSource efforts also exist

Right to repair (GOAT)

Archive work (GOAT)

Disability leadership (GOAT)

DIY (both)

3D printing / hardware (both)

Volunteers making for disabled people (both)

Hack events & Community Building (both)

22

Grassroots Open Assistive Technology (GOAT, openassistivetech.org)

Our Addition: A11yhood

Right to repair (GOAT)

Archive work (GOAT)

Disability leadership (GOAT)

DIY (both)

3D printing / hardware (both)

Volunteers making for disabled people (both)

Hack events & Community �Building (both)

Software AT

Accessible hardware design and assembly support

Search and discoverability

Lived Experience (reviews)

23

Planned Study of Open Source AT Use

Learn about user needs

• How do people find AT?
• What do they need to know about AT to invest in it?
• How do intersectional identities factor into AT choices?
• How do people repurpose, modify, and share tech for access?

24

Plan for building: Tools and metadata

Finding the right AT

• What AT supports a specific need?
• Does it run on my hardware? What skills do I need to install/modify it?
• Do people like it?

Learning about AT (what disabilities benefit from AT X)

Adding metadata through community engagement

25

Contributing to A11yhood.org

Join our a11yhood.org github discussion to contribute: �tinyurl.com/allyhood-community

​

Join the CAOS mailing list for updates: CAOS-announcements+subscribe@googlegroups.com

26

Accessibility, Open Source & AI�Joe Devon, GAAD Foundation

27

Global Accessibility Awareness Day (GAAD)

Joe | 28

The WebAIM Million Report

29

The SOMAA Report

72%

30

Product accessibility is downstream of culture

Joe | 31

No “CFO Excuse”: Money does not = craft

Joe | 32

“When I want my devs to improve their code quality, I open source it”

Joe | 33

AI is for Agency

Joe | 34

AI Benchmarks & Evals

Joe | 35

Coding with AI

Joe | 36

ServiceNow Partnership

Joe | 37

Eamon McErlean, VP & Global Head of Digital Accessibility & Globalization

Working Title - ALICE

Testing 6 WCAG Criteria

Joe | 39

Launches Global Accessibility Awareness Day

Joe | 40

How to learn more and participate

Subscribe to Joe Dev on Tech LinkedIn Newsletter (weekly)�bit.ly/jdlinews

​

Subscribe to A11y & GenAI podcast: linktr.ee/a11ygenai�

Email me: joe@a11yaudits.com

41

Audience Q&A

42