Ashlee @ SFCG

Issue #3 of #TheAccessibilityPond is out! What's in store this week: - The Pond’s first 90 days - My first 6 months as a W3C Invited Expert - My week in AGWG buttondown.com/the-accessib...

Accessibility coaching sessions officially open!

I added a new page to the @semanticfish.com website for anonymous questions! Accessibility questions are my fave but not required. ☺️ semanticfish.com/ama Depending on the content, I'll probably lean towards answering in something like a blog posts.

I’m opening up sessions for individual accessibility coaching soon! ☺️ We can work through something you’re stuck on, general questions, reviewing something you already have, brainstorm, chat about resources. Topic examples: design, dev, content, workflows, team norms, design systems, testing.

Tagging for visibility #a11y #accessibility

Today I learned that Ajax/AJAX is short for: Asynchronous JavaScript and XML Why haven't I put this together before??? 😂

“Free” content about disability inclusion and accessibility shouldn’t be walled behind a form that requires folks’ name, email, and company+job info. That content might be “free” in terms of financial cost, but it’s not free in terms of privacy cost.

2026 Accessibility hiring looks busy, yet the patterns show underlying weakness newsletters.feedbinusercontent.com/300/300e57d6... "Accessibility job postings are up. On a11yjobs.com, even at the end of the year when things normally slow down, the volume feels meaningfully different..."

Allow me to follow this with a shameless plug that you can learn accessibility and improve your job prospects with Practical Accessibility: practical-accessibility.today Make sure to read the article to also be aware of common red flags in accessibility job postings. #a11y

"After all, if a so-called participatory culture only facilitates the participation of those who are already privileged, then its progressive potential is unrealized, if not transformed into a regressive affirmation of existing power structures." Elizabeth Ellcessor, Restricted Access, p. 5

If you have a <label> and <input>, just set the "for" attribute on the <label> and reference the <input>'s ID value. No need to additionally set "aria-labelledby" on the <input>. 🥰

When truncated text goes too far:

Hi! If you display a tooltip when an element is focused or hovered, the Accessible Name of that element might need to be the exact same text. If that element is an icon-only button? Show me an example of when it shouldn't match. In my experience, I think it's just about always necessary!

Hi! If you're using the aria-controls attribute, make sure the elements referenced actually exist on the page. No reason to reference elements that don't even exist! 🥰

Hi! Your <button> probably doesn't need a "tabindex" attribute. It's actually focusable by default. 🥰

A new blog post is brewing ☕

I use a LOT of bookmarklets in a11y work. Been migrating them to @polypane.app Snippets (brilliant feature!) and one I use for checking image alt inspired a new blog. How to handle visual-only icons — bc I've used aria-hidden forever but it's a *state* which implies dynamic. Now reconsidering! 👀

Been thinking about writing a history of WAI-ARIA, the APG, and how the most popular frontend component libraries are over-engineered. The new WebAIM Million report motivates me even more! Their conclusion about worsening accessibility is AI/LLM-assisted coding (aka "vibe coding"). I 100% agree.