We knew through analytics that "Resources" on Bay Area Legal Services were not reaching as many people as they should be. We used usability testing to make small changes that greatly improved user engagement.
We want our websites to be able to reach as many people as possible. If done right, your site's visual design and theme will ensure that color contrasts work for the vast majority of people, that screen reader users and keyboard navigators can use your menus, and that other accessibility benchmarks are met. So, when all is said and done, remaining accessibility issues usually come down to the content that editors add to a site. This is where accessibility checkers prove useful.
I recently went through the process of setting up an RSS Feed for our blog here at DevCollaborative so that our articles can be syndicated to Planet Drupal. It had a surprising amount of gotchas and the documentation was dated and sparse. So I thought I’d help remedy that by sharing what I learned.
Clayton introduced me to the Consentful Tech Project, which provides a framework for applying Planned Parenthood's FRIES definition of consent to applications. Clayton and I played around with extending that framework into the world of web UX, and the result of those thought experiments is our talk, Consentful UX. A video of the talk and its slides are here.
This is good news for nonprofit organizations on Drupal 7 who don’t have funds, capacity, and/or time for a rebuild right now. We'll attempt to tackle some questions about Drupal versions, upgrades, rebuilds, timing, and planning website projects here.
