This item has been reassigned from the project Gnash - The GNU Flash player bugs tracker to your tracker.

The original report is still available at bugs #18194

Following are the information included in the original report:

[field #0]                  Item ID: 18194
[field #1]                 Group ID: 8191
[field #2]              Open/Closed: Open
[field #3]                 Severity: 3 - Normal
[field #4]                  Privacy: Public
[field #6]                 Category: gui
[field #7]             Submitted by: hawkeslewis
[field #8]              Assigned to: None
[field #9]             Submitted on: Saturday 11/04/2006 at 11:55
[field #10]                  Summary: Expose Flash content to assistive technology via common accessibility frameworks
[field #11]      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:

http://www.adobe.com/resources/accessibility/flash8/

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

http://www.jkrowling.com/

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

http://www.rnib.org.uk/xpedio/groups/public/documents/publicwebsite/public_jkrowling.hcsp

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

http://www-306.ibm.com/able/resources/firefox.html

http://www.mozilla.org/access/windows/at-apis#knowndif

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:

http://tinyurl.com/y68flt

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.

http://developer.gnome.org/projects/gap/

http://accessibility.kde.org/developer/qtconnection.php

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

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msaa/msaastart_9w2t.asp

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

http://developer.apple.com/ue/accessibility/

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

http://diveintomark.org/archives/2006/10/13/mozilla-accessibility-summit#mac

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

http://www.microsoft.com/enable/at/uiadeveloper.aspx

[field #13]               Item Group: None
[field #14]                   Status: Invalid
[field #15]        Component Version: None
[field #16]         Operating System: None
[field #17]          Reproducibility: None
[field #18]               Size (loc): None
[field #19]            Fixed Release: None
[field #20]          Planned Release: None
[field #21]                   Effort: 0.00
[field #25]                 Priority: 5 - Normal
[field #28]         Percent Complete: 0%
[field #30]                  Release: None
[field #55]     Custom Select Box #1: None
[field #56]     Custom Select Box #2: None
[field #57]     Custom Select Box #3: None
[field #58]     Custom Select Box #4: None
[field #59]     Custom Select Box #5: None
[field #60]     Custom Select Box #6: None
[field #61]     Custom Select Box #7: None
[field #62]     Custom Select Box #8: None
[field #63]     Custom Select Box #9: None
[field #64]    Custom Select Box #10: None

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:

http://www.adobe.com/resources/accessibility/flash8/

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

http://www.jkrowling.com/

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

http://www.rnib.org.uk/xpedio/groups/public/documents/publicwebsite/public_jkrowling.hcsp

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

http://www-306.ibm.com/able/resources/firefox.html

http://www.mozilla.org/access/windows/at-apis#knowndif

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:

http://tinyurl.com/y68flt

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.

http://developer.gnome.org/projects/gap/

http://accessibility.kde.org/developer/qtconnection.php

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

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msaa/msaastart_9w2t.asp

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

http://developer.apple.com/ue/accessibility/

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

http://diveintomark.org/archives/2006/10/13/mozilla-accessibility-summit#mac

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

http://www.microsoft.com/enable/at/uiadeveloper.aspx