Section 508 (Revised) Summary Report - Microsoft
Section 508 (Revised) Summary ReportDate: 8/1/2017Name of Product: Azure Container RegistryDescription of Product: Azure Container Registry is a private registry for hosting container images. Using the Azure Container Registry, you can store Docker-formatted images for all types of container deployments. Azure Container Registry integrates well with orchestrators hosted in Azure Container Service, including Docker Swarm, DC/OS, and Kubernetes. Users can benefit from using familiar tooling capable of working with the open source Docker Registry v2.Platform: WebConformance to accessibility standards has been evaluated by external suppliers under the?DHS Trusted Tester Program. For more information, please?email us.Website: Azure PortalSupport: Azure Container Registry DocumentationAccessibility Website: Enterprise Disability Answer DeskFor assistance with this report, please email us.Chapter 1 Application and AdministrationSection 508 (ICT Refresh)Chapter 2 Scoping RequirementsCriteriaE207.2 WCAG Conformance. User interface components and content of platforms and applications shall conform to Level A and Level AA Success Criteria and Conformance Requirements specified for web pages inWCAG 2.0.Web Content Accessibility Guidelines (WCAG) 2.0 Principle 1: PerceivableInformation and user interface components must be presentable to users in ways they can perceive.Guideline 1.1 Text AlternativesProvide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language.CriteriaSupporting Feature1.1.1 Non-text ContentSupportedGuideline 1.2 Time-based MediaProvide alternatives for time-based media.CriteriaSupporting Feature1.2.1 Audio-only and Video-only (Prerecorded)Not Applicable1.2.2 Captions (Prerecorded)Not Applicable1.2.3 Audio Description or Media Alternative (Prerecorded)Not Applicable1.2.4 Captions (Live)Not Applicable1.2.5 Audio Description (Prerecorded)Not ApplicableGuideline 1.3 AdaptableCreate content that can be presented in different ways (for example simpler layout) without losing information or structure.CriteriaSupporting Feature1.3.1 Info and RelationshipsSupported1.3.2 Meaningful SequenceSupported1.3.3 Sensory CharacteristicsSupportedGuideline 1.4 DistinguishableMake it easier for users to see and hear content including separating foreground from background.CriteriaSupporting Feature1.4.1 Use of ColorSupported1.4.2 Audio ControlNot Applicable1.4.3 Contrast (Minimum)Supported1.4.4 Resize textSupported1.4.5 Images of TextSupportedPrinciple 2: OperableUser interface components and navigation must be operable.Guideline 2.1 Keyboard AccessibleMake all functionality available from a keyboard. CriteriaSupporting Feature2.1.1 KeyboardSupported With Exceptions2.1.2 No Keyboard TrapSupportedGuideline 2.2 Enough TimeProvide users enough time to read and use content. CriteriaSupporting Feature2.2.1 Timing AdjustableNot Applicable2.2.2 Pause, Stop, HideSupportedGuideline 2.3 SeizuresDo not design content in a way that is known to cause seizures. CriteriaSupporting Feature2.3.1 Three Flashes or Below ThresholdSupportedGuideline 2.4 NavigableProvide ways to help users navigate, find content, and determine where they are. CriteriaSupporting Feature2.4.1 Bypass BlocksSupported2.4.2 Page TitledSupported2.4.3 Focus OrderSupported2.4.4 Link Purpose (In Context)Supported2.4.5 Multiple WaysSupported2.4.6 Headings and LabelsSupported2.4.7 Focus VisibleSupportedPrinciple 3: UnderstandableInformation and the operation of user interface must be understandable. Guideline 3.1 ReadableMake text content readable and understandable. CriteriaSupporting Feature3.1.1 Language of PageSupported3.1.2 Language of PartsNot ApplicableGuideline 3.2 PredictableMake Web pages appear and operate in predictable ways. CriteriaSupporting Feature3.2.1 On FocusSupported3.2.2 On InputSupported3.2.3 Consistent NavigationSupported3.2.4 Consistent IdentificationSupportedGuideline 3.3 Input AssistanceHelp users avoid and correct mistakes.CriteriaSupporting Feature3.3.1 Error IdentificationSupported3.3.2 Labels or InstructionsSupported3.3.3 Error SuggestionSupported3.3.4 Error Prevention (Legal, Financial, Data)SupportedPrinciple 4: RobustContent must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.Guideline 4.1 CompatibleMaximize compatibility with current and future user agents, including assistive technologies. CriteriaSupporting Feature4.1.1 ParsingSupported4.1.2 Name, Role, ValueSupported With ExceptionsChapter 3 Functional Performance Criteria301 General301.1 Scope The requirements of Chapter 3 shall apply to ICT where required by 508 Chapter 2 (Scoping Requirements), 255 Chapter 2 (Scoping Requirements), and where otherwise referenced in any other chapter of the Revised 508 Standards or Revised 255 Guidelines.302 Functional Performance CriteriaCriteria302.1 Without vision302.2 With limited vision302.3 Without Perception of Color302.4 Without Hearing302.5 With Limited Hearing302.6 Without Speech302.7 With Limited Manipulation302.8 With Limited Reach and Strength302.9 With Limited Language, Cognitive, and Learning AbilitiesChapter 4 Hardware401 General401.1 Scope. The requirements of Chapter 4 shall apply to ICT that is hardware where required by 508 Chapter 2 (Scoping Requirements), 255 Chapter 2 (Scoping Requirements), and where otherwise referenced in any other chapter of the Revised 508 Standards or Revised 255 Guidelines.EXCEPTION: Hardware that is assistive technology shall not be required to conform to the requirements of this chapter.402 Closed Functionality402.1 General. ICT with closed functionality shall be operable without requiring the user to attach or install assistive technology other than personal headsets or other audio couplers, and shall conform to 402. CriteriaSupporting Feature402.2 Speech-Output EnabledNot Applicable402.2.1 Information Displayed On-ScreenNot Applicable402.2.2 Transactional OutputsNot Applicable402.2.3 Speech Delivery Type and CoordinationNot Applicable402.2.4 User ControlNot Applicable402.2.5 Braille InstructionsNot Applicable402.3 VolumeNot Applicable402.3.1 Private ListeningNot Applicable402.3.2 Non-private ListeningNot Applicable402.4 CharactersNot Applicable402.5 Characters on Variable Message SignsNot Applicable403 BiometricsCriteriaSupporting Feature403.1 GeneralNot Applicable404 Preservation of Information Provided for AccessibilityCriteriaSupporting Feature404.1 GeneralNot Applicable405 PrivacyCriteriaSupporting Feature405.1 GeneralNot Applicable406 Standard ConnectionsCriteriaSupporting Feature406.1 GeneralNot Applicable407 Operable Parts407.1 General.?Where provided, operable parts used in the normal operation of ICT shall conform to 407.CriteriaSupporting Feature407.2 ContrastNot Applicable407.3 Input ControlsSee 407.3.1, 407.3.2, and 407.3.3.407.3.1 Tactilely DiscernibleNot Applicable407.3.2 Alphabetic KeysNot Applicable407.3.3 Numeric KeysNot Applicable407.4 Key RepeatNot Applicable407.5 Timed ResponseNot Applicable407.6 OperationNot Applicable407.7 Tickets, Fare Cards, and KeycardsNot Applicable407.8 Reach Height and DepthNot Applicable407.8.1 Vertical Reference PlaneNot Applicable407.8.1.1 Vertical Plane for Side ReachNot Applicable407.8.1.2 Vertical Plane for Forward ReachNot Applicable407.8.2 Side ReachNot Applicable407.8.2.1 Unobstructed Side ReachNot Applicable407.8.2.2 Obstructed Side ReachNot Applicable407.8.3 Forward ReachNot Applicable407.8.3.1 Unobstructed Forward ReachNot Applicable407.8.3.2 Obstructed Forward ReachNot Applicable407.8.3.2.1 Operable Part Height for ICT with Obstructed Forward ReachNot Applicable407.8.3.2.2 Knee and Toe Space under ICT with Obstructed Forward ReachNot Applicable408 Display Screen408.1 General. Where provided, display screens shall conform to 408.CriteriaSupporting Feature408.2 VisibilityNot Applicable408.3 FlashingNot Applicable409 Status IndicatorsCriteriaSupporting Feature409.1 GeneralNot Applicable410 Color CodingCriteriaSupporting Feature410.1 GeneralNot Applicable411 Audible SignalsCriteriaSupporting Feature411.1 GeneralNot Applicable412 ICT with Two-Way Voice Communication412.1 General.?ICT that provides two-way voice communication shall conform to 412.CriteriaSupporting Feature412.2 Volume GainSee 412.2.2412.2.1 Volume Gain for Wireline TelephonesNot Applicable412.2.2 Volume Gain for Non-Wireline ICTNot Applicable412.3 Interference Reduction and Magnetic CouplingSee 412.3.1412.3.1 Wireless HandsetsNot Applicable412.3.2 Wireline HandsetsNot Applicable412.4 Digital Encoding of SpeechNot Applicable412.5 Real-Time Text FunctionalityNot Applicable412.6 Caller IDNot Applicable412.7 Video CommunicationNot Applicable413 Closed Caption Processing Technologies413.1 General.?Where ICT displays or processes video with synchronized audio, ICT shall provide closed caption processing technology that conforms to 413.1.1 or 413.1.2.CriteriaSupporting Feature413.1.1 Decoding and Display of Closed CaptionsNot Applicable413.1.2 Pass-Through of Closed Caption DataNot Applicable414 Audio Description Processing Technologies414.1 General.?Where ICT displays or processes video with synchronized audio, ICT shall provide audio description processing technology conforming to 414.1.1 or 414.1.2.CriteriaSupporting Feature414.1.1 Digital Television TunersNot Applicable414.1.2 Other ICTNot Applicable415 User Controls for Captions and Audio Descriptions415.1 General.?Where ICT displays video with synchronized audio, ICT shall provide user controls for closed captions and audio descriptions conforming to 415.1.CriteriaSupporting Feature415.1.1 Caption ControlsNot Applicable415.1.2 Audio DescriptionNot ApplicableChapter 5 Software501 General501.1 Scope. The requirements of Chapter 5 shall apply to software where required by 508 Chapter 2 (Scoping Requirements), 255 Chapter 2 (Scoping Requirements), and where otherwise referenced in any other chapter of the Revised 508 Standards or Revised 255 Guidelines.EXCEPTION: Where Web applications do not have access to platform accessibility services and do not include components that have access to platform accessibility services, they shall not be required to conform to 502 or 503 provided that they conform to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 (incorporated by reference, see 702.10.1).502 Interoperability with Assistive Technology502.1 General.?Software shall interoperate with assistive technology and shall conform to 502.502.2 Documented Accessibility Features. Software with platform features defined in platform documentation as accessibility features shall conform to 502.2.CriteriaSupporting Feature502.2.1 User Control of Accessibility FeaturesNot Applicable502.2.2 No Disruption of Accessibility FeaturesSupported502.3 Accessibility ServicesNot Applicable502.3.1 Object InformationSupported502.3.2 Modification of Object InformationSupported502.3.3 Row, Column, and HeadersSupported502.3.4 ValuesSupported502.3.5 Modification of ValuesSupported502.3.6 Label RelationshipsSupported502.3.7 Hierarchical RelationshipsSupported502.3.8 TextSupported502.3.9 Modification of TextSupported502.3.10 List of ActionsSupported502.3.11 Actions on ObjectsSupported502.3.12 Focus CursorSupported502.3.13 Modification of Focus CursorSupported502.3.14 Event NotificationSupported502.4 Platform Accessibility FeaturesNot Applicable503 Applications503.1 General.?Applications shall conform to 503.CriteriaSupporting Feature503.2 User Preferences Supported503.3 Alternative User InterfacesSupported503.4 User Controls for Captions and Audio DescriptionSee 503.4.1 and 503.4.2.503.4.1 Caption ControlsNot Applicable503.4.2 Audio Description ControlsNot Applicable504 Authoring Tools504.1 General.?Where an application is an authoring tool, the application shall conform to 504 to the extent that information required for accessibility is supported by the destination format.CriteriaSupporting Feature504.2 Content Creation or EditingNot Applicable504.2.1 Preservation of Information Provided for Accessibility in Format ConversionNot Applicable504.2.2 PDF ExportNot Applicable504.3 PromptsNot Applicable504.4 TemplatesNot ApplicableChapter 6 Support Documentation and Services602 Support Documentation602.1 General.?Documentation that supports the use of ICT shall conform to 602.CriteriaSupporting Feature602.2 Accessibility and Compatibility FeaturesSupported602.3 Electronic Support DocumentationSupported602.4 Alternate Formats for Non-Electronic Support DocumentationSupported603 Support Services603.1 General.?ICT support services including, but not limited to, help desks, call centers, training services, and automated self-service technical support, shall conform to 603.CriteriaSupporting Feature603.2 Information on Accessibility and Compatibility FeaturesSupported603.3 Accommodation of Communication NeedsDisability Answer DeskDisclaimer? 2017 Microsoft Corporation. All rights reserved. The names of actual companies and products mentioned herein may be the trademarks of their respective owners. The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Microsoft cannot guarantee the accuracy of any information presented after the date of publication. Microsoft regularly updates its websites with new information about the accessibility of products as that information becomes available.This document includes material copied from or derived from the Web Content Accessibility Guidelines (WCAG) 2.0). Copyright ? 2015 W3C? (MIT, ERCIM, Keio, Beihang). This document is not the Web Content Accessibility Guidelines (WCAG) and should not be used as a substitute for it. Excerpts of WCAG are referenced solely for purposes of detailing Microsoft’s conformance with the relevant provisions. A full and complete copy of the Guidelines is available from the W3C WAI.Customization of the product voids this conformance statement from Microsoft. Customers may make independent conformance statements if they have conducted due diligence to meet all relevant requirements for their customization.Please consult with Assistive Technology (AT) vendors for compatibility specifications of specific AT products. This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT. ................
................
In order to avoid copyright disputes, this page is only a partial summary.
To fulfill the demand for quickly locating and searching documents.
It is intelligent file search solution for home and business.
Related searches
- financial summary report sample
- financial summary report template
- financial executive summary report example
- quarterly summary report template word
- audit summary report template
- quarterly summary report template
- business summary report example
- example of summary report writing
- summary report template examples
- monthly summary report template
- event summary report template
- quarterly summary report examples