windows

Releasing Windows 10 Build 19042.1081 (20H2) to Release Preview Channel Hello Windows Insiders, today we’re releasing 20H2 Build 19042.1081 (KB5003690)to the Beta and Release Preview Channels for those Insiders who are on 20H2 (Windows 10 October 2020 Update). This update includes the following improvements: This update includes the following improvements: We fixed an issue that causes blurry text on the news and interests button on the Windows taskbar for some display configurations. We fixed an issue that causes communication between apps to stop working after you enable the “AppMgmt_COM_SearchForCLSID” policy. We fixed a performance issue in the MultiByteToWideChar() function that occurs when it is used in a non-English locale. We fixed an issue that prevents sorting from working properly when using multiple versions of National Language Support (NLS) sorting. We fixed an issue in a small subset of users that have lower than expected [ more… ]

Releasing Windows 10 Build 19043.1081 (21H1) to Beta & Release Preview Channels Hello Windows Insiders, today we’re releasing 21H1 Build 19043.1081 (KB5003690) to the Beta Channel & Release Preview Channel for those Insiders who are on 21H1. See our blog post here on preparing the Windows 10 May 2021 Update (21H1) for release. This update includes the following improvements: We fixed an issue that causes blurry text on the news and interests button on the Windows taskbar for some display configurations. We fixed an issue that causes communication between apps to stop working after you enable the “AppMgmt_COM_SearchForCLSID” policy. We fixed a performance issue in the MultiByteToWideChar() function that occurs when it is used in a non-English locale. We fixed an issue that prevents sorting from working properly when using multiple versions of National Language Support (NLS) sorting. We fixed an issue in a small subset [ more… ]

Improving contrast in Microsoft Edge DevTools: A bugfix case study Creating accessible products means most of all being aware of the usability issues your designs and code can cause. When creating new products, Microsoft follows a strict workflow of accessibility reviews of designs, code reviews and mandatory audits before a new feature can leave experimental stage. Microsoft Edge is no exception. Even if users spend most of their time interacting with the web content itself (which the browser can’t really do anything about) they also interact with menus, options, settings pages and more that are part of Microsoft Edge. These parts of the browser need to be accessible to you whether you use a mouse or a keyboard, or whether you rely on a screen reader to interact with your computer. The Developer Tools are part of the browser, and [ more… ]