W3C home > Mailing lists > Public > public-html@w3.org > September 2012

RE: internet explorer and UI automation

From: Adrian Bateman <adrianba@microsoft.com>
Date: Tue, 11 Sep 2012 13:46:44 +0000
To: Steve Faulkner <faulkner.steve@gmail.com>
CC: Cynthia Shelly <cyns@microsoft.com>, HTML Accessibility Task Force <public-html-a11y@w3.org>, Richard Schwerdtfeger <schwer@us.ibm.com>, HTMLWG WG <public-html@w3.org>
Message-ID: <0a4d4f88f8d84f3d8675ada6fd106de3@BL2PR03MB604.namprd03.prod.outlook.com>
Hi Steve,

Thanks for the feedback. In future, the most direct route to provide
feedback to the IE Engineering team is to file an issue through Microsoft
Connect (https://connect.microsoft.com/IE). This funnels the issue
through our feedback systems to ensure that it doesn't get lost.

We don't have any additional information to share at the moment.

Thanks again,


-----Original Message-----
From: Steve Faulkner [mailto:faulkner.steve@gmail.com] 
Sent: 10 September 2012 22:29
Cc: Cynthia Shelly; Adrian Bateman; HTML Accessibility Task Force; Richard Schwerdtfeger
Subject: internet explorer and UI automation

Hi all,

I have recently updated html5 accessibility.com [1]

As part of that update I looked at accessibility support
implementation in IE10 of the various new HTML5 elements and

One of the things that struck me was IE's continuing lack of exposure
(as compared to other browsers such as Firefox on windows and Safari
on Mac) of section , grouping and text level semantic elements via an
accessibility API (UI automation in IE's case). Note this is not just
about new HTML5 structures, for example IE is the only browser, that
while supporting the expression of accessibility information via
accessibility APIs, does not expose the semantics of the h1 to h6
elements via an accessibility API.

I thought that this was due to UI automations inability to express
such structures, but upon further reading of the UI automation it
appears possible (from my naive reading of the documenatation) for
example the semantics could be expressed via the use of properties of
the text control pattern [2] or by creating a new custom control
pattern(s) or by use of the ability to express ARIA
role/state/property information via UI automation [4]

I would be interested to hear from the IE team why such structures are
not exposed via UI automation as I think this would provide a robust
method for assistive tech to access such semantic information about
such HTML elements without having to resort to interrogating the HTML

[1] http://www.html5accessibility.com/
[2] http://msdn.microsoft.com/en-us/library/dd320536(v=vs.85).aspx
[3] http://msdn.microsoft.com/en-us/library/dd757493(v=vs.85).aspx
[4] http://msdn.microsoft.com/en-us/library/ie/gg701984(v=vs.85).aspx

with regards

Steve Faulkner
Technical Director - TPG

www.paciellogroup.com | www.HTML5accessibility.com |
HTML5: Techniques for providing useful text alternatives -
Web Accessibility Toolbar - www.paciellogroup.com/resources/wat-ie-about.html
Received on Tuesday, 11 September 2012 13:48:32 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:16:27 UTC