Full UAAG 2.0 Conformance

from email

A user agent conforms to UAAG20 at A, AA or AAA level when it meets the all of the SCs appropriate for the claimed level of conformance. The UA may meet the appropriate SCs wholly on its own or must list extensions necessary to meet specified SCs that the UA cannot meet alone.

Summary

Details

Partial UAAG 2.0 Conformance

from email

This conformance option may be selected when a user agent is unable to meet one or more success criteria because of intrinsic limitations of the platform. The SC marked with Not Applicable (NA) conformance should explain what platform features are missing.

User-Agent A conforms to the following Success Criteria:
all met SC are listed.

The following SC are listed as NA using the codes below:
all NA SC are listed

NA:* Not Applicable Codes: (Level A, AA, or AAA)

*NA-Input:* not applicable due to a constrained input set (e.g. an application that reads flight data in XML format from a corporate server, or a help system that only displays HTML files included with the product)

*NA-Platform:* not applicable due constraints of the platform (e.g. color handling when the browser is run on a monochrome device, audio handling on a silent device, video handling on a interactive voice response browser, or interprocess communication on an operating system that does not support multitasking). The conformance should explain what platform features are missing.

*NA-Output:* not applicable due to intentionally limited output modalities (e.g. video handling in a browser that only does audio output even though the platform might support video)

Summary

Details

Not Compliant Code

from email

The following SC are listed as Not Compliant using the following scheme:
All Non-compliant SC are listed

NC:* Not Compliant codes: (Level A, AA, or AAA)

*NC-Potential:* not compliant but in theory a third party could make it compliant using documented and supported techniques (e.g. the product's extension architecture readily allows adding the required feature; this is also allowed if the source is made available and the claimant believes it could be modified to add compliance with less than one person-week of effort, thus giving incentive for open source

*NC-Unsupported:* may be compliant but not using documented and supported techniques

*NC-Impossible:* not compliant even with undocumented and unsupported techniques

Summary

Details

Extension or Plug-in

from email

If the following two conditions are met then it is an extension or plug-in:

It is launched by, or extends the functionality of a platform-based application, and
Post-launch user interaction is included in, or is within the bounds of the platform-based application

This includes most extensions and plugins (e.g. media players). It excludes AT, as they are standalone applications separate from the browser (rule 2 above). It excludes web-based application plugins (see the definition below).

UAAG 2.0 Conformance for Extension (Level A, AA, or AAA):

This option may be used for extension or plug-in with very limited functionality. Conformance for an extension or plugin can be claimed for specific SCs and the SCs related to preference settings, toolbar settings, documentation, and programmatic access.

The conformance claim must list all browsers and versions with which the extension operates.

The level of conformance (A, AA, or AAA) is determined as above except that: (1) for any "no" answers, the extension (plug-in, etc.) must not prevent the success criteria from being met by another user agent extension as part of a complete user agent system and (2) the user agent extension (plug-in, etc.) must meet any requirements applying to all functionality (e.g. to be resizable, to provide documentation, etc.).

Note: User agent Extensions would not be able to meet conformance if they prevent additional user agent components from meeting the failed success criteria (e.g., for security reasons).

NA-Component: not applicable to the limited functionality provided by this user agent component, plug-in, or extension (e.g. SC relating to rendering content would not apply to a browser extension that adds additional menu commands but does not itself render any content)

Example:

A "mouseless browsing" extension allows the following listed browsers (UA1, UA2) to meet UAAG success criterion 2.3.3 ("Direct activation of Enabled Elements: The user can move directly to and activate any enabled element in rendered content."). Additionally we meet these SCs related to user interface components (Guideline 2.1 2.3.4, 2.7.1, 2.7.1, 2.8.1, 3.3.1, 3.3.2). All other SC are rated NA-Extension.

Summary

Details