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
Copy file name to clipboardExpand all lines: aries-site/src/pages/components/anchor.mdx
-2
Original file line number
Diff line number
Diff line change
@@ -131,8 +131,6 @@ Used to indicate that an anchor cannot be interacted with.
131
131
### A11y guidance
132
132
The following guidance should be considered for each instance of the component and is the responsibility of the implementer. WCAG criteria provided directly by the Grommet component are summarized under [WCAG compliance](#wcag-compliance).
133
133
134
-
**Note**: WCAG rules marked as conditional indicate that the implementer must take additional actions to ensure full compliance.
135
-
136
134
**Use 'target' and 'rel' props when linking externally:**
137
135
138
136
If clicking an Anchor leads to an external URL, apply these props to the anchor:
Copy file name to clipboardExpand all lines: aries-site/src/pages/components/button.mdx
+19-7
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,8 @@
1
-
import { BestPracticeGroup, Example } from'../../layouts';
1
+
import {
2
+
AccessibilitySection,
3
+
BestPracticeGroup,
4
+
Example,
5
+
} from'../../layouts';
2
6
import {
3
7
ButtonBadCancelPreview,
4
8
ButtonBadGroupPreview,
@@ -137,12 +141,6 @@ For buttons with icons ONLY, it is important that you show the two following ele
137
141
138
142
2. Inform the user of what will happen when the button is clicked by including `a11yTitle` or `aria-label`.
139
143
140
-
### Accessibility
141
-
142
-
If pressing a Button results in a new URL, or the resultant UI makes sense as "a new browser tab," that is a link `<a>`. Everything else is a `<button>`.
143
-
144
-
The distinction is important to screen reader users to know what's going to happen next. Will I navigate somewhere or will something happen on the page? So it's important to choose the right HTML element for the job.
145
-
146
144
## Primary buttons
147
145
148
146
Primary buttons highlight actions on a page delivering the most benefit to users. They are helpful in enabling users’ goals, unlocking new value by enabling a new experience, capability, or creation of something which hadn’t previously existed.
@@ -381,3 +379,17 @@ For button groups on screen widths less than or equal to 576px (Grommet "small")
381
379
<ButtonBadGroupPreview />
382
380
</Example>
383
381
</BestPracticeGroup>
382
+
383
+
## Accessibility
384
+
### A11y guidance
385
+
The following guidance should be considered for each instance of the component and is the responsibility of the implementer. WCAG criteria provided directly by the Grommet component are summarized under [WCAG compliance](#wcag-compliance).
386
+
387
+
If pressing a Button results in a new URL, or the resultant UI makes sense as "a new browser tab," that is a link `<a>`. Everything else is a `<button>`.
388
+
389
+
The distinction is important to screen reader users to know what's going to happen next. Will I navigate somewhere or will something happen on the page? So it's important to choose the right HTML element for the job.
390
+
391
+
If using an `<a>` tag, see the [WCAG rules for the Anchor component](/components/anchor#wcag-compliance).
Copy file name to clipboardExpand all lines: aries-site/src/pages/components/menu.mdx
+10-7
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
import { Box } from'grommet';
2
-
import { BestPracticeGroup, Example } from'../../layouts';
2
+
import { AccessibilitySection, BestPracticeGroup, Example } from'../../layouts';
3
3
import {
4
4
MenuExample,
5
5
MenuBatchActionsExample,
@@ -41,12 +41,6 @@ To create a predictable experience for users, the following are guidelines for u
41
41
42
42
**Avoid creating cascading menus.** Menus with multiple layers creates a confusing experience for the user because relevant actions may become nested and difficult to find. Refining menu items to necessary actions creates a more manageable user experience.
43
43
44
-
### Accessibility
45
-
46
-
Accessibility features such as screen reader messages are automatically built into Menu. By default, these messages are "Open Menu" and "Close Menu". However, if a more specific message is necessary, a custom [a11yTitle](https://v2.grommet.io/menu?theme=hpe#a11yTitle) or [messages](https://v2.grommet.io/menu?theme=hpe#messages) may be applied.
47
-
48
-
An icon can be used on a menu item to provide additional context about the action. It is recommended that an icon is used in conjunction with text to ensure the context of the menu item is clear. However, there may be cases where an icon alone is sufficient. For example, highly familiar action indicators, such as this example of [Menu with custom icon](#with-custom-icon) demonstrate when an icon only may be sufficient.
49
-
50
44
## Organizing menu items
51
45
52
46
Allow a user to quickly locate the menu item they desire by organizing menu items
@@ -283,3 +277,12 @@ Used to indicate that a Menu cannot be interacted with.
283
277
>
284
278
<MenuDisabledExample />
285
279
</Example>
280
+
281
+
### Accessibility
282
+
283
+
Accessibility features such as screen reader messages are automatically built into Menu. By default, these messages are "Open Menu" and "Close Menu". However, if a more specific message is necessary, a custom [a11yTitle](https://v2.grommet.io/menu?theme=hpe#a11yTitle) or [messages](https://v2.grommet.io/menu?theme=hpe#messages) may be applied.
284
+
285
+
An icon may be used on a menu item to provide additional context about the action. It is recommended that an icon is used in conjunction with text to ensure the context of the menu item is clear. However, there may be cases where an icon alone is sufficient. For example, highly familiar action indicators, such as this example of [Menu with custom icon](#with-custom-icon) demonstrate when an icon only may be sufficient.
0 commit comments