platform conformance

 E Hansen suggestions/edits 4 April 2013, 11:57 Components of UAAG 2.0
Conformance Claims

          Each component is required unless explicitly cited as “optional.”

1.    Claimant name and affiliation.

2.    Claimant contact information.

3.    Date of the claim.

4.    Conformance level (level A, AA, or AA).

5.    User agent information:

a.    Name and manufacturer

b.    Version number or version range,

c.    Required patches or updates, human language of the user interface or
documentation).

d.    Include any required configuration changes to the user agent (e.g.
ignore author foreground/background color)

e.    Required plugins or extensions with versions (e.g., mouseless
browsing)

6.    Platform: Describe the *platform* (software and hardware) on which
the user agent relies for conformance.

a.    Platform hardware

1.    Key hardware components or limitations (e.g., minimum screen size:
2-inch diagonal, audio output device [What about input devices]).

2.    Other information about the platform hardware (e.g., name and
manufacturer and version number of the hardware components)

b. Platform software (mandatory only if there is platform software)

1. Name and manufacturer

2. Version of key software components (e.g., operating system, other
software environment)

3. Any required configuration changes to the platform (e.g., turn on sticky
keys)

4. Operating system(s) (e.g., Windows 8, Android 4.0+, iOS 5.0+, GNOME 2)

5. Other software environment (Java SE 7+, Eclipse 3.7+)
"Host" web browser - relevant when the conforming user agent is web-based
(e.g., Firefox 14+, Safari 7.0+)

7. Range of web content technologies rendered

a. Web content technologies rendered. The claimant must identify all web
content technologies the rendering of which is relied upon to meet the
claimed conformance level. By including a web content technology, the claimant
is asserting that the user agent meets the requirements of UAAG 2.0 (at the
claimed level) during the rendering of web content using that web content
technology.

 Note: Web content technologies may be a combination of constituent web
content technologies. For example, an image technology (e.g. PNG) might be
listed together with a markup technology (e.g. HTML) since web content in
the markup technology[egh1] <#_msocom_1>  is used make web content in the
image technology.

b. Content technologies not relied upon (optional).  The claimant may
optionally identify one or more web content technologies that are not
relied upon to meet the claimed conformance level. If the claimant chooses
to exercise this option and to cite one or more technologies not relied on,
the description must carefully distinguish between (a) technologies that
are supported and (b) technologies that are not supported. [I did not want
to rule out the possibility that the user agent may support a web
technology yet not rely on it. I am not positive yet that this is a real
possibility.]

7.    Declarations: Provide, for each success criterion, a declaration of
either (a) whether or not the success criterion has been satisfied or (b) a
declaration that the success criterion is not applicable and a rationale
for why not. Refer to Note ABC for further information on determining which
success criteria may not be applicable.

8.    Platform: Include the name, manufacturer, and version
information of operating
system <http://www.w3.org/WAI/UA/UAAG20/#def-operating-system>, operating
environment, and/or application on which the user agent is being hosted.
(Example platforms <http://www.w3.org/WAI/UA/UAAG20/#def-platform> could
include Microsoft Windows an operating system, Gnome and the Java Runtime
Environment as operating environments, Eclipse as a hosting IDE, Mozilla
Firefox for OS X as a hosting web browser, and Samsung's version of Google
Android for the Galaxy S III as a combination of customized operating
system and hardware. All would include specific version numbers or ranges.)
Include any required configuration changes to the platform (e.g.a web-based
browser will conform when run on Firefox with the Mouseless Browsing
extension) and any relevant hardware limitations (e.g. minimum screen size,
audio output).


 ------------------------------

 [egh1] <#_msoanchor_1>Not sure I understand this. It seems to blur the
division between platform and  web technologies rendered. I find this
somewhat confusing.


-- 
Jim Allan, Accessibility Coordinator & Webmaster
Texas School for the Blind and Visually Impaired
1100 W. 45th St., Austin, Texas 78756
voice 512.206.9315    fax: 512.206.9264  http://www.tsbvi.edu/
"We shape our tools and thereafter our tools shape us." McLuhan, 1964