Web Technology Purchasing Requirements

Evaluating Accessibility of Products

Accessibility to people with disabilities is a required feature of a purchased product. Accessibility of a product will be evaluated based on responses to the Accessibility Requirements Checklist, given below, that is included as part of the RFP of the purchase. Products that meet the accessibility requirements or have a commitment to meet both the required and desired accessibility features will be given priority over proposals that do not meet the requirements or do not state an interest to meet the requirements in future releases of the product or service. If your products currently do not meet the accessibility requirements, you are still encouraged to submit a proposal if you state a commitment and schedule to include the requirements in future releases.

These requirements are based on the United States Federal Section 508 Information Technology Accessibility Standards and W3C Web Content Accessibility Guidelines 1.0 Double-A web accessibility requirements.

The following are additional resources that are helpful for evaluating accessibility of web resources:

¹Priority

Priority identifies a required feature from a feature that is highly desired.

D: Desirable feature
R: Required feature

²Response Code

The following table of codes must be used in responding to this RFP:

A: Standard
B: Requires non-code modification
C: Requires code modification
D: Avail. In Release xx.xx expected mm/yyyy
E: Can't be met

³Comments

Comments should be used provide more detailed description of accessibility features for the each requirement. For example first version feature appeared, testing with people with disabilities, participaiton in accessibility standards groups, and etc..

