We began working with Seattle Humane Society in February of 2016. They had reached out to us because they needed some emergency help with their website.
We began working with Seattle Humane Society in February of 2016. They had reached out to us because they needed some emergency help with their website.
Last month, a critical WordPress vulnerability triggered emergency patching across the web — and reignited a familiar argument: if WordPress keeps having security problems, why not let AI build something new instead?
It’s a reasonable question.
AI has made software dramatically cheaper and faster to create. But somebody still has to understand it, patch it, test it, and keep it running eighteen months from now.
That’s the part of the “AI instead of WordPress” pitch we think is getting overlooked.
On July 17, WordPress shipped an emergency security release for a vulnerability chain now being called wp2shell.
On October 5, 2023, the W3C published WCAG 2.2 as an official web standard. While WCAG 2.1 remains valid and widely referenced, WCAG 2.2 introduces nine new success criteria and removes one obsolete requirement. These changes reflect a deeper understanding of mobile accessibility, cognitive disabilities, and focus management.
Adoption of WCAG 2.2 varies by jurisdiction:
You're tabbing through a form, reading field labels before you decide what to enter. You tab into a dropdown menu just to see what options are available. The instant it receives focus - before you've even opened it - the page suddenly redirects to a completely different page. You didn't select anything, didn't press Enter, just tabbed through. Now you're disoriented and have to navigate back to find your place.
You're using voice control to navigate a website because typing is painful today. You see a button that says "Submit" - perfect, that's what you need. You say clearly: "Click Submit." Nothing happens. You try again: "Click Submit button." Still nothing. Frustrated, you finally say "Show numbers" to overlay numbers on every interactive element, then speak the number to activate the button.
You're reading a website, but the text feels cramped. Lines are too close together, making it hard to track from one line to the next. Words blur together. You try increasing your browser's font size, but that only makes part of the problem worse - now the text is bigger but still squished together.
If you could just add a little more space between lines, between words, between letters... you'd be able to read comfortably. But when you try using a browser extension to adjust spacing, the layout breaks. Text gets cut off. Paragraphs overlap. Buttons disappear.