Ashlee 🤟🏻@ashleemboyer.com · 2mo ago

Answering a question on my new accessibility coaching sessions: Will I be doing the work for you, or teaching you how to do it long term? Teaching is preferred, but if you have other tasks to handle ASAP I can help there too! Interested? Schedule a free discovery call: semanticfish.com/coaching

Ashlee 🤟🏻@ashleemboyer.com · 2mo ago

Looking for 1:1 support in work related to planning, design, development, testing, & documentation? I'm opening up 1:1 accessibility coaching sessions! ☺️ For folks who are doing their best despite declining institutional support. Info & interest form: semanticfish.com/coaching

Accessibility coaching sessions officially open!

Ashlee 🤟🏻@ashleemboyer.com · 2mo ago

I'm opening up 1:1 accessibility coaching sessions! ☺️ Aimed at helping folks who are doing their best to make their work accessible despite declining institutional support. Topic areas include planning, design, development, testing, & documentation. Info & interest form: semanticfish.com/coaching

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

Ashlee 🤟🏻@ashleemboyer.com · 3mo ago

Claude admits bias against accessibility and look at that! It’s the same bias that a whole lot of humans have against accessibility. “Claude treats accessibility fixes as optional trade-offs rather than requirements, even when the project's own rules say otherwise.” github.com/anthropics/c...

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..."

Digital Accessibility Job Board | A11yjobs

Browse 270 recent accessibility jobs. Find roles in WCAG, ADA compliance, screen readers, VPATs, and digital accessibility. Join our community of accessibili...

a11yjobs.com

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

The Practical Accessibility Course

A get-right-down-to-it online course for Web designers and developers who want to start creating more accessible Web user interfaces and digital products today

practical-accessibility.today

1/4 "One unifying feature of all of the uses of 'access' is that they convey a positive outcome—'access' is routinely understood as an individual benefit or a public good." Elizabeth Ellcessor, Restricted Access, p. 7

"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 ☕

Ashlee @ SFCG@ashlee.semanticfish.com · 4mo ago

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! 👀

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.

Anna E. Cook@annaecook.com · 4mo ago

The WebAIM Million 2026 report is out, it reports on overall accessibility across the web: 1. The number of failures increased 10.1% YOY 2. The average number of page elements increased 22.5%YOY Meaning accessibility progress is backsliding. Personally, I am quite certain this is related to AI.