Web Technologies Purchasing Requirements Checklist
Ref	Description	Priority¹
Standards
S.1	Use Technologies that Support Accessibility Resources are created and designed using `HTML`, `xhtml`, `css`, `mathml`, `SMIL`, `SVG` and other open standards with features to support accessibility by people with disabilities. The W3C Web Content Accessibility Guidelines 2.0 provides the features that should be part of an accesible markup language. IITAA 1.0 1.1 Use valid, standard web programming code. 1.2 Use appropriate markup to convey document structure. 15.1 Provide natively accessible downloadable documents whenever possible. Section 508 None WCAG 2.0 None WCAG 1.0 11.1 Use W3C technologies when they are available and appropriate for a task and use the latest versions when supported. (Priority 2) 11.2 Avoid deprecated features of W3C technologies. (Priority 2) 11.3 Provide information so that users may receive documents according to their preferences (e.g., language, content type, etc.)(Priority 3)	R
S.2	Avoid Technologies with Poor Accessibility Support Adobe Flash and other proprietary web development languages that have limited accessibility features are not used for primary content and if included are only included as equivalents to resources that are accessible. The primary interface is the accessible interface and non-accessible version(s) can be selected by user action or configuration. IITAA 1.0 1.1 Use valid, standard web programming code. 1.2 Use appropriate markup to convey document structure. 15.1 Provide natively accessible downloadable documents whenever possible. 15.2 If a downloadable document cannot be made natively accessible, provide an accessible alternative that includes the same content and functionality. 18.1 Use separate accessible versions only as a last resort. Section 508 1194.22 (m) When a web page requires that an applet, plug-in or other application be present on the client system to interpret page content, the page must provide a link to a plug-in or applet that complies with 1194.21(a) through (l). WCAG 2.0 1.2.8 Full Text Alternative (Level AAA) WCAG 1.0 11.1 Use W3C technologies when they are available and appropriate for a task and use the latest versions when supported. (Priority 2) 11.2 Avoid deprecated features of W3C technologies. (Priority 2) 11.3 Provide information so that users may receive documents according to their preferences (e.g., language, content type, etc.)(Priority 3) 11.4 If, after best efforts, you cannot create an accessible page, provide a link to an alternative page that uses W3C technologies, is accessible, has equivalent information (or functionality), and is updated as often as the inaccessible (original) page. (Priority 1)	R
S.3	Content Language The default language of the resource is included in the markup. IITAA 1.0 2.3 Identify the language of text. Section 508 None WCAG 2.0 3.1.1 Language of Page (Level A) WCAG 1.0 4.3 Identify the primary natural language of a document.(Priority 3)	D
S.4	Valid Markup Resources validate to specifications to improve interoperability, examples include HTML, xhtml, CSS, SMIL, SVG and MathML IITAA 1.0 1.1 Use valid, standard web programming code. Section 508 None WCAG 2.0 4.1.1 Parsing (Level A) WCAG 1.0 3.2 Create documents that validate to published formal grammars. (Priority 2)	D
HTML Navigation
N.1	Unique Titles Each resource in a website has a unique title that is easily identifable by assistive technoogies, for HTML this means using the `title` and `h1` elements. Web applications must update the title information to reflect the current state and changes in task of the web application. IITAA 1.0 1.3 Provide meaningful page titles. 9.2 Provide a means of skipping past repetitive navigation links. Section 508 1194.22d A method shall be provided that permits users to skip repetitive navigation links. WCAG 2.0 2.4.2 Page Titled (Level A) 3.2.3 Consistent Navigation (Level AA) 3.2.4 Consistent Identification (Level AA) WCAG 1.0 3.5 Use header elements to convey document structure and use them according to specification. (Priority 2) 13.4 Use navigation mechanisms in a consistent manner.(Priority 2)	R
N.2	Headings All major/minor topics have section headers, for HTML this means using properly nested `h2-h6` elements within the web page. The section heading text provides useful orientation information to the content and features on the page. Web applications should update headers to reflect the current state and changes in content and task. Note: For HTML heading markup should not be used to only stylize text and the heading `h1` is reserved for titling the resource. IITAA 1.0 1.2 Use appropriate markup to convey document structure. 1.3 Provide meaningful page titles. 1.4 Use headings to introduce sections and sub-sections, and use them in the correct order. 9.2 Provide a means of skipping past repetitive navigation links. Section 508 1194.22d A method shall be provided that permits users to skip repetitive navigation links. WCAG 2.0 2.4.1 Bypass Blocks (Level A) 2.4.6 Headings and Labels (Level AA) 2.4.8 Location (Level AAA) 2.4.10 Section Headings (Level AAA) 3.2.3 Consistent Navigation (Level AA) WCAG 1.0 3.5 Use header elements to convey document structure and use them according to specification. (Priority 2) 13.4 Use navigation mechanisms in a consistent manner.(Priority 2) 13.5 Provide navigation bars to highlight and give access to the navigation mechanism. (Priority 3) 13.6 Group related links, identify the group (for user agents), and, until user agents do so, provide a way to bypass the group.(Priority 3)	R
N.3	Link Text Link text is descriptive of the target of the link. The same link text is not used to point to different URIs and references to the same URI use the same link text. Note: Common link problems include "click here", "more" and other link text that assumes content of the link from the surrounding content. IITAA 1.0 9.1 Make sure that links are understandable out of context. 9.2 Provide a means of skipping past repetitive navigation links. 9.3 Avoid using small links. 9.4 Ensure that same-page links move keyboard focus as well as screen focus. Section 508 None WCAG 2.0 2.4.4 Link Purpose (In Context) (Level A) 2.4.9 Link Purpose (Link Only) (Level AAA) WCAG 1.0 13.1 Clearly identify the target of each link. (Priority 2)	R
N.4	Image Maps HTML image maps (client and server side) have redundant text links, since graphical browsers do not provide a means to render `alt` text for `area` element and server side image maps do not provide the browser with any link information. Redundent text links can be styled to the users perceptual needs. IITAA 1.0 5.1 Provide alternate text for each area in client-side image maps. 5.2 Use client-side image maps instead of server-side image maps unless areas cannot be defined with available shapes. Section 508 1194.22 (e) Redundant text links shall be provided for each active region of a server-side image map. 1194.22 (f) Client-side image maps shall be provided instead of server-side image maps except where the regions cannot be defined with an available geometric shape. WCAG 2.0 1.1.1 Non-text Content (Level A) 1.4.3 Contrast (Minimum) (Level AA) 1.4.4 Resize Text (Level AA) 1.4.5 Images of Text (Level AA) 1.4.6 Images of Text (Level AAA) WCAG 1.0 1.2 Provide redundant text links for each active region of a server-side image map. (Priority 1) 1.5 Until user agents render text equivalents for client-side image map links, provide redundant text links for each active region of a client-side image map. (Priority 3) 9.1 Provide client-side image maps instead of server-side image maps except where the regions cannot be defined with an available geometric shape. (Priority 1)	R
N.5	Navigation Bars and Menus Navigation bars and menus within web resources use ul and `li` elements as markup for the list of options and provide a title for the navigation bar with an `h2`element or other header. Header may be hidden using CSS techniques. IITAA 1.0 1.4 Use headings to introduce sections and sub-sections, and use them in the correct order. 1.5 Use lists to identify series of related items, including navigation menus. Section 508 1194.22d A method shall be provided that permits users to skip repetitive navigation links. WCAG 2.0 1.3.1 Info and Relationships (Level A) 2.4.1 Bypass Blocks (Level A) 2.4.6 Headings and Labels (Level AA) 2.4.10 Section Headings (Level AAA) 3.2.3 Consistent Navigation (Level AA) 3.2.4 Consistent Identification (Level AA) WCAG 1.0 3.5 Use header elements to convey document structure and use them according to specification. (Priority 2) 12.3 Divide large blocks of information into more manageable groups where natural and appropriate. (Priority 2) 13.5 Provide navigation bars to highlight and give access to the navigation mechanism. (Priority 3)	R
N.6	Form Control Labels and Grouping All HTML form controls (`input`, `select`, `button` and`textarea` elements) have an effective label element associated with each control to identify the purpose of the form control in the resource, usually using the `label` element. Groups of related form controls must use headings or `fieldset` and `legend` elements to indicate the relationship of the controls within the group. IITAA 1.0 10.1 Provide labels or titles for all form fields. 10.2 Provide legends for groups of form fields. 10.3 Ensure that form fields are in a logical tab order. 10.4 Avoid placing non-focusable text between form fields. 10.5 Ensure that text in form fields can be enlarged. Section 508 1194.22 (e) Redundant text links shall be provided for each active region of a server-side image map. WCAG 2.0 1.3.1 Info and Relationships (Level A) 1.3.2 Meaningful Sequence (Level A) 2.4.6 Headings and Labels (Level AA) 2.4.10 Section Headings (Level AAA) 4.1.2 Name, Role, Value (Level A) WCAG 1.0 12.3 Divide large blocks of information into more manageable groups where natural and appropriate. (Priority 2) 12.4 Associate labels explicitly with their controls. And if you use applets and scripts (Priority 2) Yes No N/A 6.4 For scripts and applets, ensure that event handlers are input device-independent. (Priority 2)	R
N.7	Language Changes Changes in content language are indicated in markup using `lang` or `xml:lang` attributes. IITAA 1.0 2.3 Identify the language of text. Section 508 None WCAG 2.0 3.1.2 Language of Parts (Level AA) WCAG 1.0 4.1 Clearly identify changes in the natural language of a document's text and any text equivalents (e.g., captions). (Priority 1)	R
N.8	Data Tables Data tables use `caption` element to title the data table, `summary` attribute to provide a summary of why the table was included in the resources, `th` elements for indicating header cells, `th.id` attribute to uniquely identify each header cell and `td.headers` attributes indicate header cells associated with each data cell. The `axis` element maybe used to provide supplementary relationship information. IITAA 1.0 11.1 Identify a header cell for each column and row in simple data tables. 11.2 Identify relationships in complex data tables using id and headers attributes. 11.3 Provide summary attributes for data tables. Section 508 1194.22 (g) Row and column headers shall be identified for data tables. 1194.22 (h) Markup shall be used to associate data cells and header cells for data tables that have two or more logical levels of row or column headers. WCAG 2.0 1.3.1 Info and Relationships (Level A) WCAG 1.0 5.1 For data tables, identify row and column headers. (Priority 1) 5.2 For data tables that have two or more logical levels of row or column headers, use markup to associate data cells and header cells. (Priority 1) 5.5 Provide summaries for tables. (Priority 3)	R
N.9	Lists Lists of items are markup using unorder lists (`ul` element), order lists (`ol` element) or definition list (`dl` element). IITAA 1.0 1.5 Use lists to identify series of related items, including navigation menus. Section 508 None WCAG 2.0 1.3.1 Info and Relationships (Level A) 1.3.2 Meaningful Sequence (Level A) WCAG 1.0 3.1 When an appropriate markup language exists, use markup rather than images to convey information. (Priority 2) 3.3 Use style sheets to control layout and presentation. (Priority 2) 3.6 Mark up lists and list items properly. (Priority 2)	R
N.10	Linearization When table markup or CSS coding for spatial layout is removed, the document reading order makes sense and is still usable. IITAA 1.0 17.1 When using tables for layout, ensure that reading order is logical. 17.2 When using style sheets for layout, ensure that reading order is logical. 17.3 Avoid horizontal scrolling. Section 508 1194.22 (d) Documents shall be organized so they are readable without requiring an associated style sheet. WCAG 2.0 1.3.1 Info and Relationships (Level A) 1.3.2 Meaningful Sequence (Level A) WCAG 1.0 5.3 Do not use tables for layout unless the table makes sense when linearized. Otherwise, if the table does not make sense, provide an alternative equivalent (which may be a linearized version). (Priority 2) 5.4 If a table is used for layout, do not use any structural markup for the purpose of visual formatting.(Priority 2) 6.1 Organize documents so they may be read without style sheets. For example, when an HTML document is rendered without associated style sheets, it must still be possible to read the document. (Priority 1)	R
N.11	Frames Frames need to provide a descriptive title for each frame to understand the purpose of the frame within a web page using the `title` attribute. Frames used for client/server interaction or frames that do not contain viewable content and marked as `title='hidden'`. In general frames cause accessibility problems and should be avoided. IITAA 1.0 12.1 Provide concise, unique, and understandable titles for frames. 12.2 Avoid using hidden, empty, or non-essential frames. Section 508 1194.22 (i) Frames shall be titled with text that facilitates frame identification and navigation. WCAG 2.0 1.3.1 Info and Relationships (Level A) 1.3.2 Meaningful Sequence (Level A) 2.4.3 Focus Order (Level A) 3.2.3 Consistent Navigation (Level AA) 3.2.4 Consistent Identification (Level AA) WCAG 1.0 12.1 Title each frame to facilitate frame identification and navigation. (Priority 1) 12.2 Describe the purpose of frames and how frames relate to each other if it is not obvious by frame titles alone. And if you use forms (Priority 2) Yes No N/A (Priority 2)	R
HTML Text Equivalents
E.1	Provide Text Equivalents for Images Images within each web resource have text equivalents. Images are used for a variety of purposes within web resources, so the type of text equivalent is dependent on how the image is being used. Stylistic or Positioning Images The `alt` attribute should be set to null `alt="` Stylistic and positioning images should be moved to CSS to improve interoperability Logos and Supporting Images The `alt` attribute should be used to provide the name of the organization or provide short title for the image Images used as Links The `alt` attribute should be used to indicate the target of the link Informative Images The `alt` attribute should be used to give the image a short title to help people understand the content of the image A longer description, ideally as part of the resource narrative, describing the features of the image should be included. Charts and graphs should use data tables or list markup to provide numerical summaries and provide the data used to generate the chart. Math Equations Equations should also be available in MathML format. IITAA 1.0 4.1 Provide "alternate text" for all images. 4.2 Provide full descriptions for graphs, diagrams, and other meaningful images. 5.1 Provide alternate text for each area in client-side image maps. 5.2 Use client-side image maps instead of server-side image maps unless areas cannot be defined with available shapes. Section 508 1194.22 (a) A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content). WCAG 2.0 1.1.1 Non-text Content (Level A) 1.4.9 Images of Text (No Exception) (Level AAA) WCAG 1.0 1.1 Provide a text equivalent for every non-text element (e.g., via "alt", "longdesc", or in element content). This includes: images, graphical representations of text (including symbols), image map regions, animations (e.g., animated GIFs), applets and programmatic objects, ascii art, frames, scripts, images used as list bullets, spacers, graphical buttons, sounds (played with or without user interaction), stand-alone audio files, audio tracks of video, and video. (Priority 1) 1.2 Provide redundant text links for each active region of a server-side image map. (Priority 1)	R
E.2	Provide Equivalents for other Graphical or Programmatic Objects Other types of embedded media for graphics, audio or video objects have text descriptions so people with disabilities know what information they are not able to access, regardless of the accessibility of the object. This is important for reporting accessibility problems to content providers or requesting information be a provided in an accessible format. IITAA 1.0 14.1 Use accessible embedded objects whenever possible. 14.2 If an inaccessible object, applet, or plug-in must be used, provide an accessible alternative that includes the same content and functionality. Section 508 1194.22 (m) When a web page requires that an applet, plug-in or other application be present on the client system to interpret page content, the page must provide a link to a plug-in or applet that complies with 1194.21(a) through (l). WCAG 2.0 1.1.1 Non-text Content (Level A) 4.1.2 Name, Role, Value (Level A) WCAG 1.0 1.1 Provide a text equivalent for every non-text element (e.g., via "alt", "longdesc", or in element content). This includes: images, graphical representations of text (including symbols), image map regions, animations (e.g., animated GIFs), applets and programmatic objects, ascii art, frames, scripts, images used as list bullets, spacers, graphical buttons, sounds (played with or without user interaction), stand-alone audio files, audio tracks of video, and video. (Priority 1) 1.2 Provide redundant text links for each active region of a server-side image map. (Priority 1)	R
HTML Styling
Y.1	Text Styling IITAA 1.0 None Section 508 WCAG 2.0 .. (Level ) .. (Level ) WCAG 1.0 . (Priority )	D
Y.2	Link Styling IITAA 1.0 None Section 508 WCAG 2.0 .. (Level ) .. (Level ) WCAG 1.0 . (Priority )	D
Y.2	Color Coding Color cannot be the only means to convey information. When color styling is changed or the content is rendered in black and white the content of the page can still be understood. IITAA 1.0 None Section 508 WCAG 2.0 .. (Level ) .. (Level ) WCAG 1.0 . (Priority )	R
Y.3	Color Coding IITAA 1.0 None Section 508 WCAG 2.0 .. (Level ) .. (Level ) WCAG 1.0 . (Priority )	R
Y.5	Styling Text Images are not used to stylize text, except in logos and other branding images. IITAA 1.0 None Section 508 WCAG 2.0 .. (Level ) .. (Level ) WCAG 1.0 . (Priority )	R
Y.6	Inline Styling All content is styled through Style sheets, no in-line styling elements of content (i.e. B, I, FONT, CENTER, BLINK, MARQUEE, ...). IITAA 1.0 None Section 508 WCAG 2.0 .. (Level ) .. (Level ) WCAG 1.0 . (Priority )	D
Y.7	Focus Styling Dynamic pseudo-classes like `:hover`, have corresponding `:focus` dynamic pseudo-class selectors. IITAA 1.0 None Section 508 WCAG 2.0 .. (Level ) .. (Level ) WCAG 1.0 . (Priority )	D
Y.2	Layout Tables CSS should be used in place of tables for the layout of content on a web page. When tables are nested to create styling effects the IITAA 1.0 2.1 Use text to display text, unless formatting that cannot be achieved with CSS is required. 2.2 Use relative sizes for fonts. Section 508 1194.31 (b) At least one mode of operation and information retrieval that does not require visual acuity greater than 20/70 shall be provided in audio and enlarged print output working together or independently, or support for assistive technology used by people who are visually impaired shall be provided. WCAG 2.0 .. (Level ) .. (Level ) WCAG 1.0 . (Priority )	D
HTML Scripting and Web Applications
R.1	Keyboard Operation All functions and tasks of a web resource can be completed using only keyboard commands. IITAA 1.0 None Section 508 WCAG 2.0 .. (Level ) .. (Level ) WCAG 1.0 . (Priority )	R
R.2	Dynamic Menus Dynamic and popup menus are created using ul and `li` and CSS techniques for rendering menu content and links, rather than using scripting to insert, delete and position menu items by manipulating the Document Object Model. Scripting is primarily used to emulate CSS techniques that are not directly supported by browsers like Microsoft Internet Explorer 6.0 for hiding and positioning links in the dynamic menu. IITAA 1.0 . Section 508 WCAG 2.0 .. (Level ) .. (Level ) WCAG 1.0 . (Priority ) . (Priority ) . (Priority )	R
R.3	Keyboard Shortcuts Frequently used functions have keyboard shortcuts. Keyboard shortcuts can be easily enabled or disabled by the user through a configuration setting or link on the web resource. Once keyboard shortcuts are enabled or disabled they remain in that state until the end of the current session or until the user changes the state. Keyboard shortcuts are part of the documentation of the resource. IITAA 1.0 None Section 508 WCAG 2.0 .. (Level ) .. (Level ) WCAG 1.0 . (Priority )	R
R.4	Configure Keyboard Shortcuts User is able to configure the keyboard shortcut for frequently used functions through a persistent configuration option. IITAA 1.0 None Section 508 WCAG 2.0 .. (Level ) .. (Level ) WCAG 1.0 . (Priority )	D
R.4	onChange Events `onChange`event handler on `select` elementsdo not cause a page reload or new resource to be loaded. IITAA 1.0 None Section 508 WCAG 2.0 .. (Level ) .. (Level ) WCAG 1.0 . (Priority )	R
R.5	Animations Animations and other automatically sequenced changes in content can be paused and restarted under user control. IITAA 1.0 None Section 508 WCAG 2.0 .. (Level ) .. (Level ) WCAG 1.0 . (Priority )	R
R.6	Flickering No content on the resource causes flickering between 2-55 Hz. IITAA 1.0 None Section 508 WCAG 2.0 .. (Level ) .. (Level ) WCAG 1.0 . (Priority )	R
R.7	Dynamic Content Dynamically generated or changing content has been tested with screen reader technology to make sure that it can be accessed with speech and refreshable Braille technologies. IITAA 1.0 None Section 508 WCAG 2.0 .. (Level ) .. (Level ) WCAG 1.0 . (Priority )	R
R.8	Embedded Objects Applications provide an accessible alternative for embedded Java Applets, Flash and other `applets` and `objects`s IITAA 1.0 None Section 508 WCAG 2.0 .. (Level ) .. (Level ) WCAG 1.0 . (Priority )	R
Multimedia
M.1	Text Transcripts Text transcript of audio, video+audio and other multimedia that include sound are available IITAA 1.0 None Section 508 WCAG 2.0 .. (Level ) .. (Level ) WCAG 1.0 . (Priority )	R
M.2	Captioning Text transcript video+audio and other multimedia with visual and auditory renderings are synchronized with visual rendering IITAA 1.0 None Section 508 WCAG 2.0 .. (Level ) .. (Level ) WCAG 1.0 . (Priority )	R
M.3	External Player Provides link to play multi-media content in external multimedia players. IITAA 1.0 None Section 508 WCAG 2.0 .. (Level ) .. (Level ) WCAG 1.0 . (Priority )	R
M.4	Audio Descriptions of Video Audio descriptions of visual events on video that is important to understanding the information in the video. IITAA 1.0 None Section 508 WCAG 2.0 .. (Level ) .. (Level ) WCAG 1.0 . (Priority )	D
Adobe PDF
A.1	Tagged PDF Support the use of tagged PDF for compatibility with assistive technologies. IITAA 1.0 . . Section 508 WCAG 2.0 .. (Level ) .. (Level ) WCAG 1.0 . (Priority )	R
A.2	Text Equivalents Text equivalents for image for all image objects in the PDF file. IITAA 1.0 . . Section 508 WCAG 2.0 .. (Level ) .. (Level ) WCAG 1.0 . (Priority )	R
A.3	Bookmarks Bookmarks should be set to major sections with in the PDF document. IITAA 1.0 . . Section 508 WCAG 2.0 .. (Level ) .. (Level ) WCAG 1.0 . (Priority )	R
A.4	Reading Order Tagged PDF reading order makes sense and represents visual document structure. IITAA 1.0 . . Section 508 WCAG 2.0 .. (Level ) .. (Level ) WCAG 1.0 . (Priority )	R
A.5	Forms Forms have labels and the tab order between form elements makes logical sense. IITAA 1.0 . . Section 508 WCAG 2.0 .. (Level ) .. (Level ) WCAG 1.0 . (Priority )	R
Commitment to Accessible Design
C.1	Participate in W3C WAI How many employees participate in activities related to the W3C Web Accessibility Initiative? IITAA 1.0 None Section 508 None WCAG 2.0 None WCAG 1.0 None	D
C.2	Participate in Section 508 Howmany employess participate in the web accessibility sub group of the Telecommunications and Electronic and Information Technology Advisory Committee to the United States Access Board? IITAA 1.0 None Section 508 None WCAG 2.0 None WCAG 1.0 None	D
C.3	Accessibility Design Specification Does your comapnay have accessibility design specifications and are adherance to these specifications tested as part of the quality assurance process? IITAA 1.0 None Section 508 None WCAG 2.0 None WCAG 1.0 None	D
C.4	User Testing with People with Disabilities Are people with disabilities including in usability and accessibility testing of products? IITAA 1.0 None Section 508 1194.31 (a) At least one mode of operation and information retrieval that does not require user vision shall be provided, or support for assistive technology used by people who are blind or visually impaired shall be provided. 1194.31 (b) At least one mode of operation and information retrieval that does not require visual acuity greater than 20/70 shall be provided in audio and enlarged print output working together or independently, or support for assistive technology used by people who are visually impaired shall be provided. 1194.31 (c) At least one mode of operation and information retrieval that does not require user hearing shall be provided, or support for assistive technology used by people who are deaf or hard of hearing shall be provided. 1194.31 (d) Where audio information is important for the use of a product, at least one mode of operation and information retrieval shall be provided in an enhanced auditory fashion, or support for assistive hearing devices shall be provided. 1194.31 (e) At least one mode of operation and information retrieval that does not require user speech shall be provided, or support for assistive technology used by people with disabilities shall be provided. 1194.31 (f) At least one mode of operation and information retrieval that does not require fine motor control or simultaneous actions and that is operable with limited reach and strength shall be provided. WCAG 2.0 None WCAG 1.0 None	D
C.5	Employment of People with Disabilities How many people with disabilities does your company employ in design, development, sales and/or administration? IITAA 1.0 None Section 508 None WCAG 2.0 None WCAG 1.0 None	D

