What should the tech community learn about accessibility?

It’s May, the month when we at Technical.ly celebrate both Philly Tech Week in our HQ city and Accessibility month of our editorial calendar.

A quick recap of the year’s editorial calendar coverage so far:

• January — The realLIST
• February — How to Get Hired
• March — Women in Tech
• April — Growing Industries

We’re defining “accessibility” as the design of technology — products, devices, services, environments — that is inclusive of as many groups of people as possible. Our reporting this month might include an explainer on how to build a more universally usable website, a profile on a notable local advocate or a deep dive into how inclusive — of all abilities and qualities — your city’s tech meetups really are.

Some past reporting on the topic:

• 6 ways your tech is making it harder on people with disabilities
• 911 texting a step toward Delaware’s accessibility goals
• Smithsonian museum visitors in DC who are visually impaired can benefit from this new tech
• Accessibility for all: 5 projects from Abilities Hackathon expanding tech’s reach
• Why this advocate keeps hosting accessibility hackathons on her birthday

This month, we’ve already published one story as part of the theme, on some of the ways Philly tech orgs are trying to make their spaces more accessible. Want to pitch a story or get featured in our coverage this month? Learn more here.

We’re also planning a roundup explainer of accessibility terms to know — think person-first language and assistive technology — for the end of the month, as we did with cybersecurity in both D.C. and Baltimore in April. Send us your ideas for inclusion:

This editorial article is a part of Technical.ly's Accessibility month of our editorial calendar.