My WebLink
|
Help
|
About
|
Sign Out
Home
8H Consent 2016 0418
CityHall
>
City Clerk
>
City Council
>
Agenda Packets
>
2016
>
Packet 2016 0418
>
8H Consent 2016 0418
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
4/25/2016 5:23:33 PM
Creation date
4/14/2016 10:34:31 AM
Metadata
Fields
Template:
CM City Clerk-City Council
CM City Clerk-City Council - Document Type
Staff Report
Document Date (6)
4/18/2016
Retention
PERM
Document Relationships
_CC Agenda 2016 0418 CS+RG
(Reference)
Path:
\City Clerk\City Council\Agenda Packets\2016\Packet 2016 0418
Reso 2016-043
(Reference)
Path:
\City Clerk\City Council\Resolutions\2016
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
180
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
Download electronic document
View images
View plain text
<br /> <br />49 SECTION 2: MASTER AGREEMENT TERMS AND CONDITIONS | 2014_0122 <br /> <br />VPAT <br />Web Content Accessibility Guidelines 2.0 level AA <br />The requested WCAG VPAT applies to the responder’s website to be offered under the Contract. For products <br />offered, VPATS are only to be provided upon request by the participating entity.It is strongly recommended <br />Technical Staff who are trained in Accessibility complete this form. <br />The comments portion must be filled in to further define how accessibility is or is not met. The quality of the comments impacts <br />the reviewers’ understanding of the accessibility of your product/service. NOTE: MN only adopted the standards that are level A <br />and level AA. This list includes level AAA standards, which are optional and highlighted in yellow. Comments are not required <br />for level AAA. <br />Principle 1: Perceivable – information and user interface components must be presentable to <br />users in ways they can perceive. <br />Standard Description Apply <br />Yes/No <br />Meets <br />Yes/No <br />Comments <br />(mandatory) <br />Guideline 1.1 Text Alternatives: Provide text alternatives for any non-text content so that it can be changed <br />into other forms people need, such as large print, braille, speech, symbols or simpler language. <br />1.1.1 Non-text Content: All non-text content that is presented to the user <br />has a text alternative that serves the equivalent purpose, except for <br />the situations listed below (Level A). <br /> Controls, Input: If non-text content is a control or accepts user <br />input, then it has a name that describes its purpose. (Refer to <br />Guideline 4.1 for additional requirements for controls and <br />content that accepts user input.) <br /> Time-Based Media: If non-text content is time-based media, <br />then text alternatives at least provide descriptive identification <br />of the non-text content. (Refer to Guideline 1.2 for the <br />additional requirements for media.) <br /> Test: If non-text content is a test or exercise that would be <br />invalid if presented in text, then text alternatives at least provide <br />descriptive identification of the non-text content. <br /> Sensory: If non-text content is primarily intended to create a <br />specific sensory experience, then text alternatives at least <br />provide descriptive identification of the non-text content. <br /> CAPTCHA: If the purpose of non-text content is to confirm that <br />content is being accessed by a person rather than a computer, <br />then text alternatives that identify and describe the purpose of <br />the non-text content are provided, and alternative forms of <br />CAPTCHA using output modes for different types of sensory <br />perception are provided to accommodate different disabilities. <br /> Decorative, Formatting, Invisible: If non-text content is pure <br />decoration, is used only for visual formatting, or is not <br />presented to users, then it is implemented in a way that it can <br />be ignored by assistive technology. <br />
The URL can be used to link to this page
Your browser does not support the video tag.