Atlanta-based community organizer with roots in the disability rights movement. Formerly worked at a Center for Independent Living.
Tone: passionate, empathetic
Voice: centers lived experience, connects to real people
CORS Emphasis: Community Input
Regional Focus: community health centers, HBCUs, rural access, grassroots organizations
Favorite Resource: Southeast ADA Center
While operational capacity matters for accessibility programs, organizations that prioritize direct community input over internal infrastructure often achieve better real-world outcomes for users with disabilities.
CSS transforms like rotateX() create stunning visual effects but can render content completely inaccessible to screen reader users and people with disabilities.
A CSS-Tricks article on rotateZ() reveals a fundamental disconnect between web development education and accessibility reality.
CSS rotation effects create significant barriers for users with vestibular disorders and cognitive disabilities, affecting 35% of adults over 40.
Legal defensibility emerges not from documentation alone, but from authentic engagement with disabled users throughout development.
Community feedback reveals that technical excellence in accessibility implementation creates stronger legal defenses than reactive compliance patches.
While AI dominates accessibility headlines, real progress comes from amplifying disabled voices and community-driven solutions that technology giants overlook.
Organizations using capacity-building as a prerequisite for community engagement risk institutionalizing the barriers they claim to address.
While systematic testing catches violations, the developer community must drive CSS specification improvements to prevent accessibility barriers at their source.
While CSS contrast-color() may offer legal protection, focusing solely on litigation defense ignores accessibility's fundamental purpose: creating inclusive experiences for disabled users.
The CSS hypot() function enables complex geometric calculations but creates new accessibility barriers when mathematical concepts become interface requirements without proper semantic support.
When organizations prioritize internal integration over community representation, they create sophisticated systems that exclude disabled voices.
Integration strategies sound efficient, but implementation data shows why many organizations struggle with embedded accessibility—and when parallel programs deliver better outcomes.
The integration versus tension debate misses the fundamental question: how do we center disabled voices in organizational transformation?
The Title II extension's real value lies in creating space for meaningful disability community engagement that shapes implementation decisions from the ground up.
The compliance-community divide isn't about maintaining separation—it's about creating structures where different methodologies challenge each other.
The sequential versus parallel accessibility debate misses a critical third option: community-driven hybrid models that adapt to organizational readiness.
Field research shows resource-constrained organizations achieve better accessibility outcomes through focused sequential approaches over parallel strategies.
The legal risk versus community engagement debate misses a fundamental truth: sustainable accessibility requires integrated approaches that leverage community expertise to strengthen compliance.
The most transformative accessibility programs emerge from authentic community engagement rather than legal infrastructure, driving innovation and sustainability.
When organizational readiness frameworks override community feedback, we risk creating accessibility standards that serve compliance departments better than disabled users.
The real infrastructure crisis isn't too much technical content—it's that community voices reach practitioners only after solutions are already built.
While organizational readiness frameworks matter, APCA's trajectory shows that meaningful accessibility progress emerges from practitioner communities.
The compliance versus maturity debate oversimplifies accessibility strategy. Organizations achieve sustainable outcomes by integrating legal foundations with robust community engagement, not by choosing between them.
The real crisis isn't too much technical content—it's the systematic exclusion of disabled voices from accessibility decision-making structures.
While automation provides immediate efficiency, community testing creates sustainable accessibility cultures that reduce long-term compliance costs and deliver superior user outcomes through deep organizational learning.
While compliance frameworks provide structure, transformative accessibility advances emerge when organizations center disabled voices in design processes.
While legal urgency drives AI accessibility implementation, sustainable solutions emerge from deep community engagement rather than reactive compliance.
While market dynamics create short-term accessibility wins, sustainable framework improvements require coordinated community standards that outlast competitive cycles.
While CSS automation offers organizational efficiency, research shows that hybrid models incorporating disabled user feedback and community testing networks deliver superior accessibility outcomes at enterprise scale.
Technical accessibility discourse that prioritizes practitioner expertise over disabled community leadership perpetuates exclusion and undermines progress.
While GSAP's SplitText problems are real, the development community's response reveals deeper systemic issues that require collaboration, not criticism.
The accessibility community produces hundreds of resources weekly, but this week's reading list reveals a troubling pattern: disabled voices are absent.
While automated testing catches obvious ARIA role violations, the deeper accessibility crisis lies in the gap between technical compliance and actual user experience in production environments.
Three JavaScript-built comboboxes violate multiple WCAG 2.1 criteria by missing essential ARIA roles and properties, creating invisible barriers for screen reader users.
Automated analysis revealed navigation barriers in dialog implementations that testing missed, exposing gaps between tool detection and user experience.
Eight distinct WCAG violations in a single wizard interface reveal how multi-step forms create cascading barriers for disabled users.
While accessibility professionals debate WCAG 3.0 and API specifications, disabled community members struggle with basic website navigation and inaccessible public services. The disconnect between technical innovation and community needs reveals troubling priorities in accessibility practice.
While WCAG-EM 2.0 offers improved standardization for accessibility evaluation, the real question is whether standardized methodologies actually improve disabled users' experiences or simply make compliance officers more comfortable. The most successful accessibility improvements come from treating evaluation as an ongoing conversation with disabled users rather than a periodic audit.
New W3C Cognitive Accessibility Research Modules represent the first serious effort to understand what people with cognitive and learning disabilities actually need from technology—moving beyond compliance to address real barriers in voice systems, navigation, online safety, and decision-making.
A recent DOJ settlement highlights how inaccessible patient portals create dangerous barriers for disabled patients managing chronic conditions. Healthcare systems that build accessibility into their core operations see improved outcomes for all patients.