Section 1 Scope .windows.net



EN 301 549 Accessibility Declaration of ConformanceDate: 7 August 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. Website: Visual StudioContact for more information: Enterprise Disability Answer DeskFor assistance with this report, please email us.Section 1 ScopeThis EN 301 549 Product Accessibility Conformance specifies the functional accessibility requirements applicable to Microsoft ICT products and services.Section 2 ReferencesEN 301 549 ReferencesSection 3 Definitions and abbreviationsEN 301 549 Definitions and abbreviationsSection 4 Functional StatementsEN 301 549 Functional StatementsFunctional Accessibility RequirementsSection 5 Generic RequirementsCriteriaSupporting FeaturesRemarks and Explanations5.1.2.2 – 5.1.6.2Not ApplicableClosed Functionality5.2 Activation of accessibility featuresWhere ICT has documented accessibility features, it shall be possible to activate those documented accessibility features that are required to meet a specific need without relying on a method that does not support that need.Supported5.3 BiometricsWhere ICT uses biological characteristics, it shall not rely on the use of a particular biological characteristic as the only means of user identification or for control of ICT.Not Applicable5.4 Preservation of accessibility information during conversionWhere ICT converts information or communication it shall preserve all documented non-proprietary information that is provided for accessibility, to the extent that such information can be contained in or supported by the destination format.Supported5.5.1 Means of operationWhere ICT has operable parts that require grasping, pinching, or twisting of the wrist to operate, an accessible alternative means of operation that does not require these actions shall be provided.Not Applicable5.5.2 Operable parts discernibilityWhere ICT has operable parts, it shall provide a means to discern each operable part, without requiring vision and without performing the action associated with the operable part.Not Applicable5.6.1 Tactile or auditory statusWhere ICT has a locking or toggle control and that control is visually presented to the user, the ICT shall provide at least one mode of operation where the status of the control can be determined either through touch or sound without operating the control.Not Applicable5.6.2 Visual statusWhen ICT has a locking or toggle control and the control is non-visually presented to the user, the ICT shall provide at least one mode of operation where the status of the control can be visually determined when the control is presented.Not Applicable5.7 Key repeatWhere ICT with key repeat is provided and the key repeat cannot be turned off:a) the delay before the key repeat shall be adjustable to at least 2 seconds; andb) the key repeat rate shall be adjustable down to one character per 2 seconds.Not Applicable5.8 Double-strike key acceptanceWhere a keyboard or keypad is provided, the delay after any keystroke, during which an additional key-press will not be accepted if it is identical to the previous keystroke, shall be adjustable up to at least 0,5 seconds.Not Applicable5.9 Simultaneous user actionsWhere ICT uses simultaneous user actions for its operation, such ICT shall provide at least one mode of operation that does not require simultaneous user actions to operate the ICT.SupportedSection 6 ICT with two-way voice communicationThis section does not apply to Visual Studio 2017.Section 7 ICT with video capabilitiesThis section does not apply to Visual Studio 2017.Section 8 HardwareThis section does not apply to Visual Studio 2017.Section 9 WebThis section does not apply to Visual Studio 2017.Section 10 Non-web documentsThis section does not apply to Visual Studio 2017.Section 11 SoftwareCriteriaSupporting FeaturesRemarks and Explanations11.2.1.1 Non-text content (screen reading supported)Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy the Success Criterion in WCAG 2.0 Table 1.1.1.Supported With ExceptionsWorkflowSome users may have difficulties determining where breakpoints are set in a Workflow in the Workflow designer.11.2.1.2 Audio-only and video-only (pre-recorded)Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading and where pre-recorded auditory information is not needed to enable the use of closed functions of ICT, it shall satisfy the Success Criterion in Table 11.2: Audio-only and video-only (pre-recorded):For pre-recorded audio-only and pre-recorded video-only media, the following are true, except when the audio or video is a media alternative for text and is clearly labelled as such:Pre-recorded Audio-only: An alternative for time-based media is provided that presents equivalent information for pre-recorded audio-only content.Pre-recorded Video-only: Either an alternative for time-based media or an audio track is provided that presents equivalent information for pre-recorded video-only content.Not Applicable11.2.1.3 Captions (pre-recorded)Where ICT is non-web software that provides a user interface, it shall satisfy the Success Criterion in Table 11.3: Captions (pre-recorded):Captions are provided for all pre-recorded audio content in synchronized media, except when the media is a media alternative for text and is clearly labeled as such.Not Applicable11.2.1.4 Audio description or media alternative (pre-recorded)Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy the Success Criterion in Table 11.4: Audio description or media alternative (pre-recorded:An alternative for time-based media or audio description of the pre-recorded video content is provided for synchronized media, except when the media is a media alternative for text and is clearly labeled as such.Not Applicable11.2.1.5 Captions (live)Where ICT is non-web software that provides a user interface, it shall satisfy the Success Criterion in Table 11.5. Captions (live):Captions are provided for all live audio content in synchronized media.Not Applicable11.2.1.6 Audio description (pre-recorded)Where ICT is non-web software that provides a user interface, it shall satisfy the Success Criterion in Table 11.6: Audio description (pre-recorded):Audio description is provided for all pre-recorded video content in synchronized media.Not Applicable11.2.1.7 Info and relationshipsWhere ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy the Success Criterion in Table 11.7: Info and relationships:Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.Supported With ExceptionsSee Table 111.2.1.8 Meaningful sequenceWhere ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy the Success Criterion in Table 11.8: Meaningful sequence:When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined.Supported11.2.1.9 Sensory characteristicsWhere ICT is non-web software that provides a user interface, it shall satisfy the Success Criterion in Table 11.9: 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.Supported11.2.1.10 Use of colourWhere ICT is non-web software that provides a user interface, it shall satisfy the Success Criterion in Table 11.10: Use of colour:Colour is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.Supported11.2.1.11 Audio controlWhere ICT is non-web software that provides a user interface, it shall satisfy the Success Criterion in Table 11.11: Audio control:If any audio in a software 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 Applicable11.2.1.12 Contrast (minimum)Where ICT is non-web software that provides a user interface, it shall satisfy the Success Criterion in Table 11.12: 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.Supported With ExceptionsSee Table 211.2.1.13 Resize textWhere ICT is non-web software that provides a user interface and that supports access to enlargement features of platform or assistive technology, it shall satisfy the Success Criterion in Table 11.13: 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.Supported11.2.1.14 Images of textWhere ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy the Success Criterion in Table 11.14: 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.Supported11.2.1.15 KeyboardWhere ICT is non-web software that provides a user interface and that supports access to keyboards or a keyboard interface, it shall satisfy the Success Criterion in Table 11.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 311.2.1.16 No keyboard trapWhere ICT is non-web software that provides a user interface, it shall satisfy the Success Criterion in Table 11.16: No keyboard trap:If keyboard focus can be moved to a component of the software 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.11.2.1.17 Timing adjustableWhere ICT is non-web software that provides a user interface, it shall satisfy the Success Criterion in Table 11.17: Timing adjustable:For each time limit that is set by the software, at least one of the following is true:Turn off: The user is allowed to turn off the time limit before encountering it; orAdjust: The user is allowed to adjust the time limit before encountering it over a wide range that is at least ten times the length of the default setting; orExtend: The user is warned before time expires and given at least 20 seconds to extend the time limit with a simple action (for example, “press the space bar”), and the user is allowed to extend the time limit at least ten times; orReal-time Exception: The time limit is a required part of a real-time event (for example, an auction), and no alternative to the time limit is possible; orEssential Exception: The time limit is essential and extending it would invalidate the activity; or20 Hour Exception: The time limit is longer than 20 hours.Not Applicable11.2.1.18 Pause, stop, hideWhere ICT is non-web software that provides a user interface, it shall satisfy the Success Criterion in Table 11.18: 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; andAuto-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 Applicable11.2.1.19 Three flashes or below thresholdWhere ICT is non-web software that provides a user interface, it shall satisfy the Success Criterion in Table 11.19: Three flashes or below threshold:Software does 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.Supported11.2.1.22 Focus orderWhere ICT is non-web software that provides a user interface, it shall satisfy the Success Criterion in Table 11.22: Focus order:If software 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 411.2.1.23 Link purpose (in context)Where ICT is non-web software that provides a user interface, it shall satisfy the Success Criterion in Table 11.23: 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.Supported11.2.1.25 Headings and labelsWhere ICT is non-web software that provides a user interface, it shall satisfy the Success Criterion in Table 11.25: Headings and labels:Headings and labels describe topic or purpose.Supported11.2.1.26 Focus visibleWhere ICT is non-web software that provides a user interface, it shall satisfy the Success Criterion in 11.26: Focus visible:Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible.Supported With ExceptionsSee Table 511.2.1.27 Language of softwareWhere ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy the Success Criterion in Table 11.27: Language of software:The default human language of software can be programmatically determined.Supported11.2.1.29 On focusWhere ICT is non-web software that provides a user interface, it shall satisfy the Success Criterion in Table 11.29: On focus:When any component receives focus, it does not initiate a change of context.Supported11.2.1.30 On inputWhere ICT is non-web software that provides a user interface, it shall satisfy the Success Criterion in Table 11.30: 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 component.Supported11.2.1.33 Error identificationWhere ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy the Success Criterion in Table 11.33: 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.Supported11.2.1.34 Labels or instructionsWhere ICT is non-web software that provides a user interface, it shall satisfy the Success Criterion in Table 11.34: Labels or instructions:Labels or instructions are provided when content requires user input.Supported11.2.1.35 Error suggestionWhere ICT is non-web software that provides a user interface, it shall satisfy the Success Criterion in Table 11.35: 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.Supported11.2.1.36 Error prevention (legal, financial, data)Where ICT is non-web software that provides a user interface, it shall satisfy the Success Criterion in Table 11.36: Error prevention (legal, financial, data):For software 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:Reversible: Submissions are reversible.Checked: Data entered by the user is checked for input errors and the user is provided an opportunity to correct them.Confirmed: A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission.Supported11.2.1.37 ParsingWhere ICT is non-web software that provides a user interface and that supports access to any assistive technologies, it shall satisfy the Success Criterion in Table 11.37: Parsing:For software that uses markup languages, in such a way that the markup is separately exposed and available to assistive technologies and accessibility features of software or to a user-selectable user agent, 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.Supported11.2.1.38 Name, role, valueWhere ICT is non-web software that provides a user interface and that supports access to any assistive technologies, it shall satisfy the Success Criterion in Table 11.38: 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 611.2.2.1 – 11.2.2.38Not ApplicableClosed Functionality11.3.2.1 Platform accessibility service support for software that provides a user interfacePlatform software shall provide a set of documented platform services that enable software that provides a user interface running on the platform software to interoperate with assistive technology.Platform software should support requirements 11.3.2.5 to 11.3.2.17 except that, where a user interface concept that corresponds to one of the clauses 11.3.2.5 to 11.3.2.17 is not supported within the software environment, these requirements are not applicable. For example, selection attributes from 11.3.2.14 (Modification of focus and selection attributes) may not exist in environments that do not allow selection, which is most commonly associated with copy and paste.Not Applicable11.3.2.2 Platform accessibility service support for assistive technologiesPlatform software shall provide a set of documented platform accessibility services that enable assistive technology to interoperate with software that provides a user interface running on the platform software.Platform software should support the requirements of clauses 11.3.2.5 to 11.3.2.17 except that, where a user interface concept that corresponds to one of the clauses 11.3.2.5 to 11.3.2.17 is not supported within the software environment, these requirement are not applicable. Not Applicable11.3.2.3 Use of accessibility servicesWhere the software provides a user interface it shall use the applicable documented platform accessibility services. If the documented platform accessibility services do not allow the software to meet the applicable requirements of clauses 11.3.2.5 to 11.3.2.17, then software that provides a user interface shall use other documented services to interoperate with assistive technology.See sections 11.3.2.5 through 11.3.2.1711.3.2.4 Assistive technologyWhere the ICT is assistive technology it shall use the documented platform accessibility services.Not Applicable11.3.2.5 Object informationWhere the software provides a user interface it shall, by using the services as described in clause 11.3.2.3, make the user interface elements’ role, state(s), boundary, name, and description programmatically determinable by assistive technologies.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.11.3.2.6 Row, column, and headersWhere the software provides a user interface it shall, by using the services as described in clause 11.3.2.3, make the row and column of each cell in a data table, including headers of the row and column if present, programmatically determinable by assistive technologies.Supported With - Users who rely on Assistive Technologies may have difficulties using the results table in the Test Query dialog.11.3.2.7 ValuesWhere the software provides a user interface, it shall, by using the services as described in clause 11.3.2.3, make the current value of a user interface element and any minimum or maximum values of the range, if the user interface element conveys information about a range of values, programmatically determinable by assistive technologies.Supported11.3.2.8 Label relationshipsWhere the software provides a user interface it shall expose the relationship that a user interface element has as a label for another element, or of being labelled by another element, using the services as described in clause 11.3.2.3, so that this information is programmatically determinable by assistive technologies.Supported11.3.2.9 Parent-child relationshipsWhere the software provides a user interface it shall, by using the services as described in clause 11.3.2.3, make the relationship between a user interface element and any parent or children elements programmatically determinable by assistive technologies.Supported11.3.2.10 TextWhere the software provides a user interface it shall, by using the services as described in clause 11.3.2.3, make the text contents, text attributes, and the boundary of text rendered to the screen programmatically determinable by assistive technologies.Supported11.3.2.11 List of available actionsWhere the software provides a user interface it shall, by using the services as described in clause 11.3.2.3, make a list of available actions that can be executed on a user interface element, programmatically determinable by assistive technologies.Supported11.3.2.12 Execution of available actionsWhen permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.3.2.3, allow the programmatic execution of the actions exposed according to clause 11.3.2.11 by assistive technologies.Supported11.3.2.13 Tracking of focus and selection attributesWhere software provides a user interface it shall, by using the services as described in clause 11.3.2.3, make information and mechanisms necessary to track focus, text insertion point, and selection attributes of user interface elements programmatically determinable by assistive technologies.Supported11.3.2.14 Modification of focus and selection attributesWhen permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.3.2.3, allow assistive technologies to programmatically modify focus, text insertion point, and selection attributes of user interface elements where the user can modify these items.Supported11.3.2.15 Change notificationWhere software provides a user interface it shall, by using the services as described in 11.3.2.3, notify assistive technologies about changes in those programmatically determinable attributes of user interface elements that are referenced in requirements 11.3.2.5 to 11.3.2.11 and 11.3.2.13.Supported11.3.2.16 Modifications of states and propertiesWhen permitted by security requirements, software that provides a user interface shall, by using the services as described in clause 11.3.2.3, allow assistive technologies to programmatically modify states and properties of user interface elements, where the user can modify these items.Supported11.3.2.17 Modifications of values and textWhen permitted by security requirements, software that provides a user interface shall, by using the services as described in 11.3.2.3, allow assistive technologies to modify values and text of user interface elements using the input methods of the platform, where a user can modify these items without the use of assistive technology.Supported11.4.1 User control of accessibility featuresWhere software is a platform it shall provide sufficient modes of operation for user control over those platform accessibility features documented as intended for users.Not Applicable11.4.2 No disruption of accessibility featuresWhere software provides a user interface it shall not disrupt those documented accessibility features that are defined in platform documentation except when requested to do so by the user during the operation of the software.Supported With ExceptionsSee Table 711.5 User preferencesWhere software provides a user interface it shall provide sufficient modes of operation that use user preferences for platform settings for colour, contrast, font type, font size, and focus cursor except for software that is designed to be isolated from its underlying platforms.Supported With ExceptionsSee Table 711.6.2 Accessible content creationAuthoring tools shall enable and guide the production of content that conforms to clauses 9 (Web content) or 10 (Non-Web content) as applicable.Supported11.6.3 Preservation of accessibility information in transformationsIf the authoring tool provides restructuring transformations or re-coding transformations, then accessibility information shall be preserved in the output if equivalent mechanisms exist in the content technology of the output.Supported11.6.4 Repair assistanceIf the accessibility checking functionality of an authoring tool can detect that content does not meet a requirement of clauses 9 (Web content) or 10 (Documents) as applicable, then the authoring tool shall provide repair suggestion(s).Supported11.6.5 TemplatesWhen an authoring tool provides templates, at least one template that supports the creation of content that conforms to the requirements of clauses 9 (Web content) or 10 (Documents) as applicable shall be available and identified as such.SupportedSection 12 Documentation and support servicesCriteriaSupporting FeaturesRemarks and Explanations12.1.1 Accessibility and compatibility featuresProduct documentation provided with the ICT whether provided separately or integrated within the ICT shall list and explain how to use the accessibility and compatibility features of the ICT.Supported12.1.2 Accessible documentationProduct documentation provided with the ICT shall be made available in at least one of the following electronic formats:a) a Web format that conforms to clause 9, orb) a non-web format that conforms to clause 10.Supported12.2.2 Information on accessibility and compatibility featuresICT support services shall provide information on the accessibility and compatibility features that are included in the product documentation.Supported12.2.3 Effective communication ICT support services shall accommodate the communication needs of individuals with disabilities either directly or through a referral point.SupportedDisability Answer Desk12.2.4 Accessible documentationDocumentation provided by support services shall be made available in at least one of the following electronic formats:a) a Web format that conforms to clause 9, orb) a non-web format that conforms to clause 10.SupportedSection 13 ICT providing relay or emergency service accessThis section does not apply to Visual Studio 2017.TablesTable 1: Info and RelationshipsTable 111.2.1.7 Info and Relationships Where ICT is non-web software that provides a user interface and that supports access to assistive technologies for screen reading, it shall satisfy the Success Criterion in Table 11.7: 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 211.2.1.12 Contrast (minimum) Where ICT is non-web software that provides a user interface, it shall satisfy the Success Criterion in Table 11.12: 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 311.2.1.15 Keyboard Where ICT is non-web software that provides a user interface and that supports access to keyboards or a keyboard interface, it shall satisfy the Success Criterion in Table 11.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 411.2.1.22 Focus order Where ICT is non-web software that provides a user interface, it shall satisfy the Success Criterion in Table 11.22: Focus order:If software 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 511.2.1.26 Focus visible Where ICT is non-web software that provides a user interface, it shall satisfy the Success Criterion in 11.26: 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 611.2.1.38 Name, role, value Where ICT is non-web software that provides a user interface and that supports access to any assistive technologies, it shall satisfy the Success Criterion in Table 11.38: 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 711.4.2 No disruption of accessibility features Where software provides a user interface it shall not disrupt those documented accessibility features that are defined in platform documentation except when requested to do so by the user during the operation of the software.11.5 User preferences Where software provides a user interface it shall provide sufficient modes of operation that use user preferences for platform settings for colour, contrast, font type, font size, and focus cursor except for software that is designed to be isolated from its underlying platforms.- 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.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 not the EN 301 549 v 1.1.2 (2015-04) standard and should not be used as a substitute for it.?Excerpts of EN 301 549 v 1.1.2 are referenced solely for purposes of detailing Microsoft’s conformance with the relevant provisions.?A full and complete copy of the EN 301 549 v 1.1.2 (2015-04) is available? HYPERLINK "" \t "_blank" in this PDF?from?the European Telecommunications Standards Institute, Comité Européen de Normalisation, and Comité Européen de Normalisation Electrotechnique.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