ACTION-43: Revisit Christophe's comments on 1.4.4 Resize Text from the WCAG 19 July survey

The consequence of this is: when a platform supports text enlargement at 200%, then neither web content authors nor browsers need to provide a mechanism for text enlargement or zoom in order for content to meet SC 1.4.4. But wouldn't it be necessary to set text size independent of the current platform text enlargement? 200% at the platform level may be a good approximation of the desired size for some documents or web pages, but not for others.

Update: After writing the above, I set text size in my Windows 7 computer to 200% and checked how this affected UIs and content in a number of applications. I found the following effects:
(1) text in UI (menus etc) and content are the same size as before (e.g. Java-based programmers editor JEdit) - this is a clear failure;
(2) text in UI is 200% and sharp, while content is the same size as before (e.g. Firefox 12, SeaMonkey 2.11) - so users next UI text resizing or zooming even after setting text size on the platform;
(3) both text in UI and in content are at 200% but unsharp (e.g. Opera 11.64, Adobe Reader X, Apache OpenOffice.org 3.4, LibreOffice 3.5.4.2, Chrome 20, Safari 5.1.7, NetBeans 6.8; note: in Skype 4.2.0.187 there is overlap in at least two parts of the UI) - this meets the SC if slightly unsharp text is OK;
(4) both text in UI and in content are at 200% and sharp (e.g. Internet Explorer 8; Notepad; Microsoft Word 2012, except for icons on the ribbon; Eclipse Indigo Service Release 2, including the help, but not the welcome screen) - this meets the SC.