A client paid thousands for an AI accessibility overlay and still got complaints from deaf users. Notes on what does help: text-based contact options, human captions, visual and haptic cues in place of sound, and accessibility handled before launch instead of after.
A client thought their WooCommerce recommendation engine was broken because accuracy at a 0.5 threshold read 51%. The ranking was fine, the threshold was not. This walks through checking AUC in a spreadsheet with sorted scores and the trapezoidal rule.
A WooCommerce recommendation engine kept timing out the server, and the weights oscillated instead of settling. Swapping the basic update rule for Momentum and then Adam is what fixed it, and this explains why adaptive step sizes matter on messy data.
I spent three hours hand-coding cubic-bezier keyframes for a WooCommerce build and the bounce still felt stiff. A spring-based SVG animation workflow with SMIL exports got it right and kept the animation inside the asset.
A client’s desktop PageSpeed score was 98 while his conversions fell. Why lab tests miss what real visitors feel, and how to time a WooCommerce cart action with the User Timing API.
A client’s wallpaper gallery took down its own dashboard hours after launch. Pruning the image sizes WordPress generates and offloading originals to object storage cut upload processing by about 70%.
An agency gallery held 14 years of high-resolution assets and took 12 seconds to load. Caching the resolution URLs in a transient made it worse; generating the links from a CDN naming convention fixed it.
A client’s WooCommerce sync kept dropping SKUs because the same iterator was read twice. Here is what the iterator protocol actually does, and why an iterable and an iterator are not the same thing.
A legacy vendor portal with no IDs, no classes and no API broke every CSS selector we threw at it. One XPath expression replaced fifty lines of them, and it has not broken since.
Console logging the Gamepad API at 60 frames per second tells you nothing useful. Here is the visual debugger I built instead, with its styles isolated in a CSS cascade layer so they stop fighting the theme.