bugGnash - The GNU Flash player - Bugs: bug #18194, Reassigned to another tracker...


bug #18194: Reassigned to another tracker [was: Expose Flash content to assistive technology via common accessibility frameworks]

Submitter:  Benjamin Hawkes-Lewis <hawkeslewis>
Submitted:  Sat 04 Nov 2006 10:55:45 AM UTC
Category:  gui Severity:  3 - Normal
Release:  None Status:  Invalid
Privacy:  Public Assigned to:  None
Open/Closed:  Closed
* Mandatory Fields

Add a New Comment Rich Markup

Sat 04 Nov 2006 04:06:02 PM UTC, comment #2: 


Please, do not post any new comments to this item.

Sandro Santilli <strk>
Group Member
Sat 04 Nov 2006 04:06:02 PM UTC, comment #1: 

moved to support tracker (hopefully)

Sandro Santilli <strk>
Group Member
Sat 04 Nov 2006 10:55:45 AM UTC, original submission:  


As early as Flash Player 6, Adobe began introducing accessibility features into Flash via the MSAA (Microsoft Active Accessibility) framework. Flash Player 8 and higher give assistive technology users access to Flash content on the web, but this only happens when using Internet Explorer:


A much publicized example of "accessible" Flash web content can be found at the home page of J. K. Rowling:


Here's a case study by RNIB (the Royal National Institute for the Blind in the UK):


Yet the Gecko engine used in Firefox arguably has superior MSAA integration for non-Flash web content:



Given the excellent level of support for Firefox from screen readers like GW-Micro Window-Eyes, the failure of the Flash plugin to expose objects to MSAA when called from Firefox has been raised as a matter of great concern on the mozilla.dev.accessibility list:


Implementing the Accessibility classes is already on the Gnash TODO list. But it is crucial that Flash objects using that class be exposed correctly to the key accessibility frameworks, especially:

1) AT-SPI: the Gnome accessibility framework. This should give better access to Flash content to Linux assistive technology users, including those with motor impairments using online keyboards like GOK, and those with visual impairments using Linux screen readers such as Gnopernicus, Orca, and LSR. Supporting AT-SPI should allow integration with KDE assistive technologies (such as KTTS) too, thanks to the AT-SPI to QT Accessibility bridge planned for KDE 4.



2) MSAA: the framework currently used in Windows and Mozilla's Windows builds, and by Adobe Flash Player.


3) Maybe Apple's Accessibility APIs for Mac OS X?


HÃ¥kan Waara is working on Mozilla support for VoiceOver (the screen reader bundled with OS X) for Firefox 3:


4) Maybe UI Automation: the new accessibility framework in Windows Vista?


Benjamin Hawkes-Lewis <hawkeslewis>


(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:

No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


CC list is empty


There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

Only logged-in users can vote.


Follow 2 latest changes.

Date Changed by Updated Field Previous Value => Replaced by
2006-11-04 strk StatusNone Invalid
    Reassign ItemGnash - The GNU Flash player, bug #18194 Gnash - The GNU Flash player, sr #105660

Back to the top

Powered by Savane 3.13-599c.
Corresponding source code