The best idea I have so far is this: Win32 and classic hand-coded web user interfaces used to leak implementation details, including class names and IDs (numeric control IDs in Win32 dialogs, string IDs for HTML elements). This wasn't done for the sake of accessibility, but developers of screen reader scripts/add-ons made the most of these things to work around the app developer's indifference toward accessibility, especially for Win32.