Section 508 (Revised) Report - Microsoft



Section 508 (Revised) ReportDate: 8/7/2017Name of Product: Visual Studio 2017Description of Product: Visual Studio is a rich, integrated development environment for creating stunning applications for Windows, Android, and iOS, as well as modern web applications and cloud services.Platform: Win32Visual Studio 2017 Conformance Documentation: GlobalWeb ToolsSome users may experience accessibility difficulty with the?publishing options on the project properties screen?due to incompatibilities with some assistive technologies.Visually impaired users may not be able to take full advantage of the WebForms designer.Some users may experience accessibility difficulty with the?screen for manually synchronizing files between the local environment and the location the project is deployed to?due to incompatibilities with some assistive technologies.Some users may experience difficulty with the HTML Tag Navigator due to incompatibilities with some assistive technologies..NET DevExThe Code Analysis Solution Property Page is not fully accessible.The Code Analysis Ruleset Editor is not fully accessible.?Visual C++Several of the Win32 Resource editors are not fully accessible to varying degrees especially with regard to being able to understand information and relationships of UI items as they navigate within them. In particular, users will likely have difficulty using a screen reader with the following editors:Cursor EditorRibbon EditorString Table EditorAccelerator EditorBinary EditorUsers who rely on accessibility features may have difficulty creating new MFC applications using the Visual C++ MFC Application Wizard. This wizard has various accessibility issues, including improper keyboard navigation, screen-reader issues, and high-contrast problems. ?Microsoft Test Manager and Feedback Client Microsoft Test Manager (MTM) and Feedback Client are desktop applications that ship in VS Enterprise and VS Test Professional SKUs. MTM and Feedback Client are not accessible. The Test hub, which is accessible, has full parity with the capabilities offered by MTM except "Testing desktop apps." For more information, please refer to "Guidance on Microsoft Test Manager Usage."?XAML Build in TeamExplorerXAML Build in TeamExplorer is not accessible and we are deprecating this experience in VS 2018. The new build system is accessible and the preferred system moving forward. For more information, please refer to "Evolving TFS/Team Services build automation capabilities."?Graphical representation of commits in CodeLensIn CodeLens we show commits for a particular file in a list view. This information is accessible. We show the same information in a graphical UI as well.?The graphical view is not accessible.?Team Explorer Work Item Tracking affecting query and viewing/editing work itemsIn VS2017, the default experience is to open work items in the web view (which is accessible), however there is an option to open and view work items in the IDE. If someone selects that option, they will run into issues with visible focus, keyboard interaction, name/role/value and high contrast. VS2017 is the last release this experience is available. In the next release, the experience will always be web-based. Conformance to accessibility standards has been evaluated by external suppliers under the?DHS Trusted Tester Program. For more information, please?email us.Website: Visual StudioContact for more information: 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 FeatureRemarks and Explanations1.1.1 Non-text Content: All non-text content that is presented to the user has a text alternative that serves the equivalent purpose, except in situations listed in WCAG 2.0 1.1.1.Supported With ExceptionsWorkflowSome users may have difficulties determining where breakpoints are set in a Workflow in the Workflow designer.Guideline 1.2 Time-based MediaProvide alternatives for time-based media.CriteriaSupporting FeatureRemarks and Explanations1.2.1 Audio-only and Video-only (Prerecorded): For prerecorded audio-only and prerecorded video-only media, the following are true, except when the audio or video is a media alternative for text and is clearly labeled as such:? Prerecorded Audio-only: An alternative for time-based media is provided that presents equivalent information for prerecorded audio-only content.? Prerecorded Video-only: Either an alternative for time-based media or an audio track is provided that presents equivalent information for prerecorded video-only content.Not Applicable1.2.2 Captions (Prerecorded): Captions are provided for all prerecorded audio content in synchronized media, except when the media is a media alternative for text and is clearly labeled as such.Not Applicable1.2.3 Audio Description or Media Alternative (Prerecorded): An alternative for time-based media or audio description of the prerecorded video content is provided for synchronized media, except when the media is a media alternative for text and is clearly labeled as such.Not Applicable1.2.4 Captions (Live): Captions are provided for all live audio content in synchronized media.Not Applicable1.2.5 Audio Description (Prerecorded): Audio description is provided for all prerecorded video content in synchronized media.Not ApplicableGuideline 1.3 AdaptableCreate content that can be presented in different ways (for example simpler layout) without losing information or structure.CriteriaSupporting FeatureRemarks and Explanations1.3.1 Info and Relationships: Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.Supported With ExceptionsSee Table 11.3.2 Meaningful Sequence: When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined.Supported1.3.3 Sensory Characteristics: Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, size, visual location, orientation, or sound.SupportedGuideline 1.4 DistinguishableMake it easier for users to see and hear content including separating foreground from background.CriteriaSupporting FeatureRemarks and Explanations1.4.1 Use of Color: Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.Supported1.4.2 Audio Control: If any audio on a Web page plays automatically for more than 3 seconds, either a mechanism is available to pause or stop the audio, or a mechanism is available to control audio volume independently from the overall system volume level.Not Applicable1.4.3 Contrast (Minimum): The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, except for situations listed in WCAG 2.0 1.4.3. Supported With ExceptionsSee Table 21.4.4 Resize text: Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality.Supported1.4.5 Images of Text: If the technologies being used can achieve the visual presentation, text is used to convey information rather than images of text except for the following: ? Customizable: The image of text can be visually customized to the user's requirements;? Essential: A particular presentation of text is essential to the information being conveyed.SupportedPrinciple 2: OperableUser interface components and navigation must be operable.Guideline 2.1 Keyboard AccessibleMake all functionality available from a keyboard. CriteriaSupporting FeatureRemarks and Explanations2.1.1 Keyboard: All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints.Supported With ExceptionsSee Table 32.1.2 No Keyboard Trap: If keyboard focus can be moved to a component of the page using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, the user is advised of the method for moving focus away.Supported With ExceptionsDiagnostics- While inspecting the Performance Tools options in the Tools -> Options dialog , users cannot use the Tab or Arrow keys exclusively to navigate the elements of the window and focus order is not consistent between Tab and Arrow keys. Screen reader users may not be able to determine the flow of the window.- While inspecting a performance violation in an IntelliTrace file with performance data, users cannot tab out of the call tree once the focus is set on it. This is a keyboard trap for users with visual impairments who will find it difficult to navigate away from the call tree using the keyboard. Users may escape the trap by closing the IntelliTrace file and re-opening it.Guideline 2.2 Enough TimeProvide users enough time to read and use content. CriteriaSupporting FeatureRemarks and Explanations2.2.1 Timing Adjustable: For each time limit that is set by the content, at least one of the instances in WCAG 2.0 2.2.1 is true.Not Applicable2.2.2 Pause, Stop, Hide: For moving, blinking, scrolling, or auto-updating information, all of the following are true:? Moving, blinking, scrolling: For any moving, blinking or scrolling information that (1) starts automatically, (2) lasts more than five seconds, and (3) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it unless the movement, blinking, or scrolling is part of an activity where it is essential; and? Auto-updating: For any auto-updating information that (1) starts automatically and (2) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it or to control the frequency of the update unless the auto-updating is part of an activity where it is essential.Not ApplicableGuideline 2.3 SeizuresDo not design content in a way that is known to cause seizures. CriteriaSupporting FeatureRemarks and Explanations2.3.1 Three Flashes or Below Threshold: Web pages do not contain anything that flashes more than three times in any one second period, or the flash is below the general flash and red flash thresholds.SupportedGuideline 2.4 NavigableProvide ways to help users navigate, find content, and determine where they are. CriteriaSupporting FeatureRemarks and Explanations2.4.1 Bypass Blocks: A mechanism is available to bypass blocks of content that are repeated on multiple Web pages.Not Applicable2.4.2 Page Titled: Web pages have titles that describe topic or purpose.Not Applicable2.4.3 Focus Order: If a Web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability.Supported With ExceptionsSee Table 42.4.4 Link Purpose (In Context): The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general.Supported2.4.5 Multiple Ways: More than one way is available to locate a Web page within a set of Web pages except where the Web Page is the result of, or a step in, a process.Not Applicable2.4.6 Headings and Labels: Headings and labels describe topic or purpose.Supported2.4.7 Focus Visible: Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible.Supported With ExceptionsSee Table 5Principle 3: UnderstandableInformation and the operation of user interface must be understandable. Guideline 3.1 ReadableMake text content readable and understandable. CriteriaSupporting FeatureRemarks and Explanations3.1.1 Language of Page: The default human language of each Web page can be programmatically determined.Supported3.1.2 Language of Parts: The human language of each passage or phrase in the content can be programmatically determined except for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text.Not ApplicableGuideline 3.2 PredictableMake Web pages appear and operate in predictable ways. CriteriaSupporting FeatureRemarks and Explanations3.2.1 On Focus: When any component receives focus, it does not initiate a change of context.Supported3.2.2 On Input: Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the componentSupported3.2.3 Consistent Navigation: Navigational mechanisms that are repeated on multiple Web pages within a set of Web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user.Not Applicable3.2.4 Consistent Identification: Components that have the same functionality within a set of Web pages are identified consistently.Supported With - When users configure a DataPager web control, user could edit pager fields. In the Fields dialog, some users may have difficulty accessing the access Available Fields or Selected Fields.- When user choose Configuration Data Selection Dialog during create/config data sources for web controls, some users may have difficulties accessing the 'Move up' , 'Move down' or 'Delete' operations using keyboard for the associated table elements.Guideline 3.3 Input AssistanceHelp users avoid and correct mistakes.CriteriaSupporting FeatureRemarks and Explanations3.3.1 Error Identification: If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text.Supported3.3.2 Labels or Instructions: Labels or instructions are provided when content requires user input.Supported3.3.3 Error Suggestion: If an input error is automatically detected and suggestions for correction are known, then the suggestions are provided to the user, unless it would jeopardize the security or purpose of the content.Supported3.3.4 Error Prevention (Legal, Financial, Data): For Web pages that cause legal commitments or financial transactions for the user to occur, that modify or delete user-controllable data in data storage systems, or that submit user test responses, at least one of the following is true: 1. Reversible: Submissions are reversible.2. Checked: Data entered by the user is checked for input errors and the user is provided an opportunity to correct them.3. Confirmed: A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission.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 FeatureRemarks and Explanations4.1.1 Parsing: In content implemented using markup languages, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique, except where the specifications allow these features.Supported4.1.2 Name, Role, Value: For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies.Supported With ExceptionsSee Table 6Chapter 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 vision. Where a visual mode of operation is provided, ICT shall provide at least one mode of operation that does not require user vision.302.2 With limited vision. Where a visual mode of operation is provided, ICT shall provide at least one mode of operation that enables users to make use of limited vision.302.3 Without Perception of Color. Where a visual mode of operation is provided, ICT shall provide at least one visual mode of operation that does not require user perception of color.302.4 Without Hearing. Where an audible mode of operation is provided, ICT shall provide at least one mode of operation that does not require user hearing.302.5 With Limited Hearing. Where an audible mode of operation is provided, ICT shall provide at least one mode of operation that enables users to make use of limited hearing.302.6 Without Speech. Where speech is used for input, control, or operation, ICT shall provide at least one mode of operation that does not require user speech.302.7 With Limited Manipulation. Where a manual mode of operation is provided, ICT shall provide at least one mode of operation that does not require fine motor control or simultaneous manual operations.302.8 With Limited Reach and Strength. Where a manual mode of operation is provided, ICT shall provide at least one mode of operation that is operable with limited reach and limited strength.302.9 With Limited Language, Cognitive, and Learning Abilities. ICT shall provide features making its use by individuals with limited cognitive, language, and learning abilities simpler and easier.Chapter 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 FeatureRemarks and Explanations402.2 Speech-Output Enabled.?ICT with a display screen shall be speech-output enabled for full and independent use by individuals with vision impairments.Not Applicable402.2.1 Information Displayed On-Screen. Speech output shall be provided for all information displayed on-screen.Not Applicable402.2.2 Transactional Outputs. Where transactional outputs are provided, the speech output shall audibly provide all information necessary to verify a transaction.Not Applicable402.2.3 Speech Delivery Type and Coordination. Speech output shall be delivered through a mechanism that is readily available to all users, including, but not limited to, an industry standard connector or a telephone handset. Speech shall be recorded or digitized human, or synthesized. Speech output shall be coordinated with information displayed on the screen.Not Applicable402.2.4 User Control. Speech output for any single function shall be automatically interrupted when a transaction is selected. Speech output shall be capable of being repeated and paused.Not Applicable402.2.5 Braille Instructions. Where speech output is required by 402.2, braille instructions for initiating the speech mode of operation shall be provided. Not Applicable402.3 Volume. ICT that delivers sound, including speech output required by 402.2, shall provide volume control and output amplification conforming to 402.3.Not Applicable402.3.1 Private Listening. Where ICT provides private listening, it shall provide a mode of operation for controlling the volume. Where ICT delivers output by an audio transducer typically held up to the ear, a means for effective magnetic wireless coupling to hearing technologies shall be provided.Not Applicable402.3.2 Non-private Listening.?Where ICT provides non-private listening, incremental volume control shall be provided with output amplification up to a level of at least 65 dB. A function shall be provided to automatically reset the volume to the default level after every use.Not Applicable402.4 Characters.?At least one mode of characters displayed on the screen shall be in a sans serif font. Where ICT does not provide a screen enlargement feature, characters shall be 3/16 inch (4.8 mm) high minimum based on the uppercase letter “I”. Characters shall contrast with their background with either light characters on a dark background or dark characters on a light background.Not Applicable402.5 Characters on Variable Message Signs. Characters on variable message signs shall conform to section 703.7 Variable Message Signs of ICC A117.1-2009 (incorporated by reference, see 702.6.1).Not Applicable403 BiometricsCriteriaSupporting FeatureRemarks and Explanations403.1 General.?Biometrics shall not be the only means for user identification or control.Not Applicable404 Preservation of Information Provided for AccessibilityCriteriaSupporting FeatureRemarks and Explanations404.1 General.?ICT that transmits or converts information or communication shall not remove non-proprietary information provided for accessibility or shall restore it upon delivery.Supported405 PrivacyCriteriaSupporting FeatureRemarks and Explanations405.1 General.?The same degree of privacy of input and output shall be provided to all individuals. When speech output required by 402.2 is enabled, the screen shall not blank automatically.Not Applicable406 Standard ConnectionsCriteriaSupporting FeatureRemarks and Explanations406.1 General.?Where data connections used for input and output are provided, at least one of each type of connection shall conform to industry standard non-proprietary formats.Not Applicable407 Operable Parts407.1 General.?Where provided, operable parts used in the normal operation of ICT shall conform to 407.CriteriaSupporting FeatureRemarks and Explanations407.2 Contrast.?Where provided, keys and controls shall contrast visually from background surfaces. Characters and symbols shall contrast visually from background surfaces with either light characters or symbols on a dark background or dark characters or symbols on a light background.Not Applicable407.3 Input Controls. At least one input control conforming to 407.3 shall be provided for each function.See 407.3.1, 407.3.2, and 407.3.3.407.3.1 Tactilely Discernible. Input controls shall be operable by touch and tactilely discernible without activation.Not Applicable407.3.2 Alphabetic Keys. Where provided, individual alphabetic keys shall be arranged in a QWERTY-based keyboard layout and the “F” and “J” keys shall be tactilely distinct from the other keys.Not Applicable407.3.3 Numeric Keys.?Where provided, numeric keys shall be arranged in a 12-key ascending or descending keypad layout. The number five key shall be tactilely distinct from the other keys. Where the ICT provides an alphabetic overlay on numeric keys, the relationships between letters and digits shall conform to ITU-T Recommendation E.161 (incorporated by reference, see 702.7.1).Not Applicable407.4 Key Repeat. Where a keyboard with key repeat is provided, the delay before the key repeat feature is activated shall be fixed at, or adjustable to, 2 seconds minimum.Not Applicable407.5 Timed Response. Where a timed response is required, the user shall be alerted visually, as well as by touch or sound, and shall be given the opportunity to indicate that more time is needed.Not Applicable407.6 Operation. At least one mode of operation shall be operable with one hand and shall not require tight grasping, pinching, or twisting of the wrist. The force required to activate operable parts shall be 5 pounds (22.2 N) maximum.Not Applicable407.7 Tickets, Fare Cards, and Keycards. Where tickets, fare cards, or keycards are provided, they shall have an orientation that is tactilely discernible if orientation is important to further use of the ticket, fare card, or keycard.Not Applicable407.8 Reach Height and Depth. At least one of each type of operable part of stationary ICT shall be at a height conforming to 407.8.2 or 407.8.3 according to its position established by the vertical reference plane specified in 407.8.1 for a side reach or a forward reach. Operable parts used with speech output required by 402.2 shall not be the only type of operable part complying with 407.8 unless that part is the only operable part of its type.Not Applicable407.8.1 Vertical Reference Plane. Operable parts shall be positioned for a side reach or a forward reach determined with respect to a vertical reference plane. The vertical reference plane shall be located in conformance to 407.8.2 or 407.8.3.Not Applicable407.8.1.1 Vertical Plane for Side Reach. Where a side reach is provided, the vertical reference plane shall be 48 inches (1220 mm) long minimum.Not Applicable407.8.1.2 Vertical Plane for Forward Reach. Where a forward reach is provided, the vertical reference plane shall be 30 inches (760 mm) long minimum.Not Applicable407.8.2 Side Reach. Operable parts of ICT providing a side reach shall conform to407.8.2.1 or 407.8.2.2. The vertical reference plane shall be centered on the operable part and placed at the leading edge of the maximum protrusion of the ICT within the length of the vertical reference plane. Where a side reach requires a reach over a portion of the ICT, the height of that portion of the ICT shall be 34 inches (865 mm) maximum.Not Applicable407.8.2.1 Unobstructed Side Reach. Where the operable part is located 10 inches (255 mm) or less beyond the vertical reference plane, the operable part shall be 48 inches (1220 mm) high maximum and 15 inches (380 mm) high minimum above the floor.Not Applicable407.8.2.2 Obstructed Side Reach. Where the operable part is located more than 10 inches (255 mm), but not more than 24 inches (610 mm), beyond the vertical reference plane, the height of the operable part shall be 46 inches (1170 mm) high maximum and 15 inches (380 mm) high minimum above the floor. The operable part shall not be located more than 24 inches (610 mm) beyond the vertical reference plane.Not Applicable407.8.3 Forward Reach. Operable parts of ICT providing a forward reach shall conform to 407.8.3.1 or 407.8.3.2. The vertical reference plane shall be centered, and intersect with, the operable part. Where a forward reach allows a reach over a portion of the ICT, the height of that portion of the ICT shall be 34 inches (865 mm) maximum.Not Applicable407.8.3.1 Unobstructed Forward Reach. Where the operable part is located at the leading edge of the maximum protrusion within the length of the vertical reference plane of the ICT, the operable part shall be 48 inches (1220 mm) high maximum and 15 inches (380 mm) high minimum above the floor.Not Applicable407.8.3.2 Obstructed Forward Reach. Where the operable part is located beyond the leading edge of the maximum protrusion within the length of the vertical reference plane, the operable part shall conform to 407.8.3.2. The maximum allowable forward reach to an operable part shall be 25 inches (635 mm).Not Applicable407.8.3.2.1 Operable Part Height for ICT with Obstructed Forward Reach. The height of the operable part shall conform to Table 407.8.3.2.1.Reach DepthOperable Part HeightLess than 20 inches (510 mm)48 inches (1220 mm) maximum20 inches (510 mm) to 25 inches (635 mm)44 inches (1120 mm) maximumNot Applicable407.8.3.2.2 Knee and Toe Space under ICT with Obstructed Forward Reach. Knee and toe space under ICT shall be 27 inches (685 mm) high minimum, 25 inches (635 mm) deep maximum, and 30 inches (760 mm) wide minimum and shall be clear of obstructions.Not Applicable408 Display Screen408.1 General. Where provided, display screens shall conform to 408.CriteriaSupporting FeatureRemarks and Explanations408.2 Visibility. Where stationary ICT provides one or more display screens, at least one of each type of display screen shall be visible from a point located 40 inches (1015 mm) above the floor space where the display screen is viewed.Not Applicable408.3 Flashing Where ICT emits lights in flashes, there shall be no more than three flashes in any one-second period.Not Applicable409 Status IndicatorsCriteriaSupporting FeatureRemarks and Explanations409.1 General. Where provided, status indicators shall be discernible visually and by touch or sound.Not Applicable410 Color CodingCriteriaSupporting FeatureRemarks and Explanations410.1 General.?Where provided, color coding shall not be used as the only means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.Not Applicable411 Audible SignalsCriteriaSupporting FeatureRemarks and Explanations411.1 General.?Where provided, audible signals or cues shall not be used as the only means of conveying information, indicating an action, or prompting a response.Not Applicable412 ICT with Two-Way Voice Communication412.1 General.?ICT that provides two-way voice communication shall conform to 412.CriteriaSupporting FeatureRemarks and Explanations412.2 Volume Gain. ICT that provides two-way voice communication shall conform to 412.2.1 or 412.2.2.See 412.2.2412.2.1 Volume Gain for Wireline Telephones. Volume gain conforming to 47 CFR 68.317 shall be provided on analog and digital wireline telephones.Not Applicable412.2.2 Volume Gain for Non-Wireline ICT. A method for increasing volume shall be provided for non-wireline ICT.Not Applicable412.3 Interference Reduction and Magnetic Coupling. Where ICT delivers output by a handset or other type of audio transducer that is typically held up to the ear, ICT shall reduce interference with hearing technologies and provide a means for effective magnetic wireless coupling in conformance with 412.3.1 or 412.3.2.See 412.3.1.412.3.1 Wireless Handsets. ICT in the form of wireless handsets shall conform to ANSI/IEEE C63.19-2011 (incorporated by reference, see 702.5.1).Not Applicable412.3.2 Wireline Handsets. ICT in the form of wireline handsets, including cordless handsets, shall conform to TIA-1083-B (incorporated by reference, see702.9.1).Not Applicable412.4 Digital Encoding of Speech. ICT in IP-based networks shall transmit and receive speech that is digitally encoded in the manner specified by ITU-T Recommendation G.722.2 (incorporated by reference, see 702.7.2) or IETF RFC 6716 (incorporated by reference, see 702.8.1).Not Applicable412.5 Real-Time Text Functionality. Reserved.Not Applicable412.6 Caller ID. Where provided, caller identification and similar telecommunications functions shall be visible and audible.Not Applicable412.7 Video Communication. Where ICT provides real-time video functionality, the quality of the video shall be sufficient to support communication using sign language.Not 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 FeatureRemarks and Explanations413.1.1 Decoding and Display of Closed Captions. Players and displays shall decode closed caption data and support display of captions.Not Applicable413.1.2 Pass-Through of Closed Caption Data. Cabling and ancillary equipment shall pass through caption data.Not 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 FeatureRemarks and Explanations414.1.1 Digital Television Tuners. Digital television tuners shall provide audio description processing that conforms to ATSC A/53 Digital Television Standard, Part 5 (2014) (incorporated by reference, see 702.2.1). Digital television tuners shall provide processing of audio description when encoded as a Visually Impaired (VI) associated audio service that is provided as a complete program mix containing audio description according to the ATSC A/53 standard.Not Applicable414.1.2 Other ICT. ICT other than digital television tuners shall provide audio description processing.Not 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 FeatureRemarks and Explanations415.1.1 Caption Controls. Where ICT provides operable parts for volume control, ICT shall also provide operable parts for caption selection.Not Applicable415.1.2 Audio Description Controls. Where ICT provides operable parts for program selection, ICT shall also provide operable parts for the selection of audio description.Not 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 FeatureRemarks and Explanations502.2.1 User Control of Accessibility Features. Platform software shall provide user control over platform features that are defined in the platform documentation as accessibility features.Not Applicable502.2.2 No Disruption of Accessibility Features. Software shall not disrupt platform features that are defined in the platform documentation as accessibility features.Supported With ExceptionsSee Table 7502.3 Accessibility Services. Platform software and software tools that are provided by the platform developer shall provide a documented set of accessibility services that support applications running on the platform to interoperate with assistive technology and shall conform to 502.3. Applications that are also platforms shall expose the underlying platform accessibility services or implement other documented accessibility services.Not Applicable502.3.1 Object Information. The object role, state(s), properties, boundary, name, and description shall be programmatically determinable.Supported With - Users who rely on Assistive Technologies may have difficulties using the Access Permission list items on the Data Link Properties dialog.- Users who rely on Assistive Technologies may have difficulties Enabling Paging the Configure ListView dialog.- Users who rely on Assistive Technologies may have difficulties adding Members in the WizardStep Collection Editor dialog.502.3.2 Modification of Object Information. States and properties that can be set by the user shall be capable of being set programmatically, including through assistive technology.Supported502.3.3 Row, Column, and Headers. If an object is in a data table, the occupied rows and columns, and any headers associated with those rows or columns, shall be programmatically determinable.Supported With - Users who rely on Assistive Technologies may have difficulties using the results table in the Test Query dialog.502.3.4 Values. Any current value(s), and any set or range of allowable values associated with an object, shall be programmatically determinable.Supported502.3.5 Modification of Values. Values that can be set by the user shall be capable of being set programmatically, including through assistive technology.Supported502.3.6 Label Relationships. Any relationship that a component has as a label for another component, or of being labeled by another component, shall be programmatically determinable.Supported502.3.7 Hierarchical Relationships. Any hierarchical (parent-child) relationship that a component has as a container for, or being contained by, another component shall be programmatically determinable.Supported502.3.8 Text. The content of text objects, text attributes, and the boundary of text rendered to the screen, shall be programmatically determinable.Supported502.3.9 Modification of Text. Text that can be set by the user shall be capable of being set programmatically, including through assistive technology.Supported502.3.10 List of Actions. A list of all actions that can be executed on an object shall be programmatically determinable.Supported502.3.11 Actions on Objects. Applications shall allow assistive technology to programmatically execute available actions on objects.Supported502.3.12 Focus Cursor. Applications shall expose information and mechanisms necessary to track focus, text insertion point, and selection attributes of user interface components.Supported502.3.13 Modification of Focus Cursor. Focus, text insertion point, and selection attributes that can be set by the user shall be capable of being set programmatically, including through the use of assistive technology.Supported502.3.14 Event Notification. Notification of events relevant to user interactions, including but not limited to, changes in the component’s state(s), value, name, description, or boundary, shall be available to assistive technology.Supported502.4 Platform Accessibility Features. Platforms and platform software shall conform to the requirements in ANSI/HFES 200.2, Human Factors Engineering of Software User Interfaces — Part 2: Accessibility (2008) (incorporated by reference, see 702.4.1) listed below:Section 9.3.3 Enable sequential entry of multiple (chorded) keystrokes;Section 9.3.4 Provide adjustment of delay before key acceptance;Section 9.3.5 Provide adjustment of same-key double-strike acceptance;Section 10.6.7 Allow users to choose visual alternative for audio output;Section 10.6.8 Synchronize audio equivalents for visual events;Section 10.6.9 Provide speech output services; andSection 10.7.1 Display any captions provided.Not Applicable503 Applications503.1 General.?Applications shall conform to 503.CriteriaSupporting FeatureRemarks and Explanations503.2 User Preferences. Applications shall permit user preferences from platform settings for color, contrast, font type, font size, and focus cursor.Supported With ExceptionsSee Table 7503.3 Alternative User Interfaces. Where an application provides an alternative user interface that functions as assistive technology, the application shall use platform and other industry standard accessibility services.Supported With ExceptionsSee Table 7503.4 User Controls for Captions and Audio Description. Where ICT displays video with synchronized audio, ICT shall provide user controls for closed captions and audio descriptions conforming to 503.4.See 503.4.1 and 503.4.2.503.4.1 Caption Controls. Where user controls are provided for volume adjustment, ICT shall provide user controls for the selection of captions at the same menu level as the user controls for volume or program selection.Not Applicable503.4.2 Audio Description Controls. Where user controls are provided for program selection, ICT shall provide user controls for the selection of audio descriptions at the same menu level as the user controls for volume or program selection.Not 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 FeatureRemarks and Explanations504.2 Content Creation or Editing. Authoring tools shall provide a mode of operation to create or edit content that conforms to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 (incorporated by reference, see 702.10.1) for all supported features and, as applicable, to file formats supported by the authoring tool. Authoring tools shall permit authors the option of overriding information required for accessibility.Supported504.2.1 Preservation of Information Provided for Accessibility in Format Conversion. Authoring tools shall, when converting content from one format to another or saving content in multiple formats, preserve the information required for accessibility to the extent that the information is supported by the destination format.Supported504.2.2 PDF Export. Authoring tools capable of exporting PDF files that conform to ISO 32000-1:2008 (PDF 1.7) shall also be capable of exporting PDF files that conform to ANSI/AIIM/ISO 14289-1:2016 (PDF/UA-1) (incorporated by reference, see 702.3.1).Not Applicable504.3 Prompts. Authoring tools shall provide a mode of operation that prompts authors to create content that conforms to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 (incorporated by reference, see 702.10.1) for supported features and, as applicable, to file formats supported by the authoring tool.Supported504.4 Templates. Where templates are provided, templates allowing content creation that conforms to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 (incorporated by reference, see 702.10.1) shall be provided for a range of template uses for supported features and, as applicable, to file formats supported by the authoring tool.SupportedChapter 6 Support Documentation and Services602 Support Documentation602.1 General.?Documentation that supports the use of ICT shall conform to 602.CriteriaSupporting FeatureRemarks and Explanations602.2 Accessibility and Compatibility Features. Documentation shall list and explain how to use the accessibility and compatibility features required by Chapters 4 and 5. Documentation shall include accessibility features that are built-in and accessibility features that provide compatibility with assistive technology.Supported602.3 Electronic Support Documentation. Documentation in electronic format, including Web-based self-service support, shall conform to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 (incorporated by reference, see 702.10.1).Supported602.4 Alternate Formats for Non-Electronic Support Documentation. Where support documentation is only provided in non-electronic formats, alternate formats usable by individuals with disabilities shall be provided upon request.Supported603 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 FeatureRemarks and Explanations603.2 Information on Accessibility and Compatibility Features. ICT support services shall include information on the accessibility and compatibility features required by 602.2.Supported603.3 Accommodation of Communication Needs. Support services shall be provided directly to the user or through a referral to a point of contact. Such ICT support services shall accommodate the communication needs of individuals with disabilities.SupportedDisability Answer DeskTablesTable 1: Info and RelationshipsTable 11.3.1 Info and Relationships: Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.WinForms Design Time scenariosVisually impaired users will not be aware of the current order of the selected property in the category. User is not blocked from navigating to other properties or categories. Azure Tools Visually impaired users may become confused with how many subscriptions are available to them when selecting subscriptions while configuring sending Application Insights from their Azure Cloud Service projects. DiagnosticsDebugging states such as Started, Stopped, Paused, and Resumed that are implied visually in Visual Studio, are not exposed programmatically to assistive technology. Customers relying on screen readers will not receive notifications that debugging has started, stopped, or entered break state. Users can read Visual Studio's title bar to determine if debugging is active or not - "Debugging" will be in the title if debugging. To determine if the debugged application is in break mode, look for the "Show Next Statement" menu item in the Debug top level menu - if it is present, the debugger is in a break state. When configuring an EXE project type, some rows in the property grid are not accurately represented as expandable items to assistive technology. Visually impaired users will not be aware that property grid category names serve as headers that can be expanded and collapsed for ease of navigation. If a category header is collapsed the visually impaired user may not be aware that a hidden property is available for use. (Bug 396251) VS IDEVisually impaired users who use Toolbox will not know how many controls are available under a category of controls, without expanding the group and navigating through each child. Architecture Tools (DPT)- Visually impaired users will face problems in Class Designer table as they will not know if a control is inside a table while editing a cell.- Visually impaired users will face problems in DSL details table as they will not know if a control is inside a table while editing a cell.Table 2: Contrast MinimumTable 21.4.3 Contrast (Minimum): The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, except for the following: ? Large Text: Large-scale text and images of large-scale text have a contrast ratio of at least 3:1;? Incidental: Text or images of text that are part of an inactive user interface component, that are pure decoration, that are not visible to anyone, or that are part of a picture that contains significant other visual content, have no contrast requirement.? Logotypes: Text that is part of a logo or brand name has no minimum contrast requirement.Visual Studio EditorThe Light, Dark and Blue visual themes provided in Visual Studio may not adhere to the minimum color contrast guidelines in the editor in all cases. Users who encounter difficulty reading text in the code editor windows should use the "Blue (Extra Contrast)" Theme. Themes can be changed by accessing the Options dialog under Tools in the main menu. Theme settings can be found in the Environment/General category. - Selected text in a WinForms DataGridView control does not contrast enough with the color of the background so users may have some difficulty reading it. - Some users may have difficulties reading the names of the properties when editing properties for items in the workflow designer in the properties pane because the text for the names do not adhere to color contrast guidelines.- Some users may have difficulties reading the names of the groups in the toolbox pane, because they do not adhere to color contrast guidelines, when using the workflow designer, which will make it difficult to find activities to add to the designer.- Some users may have difficulties editing SharePoint State Machine and Sequential workflows in the workflow designer because it does not adhere to color contrast guidelines.- Some users may have difficulties setting expressions in various places when editing workflows in the workflow designer and using the Dark theme.- Some users may have difficulty reading the selected 'Default' option in 'Edit Configurations' text field in 'SharePoint' tab of 'SharePoint Project' properties designer window and the selected 'Install SharePoint Add-in' option in 'Available Deployment Steps' text field in 'Add New Deployment Configuration' window because they do not adhere to color contrast guidelines.- Some users may have difficulties with the Publish Options dialog when publishing a Windows Desktop Classic project because it does not adhere to the color contrast guidelines.- Some users may have difficulties identifying the file names to include with the published application in the Application Files dialog when publishing a Windows Desktop Classic project because it does not adhere to the color contrast guidelines.-Some users may have difficulties with the Associated Controls list on the Data UI Customization Options dialog because it does not adhere to the color contrast guidelines.- Some users may have difficulties with the Address for a Service Reference on the Add Services dialog because it does not adhere to the color contrast guidelines.- Some users may have difficulties with the Associated Controls list box in the Customize Control Binding dialog because it does not adhere to the color contrast guidelines.- Some users may have difficulties with the Data Source list box in the Change Data Source dialog because it does not adhere to the color contrast guidelines.- Some users may have difficulties with the Data Source list box in the Choose Data Source dialog because it does not adhere to the color contrast guidelines.- Some users may have difficulties determining the selected Property on the Advanced Propertied Dialog for a Data Source connection.- In WCF Projects, when using Config editor to create a new Standard Endpoint, some users may have difficulties using the selected list item because it does not follow the color contrast guidelines.- In WCF Projects, when using Config editor to create a New Binding, some users may have difficulties using the selected list items on the Create New Binding dialog because it does not adhere to the color contrast guidelines.- Visually impaired users may not be able to determine active selection of the service templates when creating a new Service Fabric Application project.- While inspecting a performance report from the profiler, some elements may have a low amount of contrast between the foreground and background colors of the elements. Visually impaired users who require specific contrast ratios may have difficulty reading the text because of low contrast.- Selected elements in the Settings Project Property Page table do not have sufficient contrast. Table 3: KeyboardTable 32.1.1 Keyboard: All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints.WinForms Design Time scenarios- When user enters an invalid value for a property in the WinForms Designer Property Browser, they are presented with an error message box. When a user clicks the details button the dialog box expands to show the error message text. The visually impaired user will be unable to use their keyboard to reach the text so that an accessibility aid is able to read the error message.- Users with motor disabilities may have difficulty using the WinForms Design surface to add MenuStrip items to a MenuStrip. The Items Collection Editor can be used to add all types of supported elements to the MenuStrip Control.- Users will not be able to sort the various WinForms Input Masks using a keyboard to access the header items of the Input Mask Editor dialog. Workflow- Keyboard users cannot access the warning information icons on any activities in the Workflow designer.- Keyboard users cannot stretch the state control button on states in StateMachine activity in Workflow designer.- When editing the properties of an activity using the Workflow designer, keyboard users cannot collapse property groups such as 'Misc" the first time they are focused.- Keyboard users cannot connect FlowChart activities in Workflow designer.- Keyboard users cannot access the header items of arguments list in Workflow designer.- Keyboard users cannot access the "More properties" button in properties window in Workflow designer.- When editing SharePoint State Machine and Sequential workflows, the Workflow designer is not accessible by keyboard. ClickOnce (Office Tools Team)Keyboard users may have difficulties sorting the files to include with the published application in the Application Files dialog when publishing a Windows Desktop Classic project. WCFKeyboard users may have some difficulties selecting an OrderGroupsBy for a LingDataSource on the Configure Data Source dialog for a web control. Keyboard users may have some difficulties using the WCF service Configuration Editor because some elements may not be keyboard accessible and in some cases the tab and arrow keys do not work as expected. Azure Tools - Users developing an Azure Cloud Service cannot use keyboard navigation to tab to the "OK" and "Cancel" buttons when they publish their apps and configure IntelliTrace settings.- Keyboard users may be unable to sort the datagrid for web and worker role configuration settings- Visually Impaired users will be unable to sort the datagrid(s) located under the tab items in the "Diagnostics Configuration" window using the keyboard. Diagnostics- While inspecting a performance report from the profiler, users are not able to use the keyboard to navigate to all of the elements in the report. Screen reader users will have difficulty determining all the contents of the report.- While changing the IntelliTrace settings when publishing an Azure Cloud Service app, users are not able to use the keyboard to navigate to the OK button or the Cancel button. Users with visual impairments will not be able to get to these buttons via keyboard navigation. Users can, alternatively, hit Enter in lieu of the OK button and ESC in lieu of the Cancel button. (Bug 406456) VS IDEVisually impaired users who rely on screen readers will not know when Visual Studio is busy either because Visual Studio is unresponsive or busy because of a long running operation. Additionally, if the long running operation is cancellable, visually impaired users will not be able to cancel the operation. Agile Test: Automated Testing (Client UI)- Some users will not be able to sort detailed results of a load test run based on test name or scenario or any of the result table headers.- Some users will have problems accessing data of the results table in load test result details view. .NET DevExCombo boxes in the Project Property Pages are not accessible to keyboard users. Architecture Tools (DPT)Users will not be able to sort table columns using keyboard in the table DSL Details window.Table 4: Focus OrderTable 42.4.3 Focus Order If a Web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability.<<.NET DevEx>>- The focus order of elements in the Code Analysis Solution and Project Property Pages may be unexpected. - The focus order of elements in the Code Analysis Ruleset Editor may be unexpected.WinForms Design time scenarios- Users navigating the WinForms Designer Options may not be notified when the drop down for "Auto Load Controls in the ToolBox" has focus. Be advised that the user may use the keyboard up/down arrows to cycle through the available options when the text in the corresponding text box is selected.- The ToolStrips in the WinForms Property Browser and Collection Editor Dialogs allow changes in property grid layout or content using an array of buttons. Users will not be able to determine the current state of the button while navigating the ToolStrip. The button that is currently selected (navigated) would have the same colors as the button that is checked. Workflow- When defining the keys to initialize on in the Correlation Data section of an InitializeCorrelation activity in the Workflow designer, the tab order goes from right-to-left instead of left-to-right, which may be disorientating for keyboard users.- When working with the Content Definition dialog that pops up when defining content for the Receive, Send, SendReply, and ReceiveReply activities in the Workflow designer, the first tab goes to the bottom right of the dialog instead of moving left-to-right, top-to-bottom, which may be disorientating for keyboard users.- When editing SharePoint State Machine and Sequential workflows, users may find the keyboard tab order for Workflow designer controls goes in unpredictable directions, which may be disorienting for some users. WCFSome keyboard users may have difficulties using the WCF Service Configuration Editor because the tab order may not be what is expected. DiagnosticsWhile inspecting the Summary, Events, Memory Usage, or CPU Usage details view in the Diagnostic Tools window, the focus can be lost by being placed an invisible element in the window. SHIFT-TAB doesn't being focus back to the previous element, instead focus is set on an element in the middle of the Diagnostic Tools window. Screen reader users will be unable to determine the flow of the window. Table 5: Focus VisibleTable 52.4.7 Focus Visible: Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible.WinForms Design TimeThe WinForms Property Browser allows users to invoke editors to customize property values. Editors are invoked using keyboard combination Alt+Down or a dedicated button. Once navigated to the button, using TAB key, users will not be aware that the button has focus and can be invoked using Enter key. User can still use Alt-Down key combination to invoke the editor. Workflow- Keyboard users may not be able to determine which control is focused when adding new variables into the Variables pane in the Workflow designer.- Keyboard user may not be able to see which control is focused when adding new parameters into the Content Definition window that pops up when defining content for Send, Receive, SendReply, and ReceiveReply activities in the Workflow designer.- Keyboard users may not be able to see which control is focused when adding new keys into the Initialize On section in the Initialize Correlation windows that pops up when setting CorrelationData on the InitializeCorrelation activity in the Workflow designer.- Keyboard users may not be able to see which control is focused when adding new arguments into the DelegateArguments window that pops up when setting DelegateArguments on the InvokeDelegate activity in the Workflow designer.- Keyboard users may not be able to tell that they've selected the Request field when tabbing through the ReceiveReply or SendReply (usually labeled "ReceiveReplyForSend" and "SendReplyToReceive" respectively) activities in the Workflow designer. This field is disabled and should not get keyboard focus.- When defining the content of a Receive, ReceiveAndSendReply, Send, or SendAndReceiveReply activity in the workflow designer, the grid under the Parameters section in the Content Definition dialog has an inconsistent tab order on fields that accept expressions such as Value or Assign to.- When defining the keys to initialize on in the Correlation Data section of an InitializeCorrelation activity in the Workflow designer, the tab order for the Value field is inconsistent.- When editing a workflow in the Workflow designer, the user can specify default values for variables or arguments using the Variables or Arguments panes in the workflow designer. Keyboard users may not be able to tell when they've selected the right field because they need to tab three times in the table cell.- When editing SharePoint State Machine and Sequential workflows, some users may not be able to tell which control they're on in the Workflow designer controls. SharePoint Tools (Office Tools Team)- Some users may not be able to determine which control has keyboard focus in SharePoint AppManifest.xml file window.- Users with motor disabilities who rely on the keyboard will get confused when the focus is invisible in the view links in Workflow activity properties window.- The focused button may not be easily distinguishable from other buttons when configuring Task options in SharePoint projects while using high contrast themes.- When configuring the manifest in a SharePoint or Office Add-in projects, certain grids may show multiple controls being selected at the same time. Because of this, users may not be able to distinguish which control currently has focus. - Some users may not be able to determine which item has keyboard under in Entity Set Name dropdown control on the Config Data Selection dialog. - Some users may not be able to determine which item has keyboard in the Table dropdown control when configuring LingDataSource for controls on the Config Data Selection dialog. VS Data Tools (Office Tools Team)When adding a connection to a ODBC Data Source in your project or in Server Explorer, keyboard users may have difficulties determining which control has focus on the Select Data Source window. Azure Tools Some users may have difficulty setting the transfer period for Azure cloud service project diagnostic configuration as narrator does not read it as a combo boxArchitecture Tools (DPT)Users who rely on keyboard will get confused in the Text Templating option in Visual Studio Options dialog as the keyboard focus seems to be on the text and not the combo box. Diagnostics- When opening a memory heap analysis window from either the Diagnostic Tool Window's memory tool or the Debug Managed Memory dump debugging feature, the initial keyboard focus is set to a parent container that has the narrative text of the path to a file on disk. This will also happen when selecting a snapshot to diff against, or when the user tabs off of the last element in the view. This focus element can be disorienting to users, as they are not alerted to where the tool has taken them. In the meantime, pressing tab will return focus to the tool as expected.- While inspecting a performance report from the profiler, the focus indicator can be lost when placed on elements in the report. Users who rely on the keyboard to operate the report will have difficulty determining the component on which keyboard operations will interact. - While inspecting the Diagnostic Tools window, the focus indicator can be lost when focus is placed on an invisible element. Users who rely on the keyboard to operate the page will have difficulty determining the component on which keyboard operations will interact. Table 6: Name, Role, ValueTable 64.1.2 Name, Role, Value: For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies.VS IDE- Visually impaired users relying on screen readers will not be able to distinguish between menus and toolbar buttons that can be toggled from those that cannot.- On certain tool windows, like diagnostic tools and in the Visual Studio web browser, keyboard users will have to tab one extra time to get keyboard focus into the control because the entire control hosting HTML content takes focus. Additionally, visually impaired users relying on screen readers will hear the entire path to the HTML file on disk or url of the webpage if the content is rendered from a website. WinForms Design Time Scenarios- Visually impaired users developing Winforms applications will not be informed of the option to add alternative UI elements to their MenuStrips. Instead, they will only be informed of the ability to add text menu items. Users have the option to use the Menu Collection Editor to more efficiently add menu items to their MenuStrips.- Visually impaired users of WinForms Designer who are accessing control properties using Property Browser will see two controls, edit and a button. Edit control allows immediate editing of property value; button allows invocation of custom editor for value selection. User is not blocked from achieving any actions.- When setting up databinding for a WinForms control, user might open a "Formatting and Advanced Binding" dialog in the WinForms Designer and navigate through the list of all properties available on this control to select which one to bind to a data source. While all control properties are accessible to an AT user (names are announced in Narrator and properties can be selected), an AT user does not know how many properties are available and when they reach the end on the list.- The WinForms Designer provides users with Collection Editors to easily add items to a variety of container controls like ToolStrips, MenuStrips and TreeViews. The Collection Editor contains a standard WinForms property grid with a ToolStrip. Visually impaired users may not be able to determine the state of the ToolStrip's toggle buttons and will need to enter the contained property grid to determine its layout.- Narrator may fail to announce whether the Components List at the top of the WinForms Property Browser is expanded or collapsed, leading to confusion over its actual state. The user does have the ability to use keyboard commands alt + down arrow to expand the combo box and select the desired control.- When a visually impaired user enters an invalid value in a property in the WinForms property grid they will not be informed that the Details button of Error Message dialog box expands or collapses the current window and may dismiss the window without having Narrator narrate the error message.- Visually impaired users may not be able to properly use the Type Name Display button to change how a control appears in the WinForms Document Outline Window. Without this, the visually disabled user will be left using the default view containing control's name and simple Type, e.g. Button rather than the fully qualified type, e.g. System.Windows.Forms.Button, or no type at all.- Visually impaired users will not be aware that property grid category names serve as headers that can be expanded and collapsed for ease of navigation. If a category header is collapsed the visually impaired user may not be aware that a hidden property is available for use. All properties are available for use if the property view mode is changed to alphabetical view.- Visually impaired users will not hear detailed help text information about each property in the WinForms Designer options property grid of the Tools-Options Dialog Box or the WinForms Designer. Hitting the F1 key will launch the users default browser with detailed help documentation about the active property.- The WinForms Property Browser ToolStrip contains buttons to change the layout of the Property Browser from categorized to alphabetized and from control properties to control events. Visually impaired users may not be able to determine the state of these toggle buttons and will need to enter the Property Browser to determine its layout.- Visually impaired users developing Winforms applications will not be informed of the option to add alternative UI elements to their MenuStrips. Instead, they will only be informed of the ability to add text menu items. Users have the option to use the Menu Collection Editor to more efficiently add menu items to their MenuStrips.Office Tools- Users who rely on Assistive Technologies may have difficulties selecting the Start Action for an Office Add-in project. - When creating a VSTO Workbook or Document project the "Visual Studio Tools for Office Project wizard" allows users to select which file format they want to use when creating the file. Users who rely on Assistive Technologies may have difficulties identifying that the "Format" drop down menu is expandable.- When you start debugging in an Outlook web Add-in Visual Studio prompts the customer for sign in information. Some of the options in this window are under the "Advanced" section, which is a region expandable by pressing the button labeled "Advanced". Users who rely on Assistive Technologies may have difficulty determining that the "Advanced" button expands a new section to reveal more controls.- When publishing a VSTO project the Updates dialog allows users to select how often want to check for updates in their Add-in. Some users may have difficulties identifying that the drop- down menu that allows you to change the unit of time is expandable.- When you create a new VSTO Excel Add-in you are prompted to enable access to the Microsoft Office Visual Basic for Application project system. This prompt is a Warning dialog but Users who rely on Assistive Technologies may have difficulties identifying that the dialog is a warning. Workflow- Users who rely on Assistive Technologies may have difficulties determining when a connector has focus in the FlowChart activity in the Workflow designer.- Users who rely on Assistive Technologies may have difficulties determining the name of the context menu when they right click on any workflow activities in the Workflow designer.- Users who rely on Assistive Technologies may have difficulties determining which property currently has focus in the Properties window in the Workflow designer.- Users who rely on Assistive Technologies may have difficulties determining that the Clear Search button or Expression Editing dialog button on the Properties window has focus in the Workflow designer.- Users who rely on Assistive Technologies may have difficulties adding an annotation to FlowDecision activity in the workflow designer.- Users who rely on Assistive Technologies may have difficulties changing the zoom percentage of the Workflow designer from status bar.- Some users may have difficulties selecting the transition destination in Transition Designer in the Workflow designer.- Users who rely on Assistive Technologies may have difficulties selecting a Transition in the Transition window in the Workflow designer.- Users who rely on Assistive Technologies may have difficulties selecting the Exception type when working with TryCatch activity in the Workflow designer.- Users who rely on Assistive Technologies may have difficulties working with the parallel separator in Parallel or Pick activities in Workflow designer.- Users who rely on Assistive Technologies may have difficulties working with FlowSwitch or CorrelationScope activities in the Workflow designer. - Users who rely on Assistive Technologies may have difficulties defining the contents of a Receive activity in the Workflow designer. - Users who rely on Assistive Technologies may have difficulties selecting a target type for the InvokeMethod activity in the Workflow designer.- Users who rely on Assistive Technologies may have difficulties adding an activity into the Finally section of a TryCatch activity in Workflow designer.- Users who rely on Assistive Technologies may have difficulties determining that the separator bar on "Add Correlation Initializers" window has focus in the Workflow designer.- Users who rely on Assistive Technologies may have difficulties configuring parameters in the Content Definition window in Workflow designer, which is used by Receive and Send activities.- Users who rely on Assistive Technologies may have difficulties updating the Message Queue field on the CorrelatesOn definition window for the Send and RecieveReply activity in the Workflow designer.- Users who rely on Assistive Technologies may have difficulties working with FlowDecision activity in Workflow designer.- Users who rely on Assistive Technologies may have difficulties configuring the Invoke Delegate activity in the Workflow designer.- Users who rely on Assistive Technologies may have difficulties selecting to search "By Category" or "Alphabetical" in property window in Workflow designer.- Users who rely on Assistive Technologies may have difficulties determining that the Select Types window for dictionary activities has focus in the Workflow Designer.- Users who rely on Assistive Technologies may have difficulties being able to select the Types or Values on the Select Types window for Dictionary activities in SharePoint Workflow designer.- Users who rely on Assistive Technologies may have difficulties determining that the "Browse And Select .Net Type" window has focus in the Workflow Designer.- Users who rely on Assistive Technologies may have difficulties defining Dynamic Values for a Workflow activity in the Workflow Designer.- Users who rely on Assistive Technologies may have difficulties working with properties in the Properties window for the GetDynamicValueProperties activity in SharePoint Workflow designer.- Users who rely on Assistive Technologies may have difficulties using determining when they have focused on the workflow buttons in the Content Definition window in Workflow designer.- Users who rely on Assistive Technologies may have difficulties when navigating through the activities in the Workflow designer. SharePoint Tools (Office Tools Team)- Users who rely on Assistive Technologies may have difficulties editing the App Manifest with the Manifest designer in a SharePoint project.- Users who rely on Assistive Technologies may have difficulties configuring Views for a SharePoint List with the List designer in a SharePoint project.- Users who rely on Assistive Technologies may have difficulties configuring columns for a SharePoint List with the List designer in a SharePoint project.- Users who rely on Assistive Technologies may have difficulties configuring columns for a Content Type with the Content Type designer in a SharePoint project.- Users who rely on Assistive Technologies may have difficulties selecting what the Custom Action is scoped to when creating a new Custom Action for a Ribbon in a SharePoint project.- "Learn more about sandboxed solutions" may be announced twice as the name of the hyperlink on the SharePoint Customization Wizard by some screen readers.- Users who rely on Assistive Technologies may have difficulties configuring a Remote Event Receiver using the SharePoint Customization Wizard in a SharePoint project.- Users who rely on Assistive Technologies may have difficulties selecting which base content type a new Content Type should inherit from using the SharePoint Customization Wizard in a SharePoint Add-In project.-Users who rely on Assistive Technologies may not be able to select which lists will be used for debugging with the SharePoint Customization Wizard when adding a new List Workflow to a SharePoint project.- Users who rely on Assistive Technologies may not be able to associate a Workflow with the correct Lists or Libraries using the SharePoint Customization Wizard in a SharePoint project.- Users who rely on Assistive Technologies may not be able update some properties on the SharePoint tab of the Project Properties window for a SharePoint Add-in project.- Users who rely on Assistive Technologies may have difficulties viewing the details of a Business Data Connectivity method in the BDC Method Details window in a SharePoint project.- Users who rely on Assistive Technologies may not be able to determine that the hyperlink "Learn more about debugging via Microsoft Azure Service Bus" is not editable in "New SharePoint Add-in" window in SharePoint project properties window.- Users who rely on Assistive Technologies may have difficulties configuring a Custom Action when adding a Custom Action for a Menu to a SharePoint project.- Users who rely on Assistive Technologies may have difficulties selecting a workflow from the list on the SharePoint Customization Wizard dialog when creating a SharePoint project using either the Import Reusable 2010 Workflow or the SharePoint Import Solution Package templates.WCF- In WCF Service Library projects, users who rely on Assistive Technologies may have difficulties knowing which Referenced Assemblies have been selected on the WCF Options Advanced Contract Code Generation settings dialog.- Users who rely on Assistive Technologies may have difficulties using the WCF Service Configuration Editor. ClickOnce (Office Tools Team)- Users who rely on Assistive Technologies may have difficulties using the Application Files dialog when publishing a Windows Desktop Classic project.- Users who rely on Assistive Technologies may have difficulties choosing the Signature Algorithm on the Create Test Certificate dialog when publishing a Windows Desktop Classic project.- Users who rely on Assistive Technologies may have difficulties selecting which Zone the application will be installed to when publishing a Windows Desktop Classic project.- Users who rely on Assistive Technologies may have difficulties choosing the Prerequisites when publishing a Windows Desktop Classic project.- Users who rely on Assistive Technologies may have difficulties selecting a Certificate from the Store to use for signing when publishing a Windows Desktop Classic project.- Users who rely on Assistive Technologies may have difficulties selecting the File Associations on the Public Options dialog when publishing a Windows Desktop Classic project. VS Data Tools (Office Tools Team)- Users who rely on Assistive Technologies may have difficulties adding or updating a Service Refence from the context menu in Solution Explorer.- Users who rely on Assistive Technologies may have difficulties using the Discover button on the Add Service Reference.- Users who rely on Assistive Technologies may have difficulties using the toolbar buttons on the Data Sources window.- Users who rely on Assistive Technologies may have difficulties selecting the Connection String on the Data Source Configuration wizard.- Users who rely on Assistive Technologies may have difficulties selecting the Data Type on the Customize Control Binding dialog.- Users who rely on Assistive Technologies may have difficulties selecting the Access Level for Generated Classes in the Service Reference Settings dialog.- Users who rely on Assistive Technologies may have difficulties selecting the Data Type in the Data UI Customization tab of the Options dialog.- Users who rely on Assistive Technologies may have difficulties selecting the Data Provider in the Choose Data Source dialog.- Users who rely on Assistive Technologies may have difficulties selecting the Authentication in the Connection Properties dialog.- Users who rely on Assistive Technologies may have difficulties selecting the Data Source Table in the Search Criteria Builder dialog.- Users who rely on Assistive Technologies may have difficulties selecting which Data Connection should be used in the Table Adapter Configuration Wizard.- Users who rely on Assistive Technologies may have difficulties using the Configure Data Source Wizard.- Users who rely on Assistive Technologies may have difficulties using the toolbar buttons and the context menus on the Server Explorer window.- Users who rely on Assistive Technologies may have difficulties using the context menus in the Dataset designer.- Users who rely on Assistive Technologies may have difficulties using the Preview Data dialog.- Users who rely on Assistive Technologies may have difficulties selecting either a User or System data source for an ODBC data source in Add Connection dialog.- Users who rely on Assistive Technologies may have difficulties using the Query Builder dialog. Users that rely on Assistive Technologies may have difficulties choosing the field type for a new field in the DetailsView control. Azure Tools - Visually impaired users may get confused with inappropriate name and LocalizedControlType values for elements under the "Applications and Services" grid in the Service Fabric "Edit Versions" window.- Visually impaired users may have difficulties when clicking the Add/Delete Resource button in the Azure RM JSON outline window - Visually impaired users may not be able to set the transfer period time correctly in diagnostics configuration for azure cloud service web and worker roles.- Visually impaired users may have trouble understanding the descriptions and status of items in the Microsoft Azure Activity Log tool window- Some users may have difficulty setting the Resource Group while configuring an Application Insights Resource in an Azure Cloud Service project- Visually impaired users may not be able to set Diagnostic Configurations properly for an Azure Cloud Service Project- Visually impaired users may have difficulties using the ETW provider's Diagnostic Events document window after creating an Azure Cloud Service Project.- Visually impaired users may not be able to know the what the setting name they are editing in a cloud service role configuration.- Visually Impaired users may not be able to configure remote desktop properly while deploying cloud applications- Visually impaired users will have difficulty knowing what setting name they are editing in a cloud service role configuration for local Storage, Certificates, Settings and Endpoints- Visually impaired users may hear an additional option related to "Collecting data from Application running on Internet Information Services" when enabling Intellitrace during the publishing of their cloud services application. - Visually impaired users may believe there are more subscriptions selectable than actually exist when publishing a cloud service- Visually impaired users may not be able to Add a new storage account from the Server Explorer- Visually impaired users will not be read the correct descriptions and values within the blob container editor window- Visually impaired users may not be able to create a port name in endpoint settings or availability set during VM creation- Visually impaired users may have issues understanding the descriptions , values, and titles of data in the Virtual Machine configuration dialog - Visually impaired users may not be able to choose the account correctly in the Create Storage Connection string dialog for Cloud Service project configuration- Visually impaired users may have difficulties when attempting to set properties of a Docker compose project.- Visually impaired users may get confusing control types when attaching to an Azure cloud service on a virtual machine via Server Explorer. Agile Test: Automated Testing (Client UI)- Visually impaired users will not understand usage of the control used to increase or decrease the retention of web test results as name of the element is incorrect.- Visually impaired users will be not be aware of the request details of a web test recording as help text of the individual request in requests grid is not meaningful and doesn't convey the context.- Visually impaired users will find difficulty in understanding lengthy name property of load test manager pane.- Visually impaired users may not understand whether the node in UIMap hierarchy has descendant nodes as expand and collapse button's localized control type is rendered as "Custom" Agile Test: Test Platform- Visually impaired users will have problem is in getting the state for DataCollector checkbox in the Data and Diagnostics step in the TestSettings UI.- Visually impaired users would not know if the control is inside a table, when trying to choose the DataCollector in the Data and Diagnostics step in the test settings UI.- Visually impaired users will not know if IntelliTest toolbar buttons can be toggled.- Visually impaired users will have a problem in assessing the number of tests in the test explorer under any category. Architecture Tools (DPT)- Visually impaired users will face inconvenience as narrator will not tell the name of the DSL Details tool bar-Visually impaired users will face inconvenience as narrator will not tell the toggle state of the buttons in the DSL Details tool bar- Visually impaired users will face problem in DSL details table as the narrator is not announcing the row and column information at each cell. Diagnostics- While changing the IntelliTrace settings when publishing an Azure Cloud Service app, some UI elements are defined programmatically but they are not visible. Users with visual impairments will find it difficult to identify these elements. - While inspecting a performance report from the profiler, some UI elements have poor values for accessibility properties. Data tables in the report aren't defined as tables, and expandable items in the report aren't defined as expandable, for example. Screen reader users will be unable to determine the state or nature of all the elements in the report. - While inspecting the Diagnostic Tools window, focus can be set to one of two invisible elements in the window which both have long values for the Name property of each element. The values in each Name property include the full path to a file on disk ("file://C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\CommonExtensions\Platform\DiagnosticsHub\WebViews\PerformanceDebuggerSwimLanesView.html" for example). Screen readers will ready the lengthy text of the Name property which is not related to the contents of the window. .NET DevEx- Combo boxes in the Project Property Pages are not accessible to keyboard users.- Dropdown buttons in the Project Property Pages do not read the correct name in screen readers.- Uneditable combo boxes in the Project Property Pages will appear to be editable to screen readers.- Table elements in the Project Property Pages will appear to have no meaningful control type to screen readers.- The Project Property Pages pane is not properly announced by screen readers.Table 7: No Disruption of Accessibility FeaturesTable 7502.2.2 No Disruption of Accessibility Features Software shall not disrupt platform features that are defined in the platform documentation as accessibility features.503.2 User Preferences Applications shall permit user preferences from platform settings for color, contrast, font type, font size, and focus cursor.503.3 Alternative User Interfaces Where an application provides an alternative user interface that functions as assistive technology, the application shall use platform and other industry standard accessibility services.- When user enters an invalid value for a property in the WinForms Designer Property Browser, they are presented with an error message box. Text on the selected buttons in this message box may be not contrasting enough and difficult to read for a visually impaired user in a High Contrast theme. The selected button does not use color defined by the Operating System for selected text. Button text is fully visible when not selected, the user will be able to read the button text if they move focus away from this button.- Users navigating general WinForms Designer Options dialog in High Contrast theme may not distinguish the focus rectangle around an actionable element and may not perceive that this control is actionable because it is using color that is defined by the Operating System as a disabled element background color. This might preclude the user from discovering additional options. However, by default all options are fully visible because all lists are expanded.- When working with various WinForms container controls and their items collections using a Collection Editor dialog in High Contrast theme the user may find that the text on selected buttons is difficult to read because these buttons are not using selected background color that is provided by the Operating System services. User may also not realize that the button is selected. Text is readable when these buttons are not selected.- In High Contrast theme users configuring their WinForms applications to use login, roles and profile services may be presented with controls that appear to be enabled when the control is disabled. The affected controls are not using disabled text color provided by the Operating System. The user needs to click the "Enable client application services" checkbox to enable the remaining controls. - When adding a new Inherited Form or Control to a project, using an “Inheritance Picker” dialog users in High Contrast theme may have difficulty reading the text on a selected button. The selected button is not using the foreground color provided by the Operating System. Text can be read when button is unselected. - The WinForms Document Outline Window provides a the TypeName Display button to allow users to select how control types display in the main portion of the Window. In High Contrast Mode users may not be able to see the down arrow indicating that the button is a drop-down button. They will also not be able to see the check mark indicating which option is selected once the drop down is expanded. However, if the user hovers their mouse over each option the color changes allowing the user to see the check marks. This is happening because these controls are not using selected text color provided by the operating system. - When editing WinForms components in the Component Tray of a WinForms Designer in a High Contrast theme, the selection rectangle is not fully visible around the selected item. The reason is that selected item is not using the selected background color provided by the Operating System. If the user cannot determine which component is active, the component dropdown in the property browser may be used to set selection on the desired component. - Disabled text may be difficult to read when setting up data binding properties of WinForms controls in the Formatting and Advanced Binding Dialog of the WinForms Designer when the user is in High Contrast Mode. Multiple controls in this page are not using the disabled text color provided by the Operating System. - Users of WinForms Designer who are accessing control properties using Property Browser and TypeEditors associated with the TextAlign property or Anchor property in High Contrast theme will have difficulty distinguishing which property value is selected in that drop down because this control is not using selected color provided by the Operating System. The value for this property can be set and viewed in the Property Browser by reading the contents of the text edit field or in the code.Users of Visual Studio who open the PropertyGrid to access component properties or options in High Contrast theme may find it difficult to recognize that some buttons in the toolstrip associated with the PropertyGrid are disabled because they do not use disabled control colors provided by the Operating System.- When you add a ListObject control to a VSTO Excel Workbook project a dialog box shows asking which cells you want to include in the ListObject. Controls in this prompt may not be correctly read by screen readers.- Some uses may have difficulties determining the status of the RibbonType property when using the VSTO Visual Ribbon designer.- Some users may have difficulties using some highlighted buttons in VSTO wizards when using High Contrast mode.- Some users may not be able to distinguish the colors of the selected buttons against the background in the SharePoint project Properties window in High Contrast mode.- The drop-down button in the Search field of the SharePoint BDC Explorer may not be visible in High Contrast mode.- The properties on the Property Editor dialog for a BDC Method in a SharePoint project may not be visible in High Contrast mode.- The Site URL field on the SharePoint Publish dialog may not be visible in High Contrast mode.When creating and using SharePoint projects in Visual Studio various wizards are used. In these wizards, the text is not always readable on the selected button when using high contrast themes.- It may not be easy to distinguish which TextBox has focus when configuring Task options in SharePoint Workflow projects while using high contrast modes. Some users may have difficulties using the Data Source Configuration Wizard when using contrast modes. - Some users might not be able to see the "Expand All" and "Collapse All" buttons in the Workflow designer in High Contrast Mode.- Some users may have difficulties updating the list of arguments in the Arguments window in the Workflow designer in High Contrast mode.- Some users may have difficulties determining that the Clear Search button in Properties window of Workflow designer has focus in High Contrast mode.- Some users will not be able to identify that the "OK" button in Expression Editor is selected in the Workflow Designer in High Contrast mode.- Some users may have difficulties determining that the ellipsis "…" button is selected in the Properties window in High Contrast mode in the Workflow designer.- Some users may have difficulties determining which tab at the bottom of the Workflow designer is selected in High Contrast mode.- Some users may have difficulties determining that the connecting lines in Flowchart activity in Workflow designer are disabled in High Contrast mode.- The title for activities in Workflow designer may not be visible to some users in High Contrast mode.Some users may have difficulties editing SharePoint State Machine and Sequential workflows with the Workflow designer in high contrast mode. - The text in the Selected "Zoom combo box" in Workflow Designer may not be visible to some users in High Contrast Mode.- In High Contrast mode users will see a different button for the tree view of the "Browse and Select .Net Type" window of the Workflow designer. The different button may be confusing to some users. - Some users may have difficulties using the context menu in Workflow designer when the menu item is focused in High Contrast mode.- The focus may not be visible on expander controls when configuring Task options in SharePoint projects while using high contrast themes. - In WCF Projects, when using Config editor to create a new Standard Endpoint, some users may have difficulties using the buttons on the wizard in High Contrast mode.- In WCF Projects, when using Config editor to create a new Endpoint, some users may have difficulties using the buttons on the wizard in High Contrast mode.- In WCF Projects, when using Config editor to create a new Service, some users may have difficulties using the buttons on the New Service Element wizard in High Contrast mode.- In WCF Projects, when using Config editor to create a new Client, some users may have difficulties using the buttons on the New Client Element wizard in High Contrast mode.- In WCF Projects, when using Config editor to create a new Binding, some users may have difficulties using the buttons on Create a New Binding dialog in High Contrast mode.- In WCF Projects, when using Config editor to config a new Endpoint Behavior, some users may have difficulties using the buttons on the behavior configuration dialog in High Contrast mode.- In WCF Service Library project, some users may have difficulties using the buttons on WCF Options and Publish dialogs in High Contrast mode. - In WCF Service Library projects, some users may have difficulties determining which Settings pane is selected on the Advanced Contract Code Generation Settings dialog in High Contrast Mode.- Keyboard users may have some difficulties using the WCF service Configuration Editor because some elements may not be keyboard accessible and in some cases the tab and arrow keys do not work as expected.Some users may have difficulties using the WCF Service Configuration Editor in High Contrast mode. - Users who rely on Assistive Technologies may have difficulties choosing the Prerequisites for an application when publishing a Windows Desktop Classic project.- Some users may have difficulties detecting the Browse button in the Publish Wizard when publishing a Windows Desktop Classic project in High Contrast mode.- Some users may have difficulties detecting the Change Password, Select From Store, and the Select from Files buttons on the Signing Properties page for a Windows Desktop Classic project in High Contrast mode.- Some users may have difficulties detecting the Advanced and the Edit Permissions XML buttons on the Security Properties page for a Windows Desktop Classic project in High Contrast mode. - Some users may have difficulties detecting the Browse and Application Files buttons on the Publish Properties page for a Windows Desktop Classic project in High Contrast.- Some users may have difficulties changing the password for a signed assembly using the Change Password dialog when publishing Windows Desktop Classic project in High Contrast mode.- Some users may have difficulties using Application Files dialog when publishing Windows Desktop Classic projects in High Contrast mode.- Some users may have difficulties using the New Group dialog when publishing Windows Desktop Classic projects in High Contrast mode.- Some users may have difficulties using the Prerequisites dialog when publishing Windows Desktop Classic projects in High Contrast mode.- Some users may have difficulties using the Applications Updates dialog when publishing Windows Desktop Classic projects in High Contrast mode.- Some users may have difficulties using the Publish Options dialog when publishing Windows Desktop Classic projects in High Contrast mode.- Some users may have difficulties using the Advanced Security Settings window when publishing Windows Desktop Classic projects in High Contrast mode. - Users who rely on Assistive Technologies may have difficulties using Customize Control Binding dialog for WPF projects.- Users who rely on Assistive Technologies may have difficulties selecting Services in the Add Service Reference dialog.- Some users may have difficulties using some of the buttons on the Add Service Reference, Add Web Reference and the Service Settings dialogs in High Control mode.- Some users may have difficulties using some of the buttons on the Data Source Configuration wizard dialog in High Control mode. - Some users may have difficulties using some of the buttons on the Table Adapter Query Configuration wizard dialog in High Control mode.- Some users may have difficulties using the buttons on Data UI Customization tab of the Options dialog in High Control mode.- Some users may have difficulties using the buttons on Customize Control Binding dialog in High Control mode.- Some users may have difficulties using Advanced Properties dialog for a Data Connection in High Control mode.- Some uses may have difficulties with the buttons on the Add Service Reference Error window do not follow the recommended contrast guidelines.- Some users may have difficulties using some of the buttons on the Preview Data window, Unique Constraint window, Search Criteria window and the Relation window in High Control mode.- Some users may have difficulties using some of the buttons on the Table Adapter Configuration wizard dialog in High Control mode.- Some users may have difficulties using the Advanced Properties dialog for a Data Connection in High Contrast mode.- Some uses may have difficulties with the buttons on the Add Service Reference Error window because they do not follow the recommended contrast guidelines. - Visually impaired users may not be able to discern the appropriate property page when setting properties on a Docker compose project.- Visually impaired users may not be able determine the keyboard focus for the Advanced Connection parameters expandable region when publishing a service fabric application.- Visually Impaired users with High Contrast settings enabled might not recognize that the sort order in the Service Fabric Edit Upgrade Settings table can be changed. - Visually impaired users may not be able to configure cloud project diagnostics as keyboard focus indicator is not available on all controls in the dialog- Visually impaired users may not be able to determine if the More Options expander has focus on the Remote Desktop configuration dialog of a Cloud Service project- Visually impaired users will have issues seeing the keyboard navigation focus when adding new roles to the cloud service project.- When deploying an ARM template to a resource group, visually impaired users may not be able to distinguish informational icons.- Visually impaired users may have difficulties using the ETW provider's Diagnostic Events document window in high contrast settings after creating an Azure Cloud Service Project.- Visually impaired users may have trouble reading some controls when configuring cloud project diagnostics in high contrast settings.- Visually impaired users may have trouble reading some controls when filtering blobs in Azure blob storage from the Server Explorer. - Visible focus indicators will not be appearing in tables in the Project Property Pages - Buttons in the Project Property Pages have poor contrast when selected in High Contrast modes. Disclaimer? 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.

Google Online Preview   Download