You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To make sure that the accessible name is also an element that is localized, you should use correct techniques for storing localizable strings as resources and then referencing the resource connections with [x:Uid directive](/windows/uwp/xaml-platform/x-uid-directive) values. If the accessible name is coming from an explicitly set [**AutomationProperties.Name**](/dotnet/api/system.windows.automation.automationproperties.name) usage, make sure that the string there is also localizable.
145
+
To make sure that the accessible name is also an element that is localized, you should use correct techniques for storing localizable strings as resources and then referencing the resource connections with [x:Uid directive](/windows/apps/develop/platform/xaml/x-uid-directive) values. If the accessible name is coming from an explicitly set [**AutomationProperties.Name**](/dotnet/api/system.windows.automation.automationproperties.name) usage, make sure that the string there is also localizable.
146
146
147
147
Note that attached properties such as the [**AutomationProperties**](/uwp/api/Windows.UI.Xaml.Automation.AutomationProperties) properties use a special qualifying syntax for the resource name, so that the resource references the attached property as applied to a specific element. For example, the resource name for [**AutomationProperties.Name**](/dotnet/api/system.windows.automation.automationproperties.name) as applied to a UI element named `MediumButton` is: `MediumButton.[using:Windows.UI.Xaml.Automation]AutomationProperties.Name`.
Copy file name to clipboardExpand all lines: hub/apps/design/accessibility/high-contrast-themes.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -174,7 +174,7 @@ In the following code snippet, we show a Grid element declared with a background
174
174
<GridBackground="#E6E6E6">
175
175
```
176
176
177
-
Instead, we recommend using the [**{ThemeResource} markup extension**](/windows/uwp/xaml-platform/themeresource-markup-extension) to reference a color in the [**ThemeDictionaries**](/uwp/api/windows.ui.xaml.resourcedictionary.themedictionaries) collection of a [**ResourceDictionary**](/uwp/api/Windows.UI.Xaml.ResourceDictionary). This enables the automatic substitution of colors and brushes based on the user's current theme.
177
+
Instead, we recommend using the [**{ThemeResource} markup extension**](/windows/apps/develop/platform/xaml/themeresource-markup-extension) to reference a color in the [**ThemeDictionaries**](/uwp/api/windows.ui.xaml.resourcedictionary.themedictionaries) collection of a [**ResourceDictionary**](/uwp/api/Windows.UI.Xaml.ResourceDictionary). This enables the automatic substitution of colors and brushes based on the user's current theme.
Copy file name to clipboardExpand all lines: hub/apps/design/accessibility/landmarks-and-headings.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,17 +28,17 @@ For example, when using a tab panel, consider making it a *navigation* landmark.
28
28
29
29
Whether within a landmark or even outside a landmark, consider annotating sub-elements as headings with logical heading levels.
30
30
31
-
## The Windows Settings app
31
+
## Windows Settings
32
32
33
-
The following image shows the **Ease of Access** page in a previous version of the Windows Settings app.
33
+
The following image shows the **Ease of Access** page in a previous version of Windows Settings.
34
34
35
-
35
+
36
36
37
37
For this page, the search edit box is wrapped within a search landmark, the navigation elements on the left are wrapped within a navigation landmark, and the main content on the right is wrapped within a main content landmark.
38
38
39
39
Within the navigation landmark there is a main group heading called **Ease of Access** (heading level 1) with sub-options of **Vision**, **Hearing**, and so on (heading level 2). Within the main content, **Display** is set to heading level 1 with sub-groups such as **Make everything bigger** set to heading level 2.
40
40
41
-
The Settings app would be accessible without landmarks and headings, but it becomes much more usable with them. In this case, a user with a screen reader can quickly get to the group (landmark) they're interested in, and from there they can then quickly get to the sub-group (heading).
41
+
Windows Settings would be accessible without landmarks and headings, but it becomes much more usable with them. In this case, a user with a screen reader can quickly get to the group (landmark) they're interested in, and from there they can then quickly get to the sub-group (heading).
Copy file name to clipboardExpand all lines: hub/apps/design/app-settings/guidelines-for-app-settings.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -77,7 +77,7 @@ If your app allows users to choose the app's color mode, present these options u
77
77
- Dark
78
78
- Windows default
79
79
80
-
We also recommend adding a hyperlink to the Colors page of the Windows Settings app where users can access and modify the current default app mode. Use the string "Windows color settings" for the hyperlink text and `ms-settings:colors` for the URI.
80
+
We also recommend adding a hyperlink to the Colors page of Windows Settings where users can access and modify the current default app mode. Use the string "Windows color settings" for the hyperlink text and `ms-settings:colors` for the URI.
81
81
82
82
Copy file name to clipboardExpand all lines: hub/apps/design/controls/buttons.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@ A button gives the user a way to trigger an immediate action. Some buttons are s
16
16
17
17
18
18
19
-
The [Extensible Application Markup Language (XAML)](/windows/uwp/xaml-platform/xaml-overview) framework provides a standard button control as well as several specialized button controls.
19
+
The [Extensible Application Markup Language (XAML)](/windows/apps/develop/platform/xaml/xaml-overview) framework provides a standard button control as well as several specialized button controls.
When you tap a **Button** control with a finger or stylus, or press a left mouse button while the pointer is over it, the button raises the [Click](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.primitives.buttonbase.click) event. If a button has keyboard focus, pressing the Enter key or the Spacebar also raises the **Click** event.
168
168
169
-
You generally can't handle low-level [PointerPressed](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.uielement.pointerpressed) events on a **Button** object because it has the **Click** behavior instead. For more info, see [Events and routed events overview](/windows/uwp/xaml-platform/events-and-routed-events-overview).
169
+
You generally can't handle low-level [PointerPressed](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.uielement.pointerpressed) events on a **Button** object because it has the **Click** behavior instead. For more info, see [Events and routed events overview](/windows/apps/develop/platform/xaml/events-and-routed-events-overview).
170
170
171
171
You can change how a button raises the **Click** event by changing the [ClickMode](/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.clickmode) property. The default value of **ClickMode** is **Release**, but you also can set a button's **ClickMode** value to **Hover** or **Press**. If **ClickMode** is **Hover**, the **Click** event can't be raised by using the keyboard or touch.
Copy file name to clipboardExpand all lines: hub/apps/design/controls/checkbox.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -95,7 +95,7 @@ In this example, the **IsChecked** property of the check box to agree to terms o
95
95
#### Using x:Bind
96
96
97
97
> [!NOTE]
98
-
> We only show the relevant code here. For more info about data binding see [Data binding overview](/windows/uwp/data-binding/data-binding-quickstart). Specific {x:Bind} info (such as casting) is detailed in [{x:Bind} markup extension](/windows/uwp/xaml-platform/x-bind-markup-extension).
98
+
> We only show the relevant code here. For more info about data binding see [Data binding overview](/windows/uwp/data-binding/data-binding-quickstart). Specific {x:Bind} info (such as casting) is detailed in [{x:Bind} markup extension](/windows/apps/develop/platform/xaml/x-bind-markup-extension).
Copy file name to clipboardExpand all lines: hub/apps/design/controls/controls-and-events-intro.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -47,7 +47,7 @@ You can also drag the control from the Toolbox to the XAML designer.
47
47
48
48
## Set the name of a control
49
49
50
-
To work with a control in code, you set its [x:Name](/windows/uwp/xaml-platform/x-name-attribute) attribute and reference it by name in your code. You can set the name in the Visual Studio Properties window or in XAML. Here's how to set the name of the currently selected control by using the Name text box at the top of the Properties window.
50
+
To work with a control in code, you set its [x:Name](/windows/apps/develop/platform/xaml/x-name-attribute) attribute and reference it by name in your code. You can set the name in the Visual Studio Properties window or in XAML. Here's how to set the name of the currently selected control by using the Name text box at the top of the Properties window.
Each control has events that enable you to respond to actions from your user or other changes in your app. For example, a Button control has a Click event that is raised when a user clicks the Button. You create a method, called an event handler, to handle the event. You can associate a control's event with an event handler method in the Properties window, in XAML, or in code. For more info about events, see [Events and routed events overview](/windows/uwp/xaml-platform/events-and-routed-events-overview).
108
+
Each control has events that enable you to respond to actions from your user or other changes in your app. For example, a Button control has a Click event that is raised when a user clicks the Button. You create a method, called an event handler, to handle the event. You can associate a control's event with an event handler method in the Properties window, in XAML, or in code. For more info about events, see [Events and routed events overview](/windows/apps/develop/platform/xaml/events-and-routed-events-overview).
109
109
110
110
To create an event handler, select the control and then click the Events tab at the top of the Properties window. The Properties window lists all of the events available for that control. Here are some of the events for a Button.
Copy file name to clipboardExpand all lines: hub/apps/design/controls/date-and-time.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -186,7 +186,7 @@ A related concept is the Calendar class, which influences how dates are interpre
186
186
.NET also supports a type named [DateTime](/dotnet/api/system.datetime), which is implicitly convertible to a [DateTimeOffset](/dotnet/api/system.datetimeoffset). So you might see a "DateTime" type being used in .NET code that's used to set values that are really DateTimeOffset. For more info on the difference between DateTime and DateTimeOffset, see Remarks in the [DateTimeOffset](/dotnet/api/system.datetimeoffset) class.
187
187
188
188
> [!NOTE]
189
-
> Properties that take date objects can't be set as a XAML attribute string, because the Windows Runtime XAML parser doesn't have a conversion logic for converting strings to dates as DateTime/DateTimeOffset objects. You typically set these values in code. Another possible technique is to define a date that's available as a data object or in the data context, then set the property as a XAML attribute that references a [\{Binding\} markup extension](/windows/uwp/xaml-platform/binding-markup-extension) expression that can access the date as data.
189
+
> Properties that take date objects can't be set as a XAML attribute string, because the Windows Runtime XAML parser doesn't have a conversion logic for converting strings to dates as DateTime/DateTimeOffset objects. You typically set these values in code. Another possible technique is to define a date that's available as a data object or in the data context, then set the property as a XAML attribute that references a [\{Binding\} markup extension](/windows/apps/develop/platform/xaml/binding-markup-extension) expression that can access the date as data.
0 commit comments