Bread Crumbs

Web Technology Purchasing Requirements

Evaluating Accessibility of Products

1Priority

2Response Code

3Comments

Standards

Use Technologies that Support Accessibility

Show S.1 References

Avoid Technologies with Poor Accessibility Support

Show S.2 References

Content Language

Show S.3 References

Valid Markup

Show S.4 References

HTML Navigation

Unique Titles

Show N.1 References

Headings

Show N.2 References

Link Text

Show N.3 References

Image Maps

Show N.4 References

Navigation Bars and Menus

Show N.5 References

Form Control Labels and Grouping

Show N.6 References

Language Changes

Show N.7 References

Data Tables

Show N.8 References

Lists

Show N.9 References

Linearization

Show N.10 References

Frames

Show N.11 References

HTML Text Equivalents

Provide Text Equivalents for Images

Show E.1 References

Provide Equivalents for other Graphical or Programmatic Objects

Show E.2 References

HTML Styling

Text Styling

Show Y.1 References

Link Styling

Show Y.2 References

Color Coding

Show Y.2 References

Color Coding

Show Y.3 References

Styling Text

Show Y.5 References

Inline Styling

Show Y.6 References

Focus Styling

Show Y.7 References

Layout Tables

Show Y.2 References

HTML Scripting and Web Applications

Keyboard Operation

Show R.1 References

Dynamic Menus

Show R.2 References

Keyboard Shortcuts

Show R.3 References

Configure Keyboard Shortcuts

Show R.4 References

onChange Events

Show R.4 References

Animations

Show R.5 References

Flickering

Show R.6 References

Dynamic Content

Show R.7 References

Embedded Objects

Show R.8 References

Multimedia

¹Priority

²Response Code

³Comments