Microsoft’s latest Windows 11 test build delivers two changes that punch above their weight: standards-based braille display support that works from the moment you turn on a new PC, and a security policy that ties cloud PC access to a physical smart card. Build 28120.2546, released for the Experimental 26H1 channel on July 21, 2026, may seem like a modest update, but for users with visual impairments and enterprise security teams, it closes long-standing gaps.
Braille Right Out of the Box
For years, setting up a Windows PC without sighted help meant first installing screen-reader software and proprietary drivers before even starting the setup wizard. Build 28120.2546 changes that: Narrator, Windows’ built-in screen reader, can now talk directly to braille displays that use the Human Interface Device (HID) standard. Plug a compatible device into a USB port during the out-of-box experience (OOBE), and you get tactile feedback from the first screen.
Microsoft lists four supported displays: Orbit Reader 20, Orbit Slate 340, Freedom Scientific Focus 40, and APH Mantis Q40. This is a starting list, not a ceiling; any braille device that follows the HID standard might work, but Insider testing will determine real-world compatibility. The key is that you no longer need an extra software layer. The display and Windows recognize each other automatically.
Once the desktop appears, you can pair the same display over Bluetooth through Settings > Bluetooth & devices, giving you wireless freedom. But wired connectivity during setup is the real breakthrough. USB avoids the complexity of pairing a wireless device before the OS is fully configured—no need to fumble with codes, scanning, or radio initialization when you’re still choosing your language and keyboard layout.
This also bolsters privacy. You don’t need to read out your account details or Wi-Fi password to a helper; the braille display lets you confirm sensitive text privately.
Why HID Matters for Accessibility
Refreshable braille displays use rows of tiny pins that rise and fall to form characters. They’re the primary way many deaf-blind people interact with computers. But historically, every display required its own driver, and compatibility could break with a Windows update. HID is an industry standard that defines how devices report data to the OS, similar to how a standard keyboard works without special software.
With native HID support, Narrator can talk to a broad range of displays immediately. That cuts down on deployment headaches for IT admins, lets users switch between PCs without reinstalling drivers, and reduces the risk that an older device becomes unusable because its manufacturer stopped updating software. Microsoft has centralized braille settings under Settings > Accessibility > Narrator > Braille, so you can configure everything from one place.
Voice Access Adds Portuguese and Korean
The same build expands Voice Access, the hands-free control feature, to three new language variants: Portuguese as spoken in Portugal, Portuguese as spoken in Brazil, and Korean. Voice Access already understood English and a handful of other languages, but these additions open it to millions more users.
Brazilian and European Portuguese sound very different, so treating them separately boosts accuracy. Korean presents its own challenges with Hangul composition and grammar. Users in these regions can now dictate text, open apps, click buttons, and navigate by numbered overlays—all by voice.
This isn’t just dictation; it’s full system control. Voice Access lets you say “click Start,” “scroll down,” or “press Enter,” and the OS obeys. For people with limited mobility, that can be transformative. But as any voice-control user knows, the real test is whether it works reliably across all your apps, from modern UWP windows to old Win32 utilities.
Smart Cards Now Lock Cloud Desktops
For enterprises, the headline is a security policy update. Build 28120.2546 extends smart card removal behavior to Azure Virtual Desktop and Windows 365 sessions that use Microsoft Entra ID authentication. Now, if you pull out your smart card, Windows can immediately disconnect the remote session, just as it already does for local sign-ins.
Smart cards are physical authentication devices often used in government, healthcare, and finance. An employee inserts a card and enters a PIN to log in; remove the card, and the session should lock. Until now, that logic didn’t always apply to cloud-hosted desktops. Someone could log into Windows 365, pull the card, and leave the session open on a shared terminal.
The new policy closes that gap. When enabled, removing a redirected smart card triggers a disconnect—not a sign-out, mind you. The session continues to run on the cloud PC, so you can reconnect after re-inserting the card without losing open work. But the local endpoint loses visibility, and anyone walking up to that screen sees only a lock prompt.
This is a huge deal for regulated industries that need consistent hardware-token enforcement everywhere. It also reduces the risk of “lunchtime attacks,” where a logged-in session is left unattended. Combined with screen timeout policies, it gives admins more granular control.
Small but Smart Improvements
A few other tweaks round out this build. The Bluetooth Quick Settings menu can now be navigated with a gamepad—a nod to living-room PCs and handheld gaming devices. A crash in the Graphics Settings page, which let you assign apps to a specific GPU, is fixed. And system sounds get refined for dark mode, though Microsoft hasn’t detailed exactly what changed.
That last point might sound trivial, but audio cues matter. A sharp notification tone can feel jarring when you’re working late with dark visuals. Softening those sounds while keeping them recognizable is a delicate balance. Users with hearing impairments will want to verify that critical alerts still stand out.
What This Means for You
For most home users, this build won’t dramatically change your daily Windows experience. But if you rely on a braille display or hands-free controls, it’s a direct quality-of-life upgrade. Setting up a new machine independently, without waiting for a sighted helper, is a big step forward. Voice Access users get support for their native language, making voice commands less frustrating.
For IT administrators, the smart card policy is the star. It lets you apply the same physical security standard to cloud desktops that you enforce on office workstations. The accessibility gains also simplify deployment: standard braille drivers mean fewer custom images and less driver chaos.
Just remember this is an Experimental build. Features roll out gradually; two PCs on the same build might not show the same options. Don’t install it on your only production machine, and back up your data first.
How We Got Here
Microsoft reorganized its Insider channels in early 2026, replacing Canary and Dev with a broader “Experimental” label. The 26H1 branch indicates the codebase that might feed a future feature update, but it’s not a guarantee. Many of these components could ship independently or slide into a later release.
Braille support has been a long time coming. The industry has been shifting toward HID for years, but Windows lagged behind macOS and iOS in native integration. Voice Access has been steadily adding languages since its debut in 2022. And as more enterprises move to Azure Virtual Desktop and Windows 365, the security gap around smart cards became too big to ignore.
What to Do if You’re an Insider
If you’re on the Experimental 26H1 channel, you can download Build 28120.2546 now. Here’s how to test the biggest features responsibly:
- Braille: Connect a supported display via USB, restart into OOBE (or reset a test PC), and verify that Narrator provides tactile output from the first language selection screen. Then pair via Bluetooth and check reconnection after sleep.
- Voice Access: Switch your display language to Portuguese or Korean, enable Voice Access under Settings > Accessibility, and try opening apps, dictating, and navigating. Report any recognition errors or crashes.
- Smart card: Set up a test Azure Virtual Desktop or Windows 365 session with Entra ID and a redirected smart card. Remove the card and confirm the session disconnects. Re-insert the card and verify you can log back in.
- Gamepad: Open Bluetooth Quick Settings and see if you can navigate entirely with a controller.
- Graphics: Open Settings > System > Display > Graphics, switch between power-saving and high-performance GPUs, and make sure it no longer crashes.
- Sounds: Toggle dark mode and listen for changed system sounds. Note any that become hard to distinguish.
Always submit feedback through the Feedback Hub (Win+F) with exact hardware models, firmware versions, language packs, and step-by-step accounts of any problems.
What’s Next
Microsoft will likely broaden the braille display compatibility list in future builds, based on Insider telemetry. Voice Access will keep adding languages. And enterprise customers should watch for official documentation on the smart card disconnect policy—event logging, deployment guides, and client-side requirements are still needed before it’s production-ready.
If you see these features move to the Beta channel, that’s a sign Microsoft is getting confident. For now, Build 28120.2546 offers an early taste of a more accessible and more secure Windows 11, one small but significant improvement at a time.