Yeah, there&#x27;s a near-search timeout involved in order to allow multiple keystrokes to be used, and it was set a little high as the default (it&#x27;s configurable as a property).  I&#x27;ve bumped the default from 500ms down to 200ms and that seems to be a better fit.<p>Accessibility is so-so.  We use text blocks for any labels, grid headers, grid cells, etc., but I still need to audit the UI completely with the ADA helper tools that are available.  As for the combo box, the answer there is &quot;I don&#x27;t know&quot; until I complete that audit, but it probably won&#x27;t be as usable as our other combo box options that are actual edit controls (you can select text, etc.).  The reason for the combo box that you see here is touch environments, specifically those that automatically pop up a virtual keyboard.  It&#x27;s used for situations where you don&#x27;t want the keyboard constantly popping up, but you need a button-style drop-down list control.<p>The problem with the current HTML incarnation, and why stuff like the above is done, is that it&#x27;s just not flexible enough to handle real-world applications (equivalent to desktop apps) without some serious compromises on controls, or by subverting the HTML semantics.  We chose the latter.  It&#x27;s the only way to do things like virtual list controls (the combo box has a virtual list control associated with it).  If the browser offered a way to define semantics for custom controls, it would help immensely.