| Product | Version | Compliance |
|---|---|---|
| ArcGIS Desktop | 9.3 | Compliant with minor issues |
| ArcGIS Engine | 9.3 | Compliant with minor issues |
| ArcGIS Server | 9.3 | Compliant with minor issues |
| ArcInfo | 9.3 | Compliant with minor issues |
| ArcInfo | 9 | Compliant with minor issues |
| ArcInfo | 8.1, 8.1.2, 8.2, 8.3 | Compliant with minor issues |
| ArcEditor | 9.3 | Compliant with minor issues |
| ArcEditor | 9 | Compliant with minor issues |
| ArcEditor | 8.1, 8.1.2, 8.2, 8.3 | Compliant with minor issues |
| ArcView | 9.3 | Compliant with minor issues |
| ArcView | 9 | Compliant with minor issues |
| ArcView | 8.1, 8.1.2, 8.2, 8.3 | Compliant with minor issues |
| ArcView | 3.3 | Not compliant |
| ArcView | 3.2x | Will not test |
| ArcIMS | 9.3 | Compliant with minor issues |
| ArcIMS | 4.0, 4.0.1, 9.0 | Compliant with minor issues |
| ArcIMS | 3.1 | Compliant with minor issues |
| ArcPad | 8.x | Compliant with minor issues |
| ArcPad Application Builder | 7.x | Compliant with minor issues |
| ArcReader | 9.3 | Compliant with minor issues |
| ArcReader | 8.2, 8.3 | Compliant with minor issues |
| ArcSDE | 9.3 | Compliant with minor issues |
| ArcWeb ServicesDisclaimer In the context of developing geographic information system (GIS) applications, developers can programmatically include any accessibility features needed in order to interface with commercially available assistive technology. However, ESRI has not researched the current availability or feasibility of such technology, in part because we cannot know precisely the needs of your agency. |
1, 2, 2006, 2006.1 | Will not test, disclaimerDisclaimer In the context of developing geographic information system (GIS) applications, developers can programmatically include any accessibility features needed in order to interface with commercially available assistive technology. However, ESRI has not researched the current availability or feasibility of such technology, in part because we cannot know precisely the needs of your agency. |
| ArcExplorer—Java Edition | 4.0.1 | Compliant with minor issues |
| MapObjects—Windows Edition | 2.1, 2.2 | Compliant |
| MapObjects—Java Edition | 1.0, 1.0.1, 2.0 | Compliant |
ESRI has a process for testing and qualifying all its software offerings. Our test criteria are designed around the technical standards for software applications and Web-based Internet information and applications as set forth in §1194.21 and §1194.22 of Section 508 Standards.
Our goal is to ensure we provide Section 508-compliant release versions (when applicable) for all ESRI software available on or after June 25, 2001. All software (ArcInfo, ArcEditor, ArcView, etc.) has a series of releases, and each individual release has its own compliance category.
Note: Older software versions (i.e., versions that are no longer being offered for sale as of June 25, 2001) will not be tested for compliance.
Select from the list above for up-to-date compliance information. ESRI has classified each of its software releases into the following five categories:
| Category | Description |
|---|---|
| Compliant | The software release fully meets ESRI's standard of compliance. May have a prerequisite patch for compliance. |
| Compliant with minor issues | The software release meets ESRI's standard of compliance with some disclosed exceptions that constitute minor issues. |
| Not Compliant | The software release does not meet ESRI's standard of compliance. |
| Testing yet to be completed | Testing for the software release is not yet complete or has not been started. Software release will be tested. |
| Will not test | The software release will not be tested for compliance. |
