Accessibility/Comparisons: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
 
 
(8 intermediate revisions by 2 users not shown)
Line 1: Line 1:
== Gecko's Accessibility Interfaces are Cross-Platform ==
At the heart of Gecko's [http://www.mozilla.org/access/architecture accessibility architecture] are the cross-platform [http://landfill.mozilla.org/mxr-test/mozilla/source/accessible/public/nsIAccessible.idl nsIAccessible] interfaces.  
At the heart of Gecko's accessibility architecture are the cross-platform nsIAccessibility interfaces. The goal is that these be the sum of all accessible toolkits on the various platforms.


=== Different implementation for each platform ===
The goal is that these interfaces be a cross-platform representation of the abilities of the OS-specific implementations.
However, in the real world, operating systems work differently. A developer that needs to make an application accessible has to do it in different ways, depending on the OS of choice.
 
=== Mac implementation in progress ===
Right now we're working to [[Mac:Accessibility|make Gecko accessible on Mac]]. We have colored these tables to make it easier to see what the Mac APIs lack and what they support. If you're a programmer, and want to know more about Universal Access, there's a [[Mac:Accessibility/UniversalAccess|short introduction and quick reference]], and even a [[Accessibility/Comparisons:ATK_To_UA|discussion which compares ATK interfaces and UA functionality]] here at the wiki.


=== Comparing the accessibility architectures ===
=== Comparing the accessibility architectures ===
When implementating support for a new system in our cross-platform accessibility architecture, we need to make sure it fits up to the standard of the other implementations.
When implementing support for a new system in our cross-platform accessibility architecture we need to make sure that it measures up to the standard of the other implementations.


One way to do this, is try to find out their pecularities using comparison tables. Below you'll find such comparisons, showing what each accessibility implementation does and does not support.
Below you'll find comparisons of the API features of every platform, side by side.


* [[Accessibility/Comparisons:Roles|Comparison of roles]]
* [[Accessibility/Comparisons:Roles|Comparison of roles]]
* [[Accessibility/Comparisons:States|Comparison of states]]
* [[Accessibility/Comparisons:States|Comparison of states]]
* [[Accessibility/Comparisons:Events|Comparison of events/notifications]]
* [[Accessibility/Comparisons:Events|Comparison of events/notifications]]
* [[Accessibility/Comparisons:ATK_To_UA|Discussion which compares ATK interfaces to UA]]

Latest revision as of 14:29, 13 June 2006

At the heart of Gecko's accessibility architecture are the cross-platform nsIAccessible interfaces.

The goal is that these interfaces be a cross-platform representation of the abilities of the OS-specific implementations.

Mac implementation in progress

Right now we're working to make Gecko accessible on Mac. We have colored these tables to make it easier to see what the Mac APIs lack and what they support. If you're a programmer, and want to know more about Universal Access, there's a short introduction and quick reference, and even a discussion which compares ATK interfaces and UA functionality here at the wiki.

Comparing the accessibility architectures

When implementing support for a new system in our cross-platform accessibility architecture we need to make sure that it measures up to the standard of the other implementations.

Below you'll find comparisons of the API features of every platform, side by side.

Retrieved from "https://wiki.allizom.org/index.php?title=Accessibility/Comparisons&oldid=27734"