WordPress

Web Accessibility made easy for WordPress

NFB, discovered how difficult it is for low-vision users to use the internet

Title 3 lawsuits

WCAG 2.1
- Text alternative, media, adaptable, distinguishable
- Keyboard access, time, navigation, seizures
- readable, predictable, input assistance

Don’t use click here and read more on links. actually link to what it is.
don’t use color to convey meaning
- such as required fields in red
- instead use required fields are red and have an asterisk.
make the font at least 16px or higher — dependent on actual font size
error handling — input fields — review errors below, title is required.
tools such as Skip to content, menu, footer.

2007 started using WordPress
2009 started taking a deeper drive
2013 contributions to WordPress
- a simple css bug fix 🙂
WordCamp Providence 2013
- Contributor Day met @nacin
- Ticket, Improving passwords for users
- First experience in actual collaboration to core
Lurking Phase
- watched Slack at .org
Volunteering Phase
- testing patches, administrative tasks
2015 Community Summit
2018 Core Committer
2019 Triage Team
- Reduce open tickets
Why Contribute?
- Knowledge and Experience
- Career Advancement
- Cultures and backgrounds
- New Friendships
- FOSS contributions transcend jobs

Be through and careful
attention to detail
provide very strong details and examples on how to recreate the problem
be patient
be curious
be empathetic
Tips to be successful
Understand the time requirements and be realistic. Don’t take on to much.
Set realistic expectations
Understand the projects priorities
- IE block editor, phase 2 and phase 3
All contributions are valuable
Remember that you’re not alone
Assume good intent, even if frank feedback sounds rough or personal (cultural differences)
Don’t be embarrassed by your code
Master specific topics. Be an expert it a couple areas
Being a generalist has value

second day preparations for #wcoc start with coffee

Prepping for the second half of WordCamp Orange County.