From 46d1a6da5f915b233494624e00aff6318d9df52b Mon Sep 17 00:00:00 2001 From: Ron Petrusha Date: Wed, 28 Mar 2018 12:56:53 -0700 Subject: [PATCH] Fixed broken links (#683) --- .../winforms-accessibility-changes-471.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/Documentation/compatibility/winforms-accessibility-changes-471.md b/Documentation/compatibility/winforms-accessibility-changes-471.md index cb3d838..00f568b 100644 --- a/Documentation/compatibility/winforms-accessibility-changes-471.md +++ b/Documentation/compatibility/winforms-accessibility-changes-471.md @@ -60,7 +60,7 @@ The .NET Framework 4.7.1 adds support for the following UI automation patterns a - The control supports the [Name](xref:System.Windows.Automation.AutomationElement.NameProperty) property and the[Expand/Collapse pattern](~/docs/framework/ui-automation/implementing-the-ui-automation-expandcollapse-control-pattern.md). - The control supports [AccessibleEvents](xref:System.Windows.Forms.AccessibleEvents) indicating StateChange and NameChange when drop down is expanded or collapsed. - The control has a [ControlType](~/docs/framework/ui-automation/ui-automation-support-for-the-menubar-control-type.md) property value of . -- The control supports the [Toggle Pattern](~/docs/api/system.windows.automation.togglepattern.md). +- The control supports the [Toggle Pattern](xref:System.Windows.Automation.TogglePattern). - The and controls support the [Name](xref:System.Windows.Automation.AutomationElement.NameProperty) property and have a [ControlType](~/docs/framework/ui-automation/ui-automation-support-for-the-spinner-control-type.md) of .

**Improvements to the PropertyGrid control**
@@ -81,11 +81,11 @@ The .NET Framework 4.7.1 adds the following improvements to the PropertyBrowser **Use of OS-defined colors in High Contrast themes**
-- The and controls with their property set to , which is the default style, now use OS-defined colors in High Contrast theme when selected. Previously, text and background colors were not contrasting and were hard to read. +- The and controls with their property set to , which is the default style, now use OS-defined colors in High Contrast theme when selected. Previously, text and background colors were not contrasting and were hard to read. - The , , , , and controls with their property set to **false** used a shaded color to render text in High Contrast themes, resulting in low contrast against the background. Now these controls use the "Disabled Text" color defined by the OS. This fix applies to controls with the property set to a value other than . The latter controls are rendered by the OS. - now renders a visible rectangle around the content of the cell which has the current focus. Previously, this was not visible in certain High Contrast themes. -- controls with a property set to **false** now use the "Disabled Text" color defined by the OS. -- controls with a property set to **true** now render the associated check mark in a contrasting system color. Previously the check mark color was not contrasting enough and not visible in High Contrast themes. +- controls with their property set to **false** now use the "Disabled Text" color defined by the OS. +- controls with their property set to **true** now render the associated check mark in a contrasting system color. Previously the check mark color was not contrasting enough and not visible in High Contrast themes. NOTE: Windows 10 has changed values for some high contrast system colors. Windows Forms Framework is based on the Win32 framework. For the best experience, run on the latest version of Windows and opt in to the latest OS changes by adding an app.manifest file in a test application and uncommenting the following code: @@ -97,11 +97,11 @@ NOTE: Windows 10 has changed values for some high contrast system colors. Window
**Improved keyboard navigation** -- When a control has its property set to and is the first control in the tab order on the form, it now displays a focus rectangle when the parent form is opened using the keyboard. Before this change, keyboard focus was on this control, but a focus indicator was not rendered. +- When a control has its property set to and is the first control in the tab order on the form, it now displays a focus rectangle when the parent form is opened using the keyboard. Before this change, keyboard focus was on this control, but a focus indicator was not rendered. **Improved Narrator support** - The control has added support for assistive technologies to access the control, including the ability for Narrator to read the value of the control when previously it could not. -- The control now notifies Narrator when a property has been changed. Previously, Narrator did not receive notification and as a result users would not be informed that the property had been updated. +- The control now notifies Narrator when a property has been changed. Previously, Narrator did not receive notification and as a result users would not be informed that the property had been updated. - The control has changed the way it notifies Narrator of the text of in the control. Previously, Narrator announced this text twice and read "&" symbols as real text even though they are not visible to a user. The duplicated text was removed from the Narrator announcements, as well as unnecessary "&" symbols. - The control types now correctly report the read-only status to Narrator and other assistive technologies. - Narrator is now able to read the System Menu of child windows in [Multiple-Document Interface]~/docs/framework/winforms/advanced/multiple-document-interface-mdi-applications.md) applications.