Service
Accessibility & Compliance
Accessible websites work better for everyone. I help organizations identify and remove accessibility barriers, improve Drupal implementations, and incorporate accessibility into everyday development practices rather than treating it as a checklist at the end of a project.
Overview
Accessibility works best when it's part of how a website is designed, built, and maintained from the beginning. Drupal provides a strong foundation, but an accessible platform can still produce inaccessible websites when themes, custom components, content, and editorial practices aren't designed with accessibility in mind.
I help organizations evaluate their Drupal sites for accessibility problems and, more importantly, determine how to fix them. That can include reviewing templates and components, improving semantic markup and keyboard navigation, addressing color and contrast issues, evaluating forms and interactive elements, and helping teams understand how their own content practices affect accessibility.
Compliance requirements such as WCAG and Section 508 provide an important framework for this work, particularly for government and other public-facing organizations. But passing an automated accessibility scan isn't the finish line. My goal is to help teams build sites that work well for real people and establish development and editorial practices that keep them accessible as the site continues to change.
I help organizations evaluate their Drupal sites for accessibility problems and, more importantly, determine how to fix them. That can include reviewing templates and components, improving semantic markup and keyboard navigation, addressing color and contrast issues, evaluating forms and interactive elements, and helping teams understand how their own content practices affect accessibility.
Compliance requirements such as WCAG and Section 508 provide an important framework for this work, particularly for government and other public-facing organizations. But passing an automated accessibility scan isn't the finish line. My goal is to help teams build sites that work well for real people and establish development and editorial practices that keep them accessible as the site continues to change.
Common challenges
- Automated accessibility scans are reporting problems, but the team isn't sure how to prioritize or resolve them.
- A Drupal theme or custom component works visually but creates problems for keyboard or assistive technology users.
- Accessibility wasn't considered during the original design and now needs to be addressed without rebuilding the entire site.
- Content editors need clearer guidance for headings, links, images, tables, documents, and other content.
- A redesign or Drupal modernization project needs accessibility incorporated from the beginning.
- The organization needs to work toward WCAG or Section 508 requirements.
- Accessibility fixes have been made before, but new content and features keep introducing the same problems.
- Developers need help distinguishing problems that belong in Drupal code and templates from those that need to be addressed through content or design.
Typical deliverables
- Accessibility reviews and technical assessments
- WCAG-focused remediation recommendations
- Drupal theme and template improvements
- Semantic HTML and ARIA improvements
- Keyboard navigation and focus management fixes
- Accessible form and interactive component improvements
- Accessibility remediation during Drupal upgrades and redesigns
- Guidance for content editors and site administrators
- Accessibility development standards and documentation
- Prioritized remediation plans for existing sites