Android 17 ships, axe-core adds a tab rule, React Native fixes hanging promises, and WWDC brings an accessibility lab. This is my monthly roundup of accessibility changes for teams shipping web, mobile web, iOS, Android and React Native. Each item links to its source.

axe-core 4.12 adds aria-tab-name

Web · Jun 1, 2026

A new aria-tab-name rule requires tabs to have an accessible name. landmark-complementary-is-top-level was deprecated.

Why it matters at work: Icon-only tabs are common in design systems. Expect new issues on them after upgrading, and fix them in the component rather than page by page.

GitHub release notes for axe-core 4.12.0 listing the new aria-tab-name rule
axe-core 4.12.0 release notes.

Sources: axe-core 4.12.0 on GitHub

React Native 0.86: AccessibilityInfo queries no longer hang

React Native · Jun 11, 2026

isDarkerSystemColorsEnabled, isHighTextContrastEnabled and prefersCrossFadeTransitions now resolve to false on platforms that don’t support them, instead of never resolving.

Why it matters at work: Code that awaited these on the wrong platform could stall forever. Remove any timeouts you added to work around it.

React Native 0.86 release post
React Native 0.86 release post.

Sources: React Native 0.86

Android 17 rolls out to Pixel

Android · Jun 16, 2026

Apps targeting API 37 that build their own text fields can report text changes during complex input (Chinese, Japanese, Korean, Vietnamese) with AccessibilityEvent.setTextChangeTypes and TextAttribute, so TalkBack can read what is being composed.

Why it matters at work: If your app has custom text editing, CJKV screen reader users have probably had a poor experience. These APIs let you fix that.

Android 17 behavior changes page, accessibility section on complex IME input
Android 17 behavior changes for apps targeting API 37.

Sources: Android 17 behavior changes

WWDC26: the Accessibility Technologies group lab

iOS · June 2026

There was no “What’s new in accessibility” session this year. Apple’s accessibility engineers answered questions in a recorded lab instead: image descriptions, Live Recognition and Accessibility Reader. They said there is no new text-to-speech API this year, and confirmed that removing the image trait stops VoiceOver’s generated description.

Why it matters at work: For decorative images, removing the image trait (or hiding the element) is now the way to keep VoiceOver from describing them.

WWDC26 Accessibility Technologies group lab video page
WWDC26 session 8005.

Sources: Accessibility Technologies group lab

WAI-ARIA 1.3 Working Draft

Standards · Jun 4, 2026

A new WAI-ARIA 1.3 Working Draft was published, with a Candidate Recommendation planned.

Why it matters at work: Nothing to change yet, but watch for new roles and properties reaching browsers.

Sources: WAI-ARIA 1.3

Chrome 150: tab and menu semantics in DevTools

Web · Jun 30, 2026

DevTools’ own tabs, tooltips and menu items now expose the right roles to screen readers.

Why it matters at work: A small one, but a good sign for DevTools users who rely on screen readers.

Sources: What’s new in DevTools (Chrome 150)

For the whole year in one place, read What changed in accessibility in 2026. For more depth on August to November, see A11y Signal, Issue 01.


© 2026 Giovani Camara. The text of this post is licensed under CC BY 4.0: you may share and adapt it if you credit Giovani Camara and link to giovanicamara.com. Screenshots show third-party pages, belong to their owners, and are not covered by this license.

The post Accessibility updates: June 2026 appeared first on Giovani Camara Blog.