Typography is treated as a brand decision and an accessibility decision in different meetings, but they're the same decision. This WPA11y Day session covers how font choice, line length, spacing, and contrast directly affect cognitive load and reading fluency, especially for users with dyslexia and low vision. Worth watching if you think WCAG text contrast requirements are the whole story.
#accessibility #a11y #typography

https://wpaccessibility.day/2025/sessions/typography-readability-and-digital-accessibility/

Still seeing placeholder used as a label in production code in 2026. The text disappears when users start typing, fails contrast requirements, and isn't reliably announced by all screen readers. It was never meant to be a label. Use a visible, persistent label element. Full stop.
#accessibility #forms #a11y

https://html5accessibility.com/stuff/2025/07/21/super-short-note-placeholder-perfidy/

Microsoft added accessible math support to Word and PowerPoint, with MathML and LaTeX rendering for screen readers and other AT. STEM content has been a persistent gap in document accessibility. If your users create or consume math-heavy files in Office, this is worth knowing and worth testing with your AT of choice.
#accessibility #assistiveTechnology #Microsoft365

https://techcommunity.microsoft.com/blog/microsoft365insiderblog/make-math-inclusive-for-everyone-with-microsoft-365/4489147

Honest GAAD take: years of awareness days have not moved the needle enough on actual digital accessibility. The gap between "people know it matters" and "people do it" is still enormous. Awareness without accountability and tooling doesn't close that gap.
#accessibility #GAAD #a11y

https://buttondown.com/access-ability/archive/gaad-2026-not-much-to-celebrate-yet

The argument: if CSS enforced semantic HTML by default, skipping accessibility would require active effort to undo. Right now the defaults let you style divs into fake buttons and never notice. The TailwindCSS model in particular makes it trivially easy to write presentation-first markup with zero structural meaning. Accessibility being opt-in is partly a tooling problem
#css #a11y #semanticHTML

https://www.craigabbott.co.uk/blog/2026/our-css-isnt-opinionated-enough/

Brands spend enormous resources building visual identity and then cut off a significant portion of their audience with inaccessible choices. Victoria Ottah's WP Accessibility Day talk frames this as a brand effectiveness problem before it's a compliance one. If people can't read, see, or understand your brand, you're not reaching them, and that's a business failure with a straightforward fix.
#accessibility #brandDesign #a11y

https://wpaccessibility.day/2025/sessions/invisible-until-it-hurts-rethinking-brand-design-through-the-lens-of-accessibility/

Over a billion people live with disabilities. Disability is not as a technical edge case but as a central feature of society that we consistently design around instead of for. The line between disabled and not yet disabled is thinner than most designers and devs acknowledge.
#disability #accessibility #inclusion

https://thetricontinental.org/newsletterissue/living-with-disabilities/

Apple Intelligence is getting baked into accessibility features, not just as a separate AI layer. Things like Personal Voice improvements, eye tracking, and enhanced screen reader support. The integration approach is what matters here: AI as a capability that makes existing a11y features more effective.
The right question is whether these features actually get tested with disabled users before shipping or just assumed to help.
#accessibility #apple #a11y

https://lifehacker.com/tech/apple-new-ai-accessibility-features

Skip links are one of those fundamentals that still get botched constantly. Keyboard users shouldn't have to tab through 50 items to get to main content. This walkthrough covers correct implementation, including the visibility behavior that trips up devs who've only half-built it before.
#accessibility #keyboard #a11y

https://hackernoon.com/how-to-implement-skip-to-navigation

Generic elements like divs and spans have no implicit role, so adding aria-label to them does nothing useful for screen reader users. Manuel Matuzovic breaks down exactly why this pattern seems reasonable and why it still causes confusion. If you're auditing code today, this is one of the easier wins to flag.
#aria #accessibility #a11y

https://www.matuzo.at/blog/2026/aria-label-generic-elements