Hi Brian: The problem is that this portion of the document can mislead people into thinking WebKit a11y is working and complete:
"WebKit supports the AT-SPI accessibility layer since version 1.0.x. The GNOME accessibility team are working hard with WebKit team to ensure WebKit is accessible when GNOME 2.28 is released." The clarification I provided hopefully would prevent any confusion. I'm not really the one to make the call about whether WebKit integrates or not, and will forward this on to my peers in the APO who can help make that call. Will Brian Cameron wrote: > > Willie: > >> If there is a chance, some clarification should be made about the a11y >> statement. The WebKit team and GNOME teams are working hard to provide >> fundamental a11y support for WebKit, but there is a lot of work to do. >> See: >> >> http://mail.gnome.org/archives/desktop-devel-list/2009-July/msg00066.html >> >> Furthermore, the first phase, which is what is being worked on now, does >> not include ARIA support: http://www.w3.org/WAI/intro/aria >> >> Currently, the WebKit a11y work is still on-going, and lack of resources >> from the WebKit side is putting WebKit a11y support at risk for 2.28.0. > > What further clarification is needed aside from the information you > provide above? Obviously there will be a negative impact to users who > need a11y features if we integrate WebKit before these issues are > addressed. > > Are you suggesting that WebKit not integrate in Solaris until it is > more fully accessible? If so, what do you recommend be done instead? > > Brian
