Vue FesJapan 2026
The main visual of Vue Fes Japan 2026. It features a silhouette of a V, representing Vue, and a circle, representing the Japanese flag, side by side. The colors are deep matcha-like shades derived from the two colors, and the circle features a Japanese gold marbling pattern.
OtemachiPlace Hall & Conference

Speaker

Cybozu Track
16:35 - 17:50
Shigeyuki-fukuda

Verifying Whether Vapor Mode Breaks Accessibility

Vapor Mode, introduced in Vue 3.6, is a new compilation strategy that manipulates the DOM directly without going through VNodes. But discussion of it has focused almost entirely on performance, and its impact on assistive technology has barely been examined.

Does live region announcement, focus management, and dynamic aria attribute updates behave the same way as in the conventional mode? I chose this topic because I see it as an unavoidable question when considering partial adoption of Vapor Mode in an existing app.

In this talk, I'll report on results from building the same component under both the conventional mode and Vapor Mode, and verifying them from two angles: comparing differences in the accessibility tree using Playwright's ariaSnapshot, and checking actual screen-reader announcements with VoiceOver.

I'll present a list of which items showed differences and which didn't, so you can take it home as a checklist of accessibility considerations to check when migrating to Vapor Mode.

Shigeyuki-fukuda

Affiliation
mov inc.
Title
Web Developer

Shigeyuki-fukuda

Affiliation
mov inc.
Title
Web Developer

Verifying Whether Vapor Mode Breaks Accessibility

Vapor Mode, introduced in Vue 3.6, is a new compilation strategy that manipulates the DOM directly without going through VNodes. But discussion of it has focused almost entirely on performance, and its impact on assistive technology has barely been examined.

Does live region announcement, focus management, and dynamic aria attribute updates behave the same way as in the conventional mode? I chose this topic because I see it as an unavoidable question when considering partial adoption of Vapor Mode in an existing app.

In this talk, I'll report on results from building the same component under both the conventional mode and Vapor Mode, and verifying them from two angles: comparing differences in the accessibility tree using Playwright's ariaSnapshot, and checking actual screen-reader announcements with VoiceOver.

I'll present a list of which items showed differences and which didn't, so you can take it home as a checklist of accessibility considerations to check when migrating to Vapor Mode.