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
title: Browser Compatibility in Blazor - Syncfusion
4
-
description: Check out and learn here all about browser compatibility of syncfusion blazor components and much more.
3
+
title: Browser support for Syncfusion Blazor
4
+
description: Supported browsers for Syncfusion Blazor components on Windows, Linux, and macOS for Blazor Server, Web App, and WebAssembly.
5
5
platform: Blazor
6
-
component: Common
6
+
control: Common
7
7
documentation: ug
8
8
---
9
9
10
10
# Browser Compatibility in Blazor
11
11
12
-
Syncfusion<supstyle="font-size:70%">®</sup> Blazor UI components are supported by all modern web browsers on both desktop and mobile devices running Windows, Linux, or MacOS.
12
+
Syncfusion<supstyle="font-size:70%">®</sup> Blazor UI components are supported by modern web browsers on desktop and mobile devices running Windows, Linux, or macOS.
13
13
14
14
## Blazor Web App
15
15
16
+
All modern browsers listed are supported on their latest stable versions.
17
+
16
18
| Browser | Versions |
17
19
|--------------|---------------|
18
20
| Google Chrome, including Android & iOS | Latest Version |
N> Blazor Server supports Microsoft Internet Explorer 11 with sufficient polyfills when using [.NET Core 3.1 / lower versions](https://learn.microsoft.com/en-us/aspnet/core/blazor/supported-platforms?view=aspnetcore-3.1). Refer this [documentation](https://blazor.syncfusion.com/documentation/common/how-to/render-blazor-server-app-in-ie) to add the polyfills in Blazor server application.
Copy file name to clipboardExpand all lines: blazor/common/accessibility.md
+21-21Lines changed: 21 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,63 +1,63 @@
1
1
---
2
2
layout: post
3
-
title: Accessibility with ADA compliance in Syncfusion Blazor components
4
-
description: The Syncfusion Blazor UI components are compliant with section 508, ADA, WAI-ARIA, WCAG, and keyboard accessibility standards.
3
+
title: Accessibility in Syncfusion Blazor components
4
+
description: Syncfusion Blazor components support WCAG 2.2, Section 508, WAI-ARIA, ADA, and keyboard accessibility standards.
5
5
platform: Blazor
6
-
component: Common
6
+
control: Common
7
7
documentation: ug
8
8
---
9
9
10
-
# Accessibility with ADA Compliance in Blazor Components
10
+
# Accessibility in Syncfusion® Blazor components
11
11
12
-
All the Syncfusion<supstyle="font-size:70%">®</sup> Blazor components follow the WAI-ARIA accessibility standard by default. This enables you to build accessible web applications, which are fully navigable by users with disabilities.
12
+
All Syncfusion<supstyle="font-size:70%">®</sup> Blazor components follow WAI-ARIA by default, enabling accessible web applications that are fully navigable with assistive technologies.
13
13
14
14
## Accessibility overview
15
15
16
-
Accessibility in components refers to the practice of designing and building user interface elements in a way that makes them accessible to users with disabilities. This can include a variety of things, such as making sure that text is high-contrast and easy to read, providing alternative text for images, and designing controls and interactions that can be used with a keyboard or assistive technology.
16
+
Accessibility in components refers to designing and building user interface elements so that users with disabilitiescan perceive, operate, and understand them. Examples include sufficient color contrast, alternative text for images, and keyboard-operable controls and interactions.
17
17
18
18
## Accessibility standards
19
19
20
-
The component is said to be accessible when it is constructed in accordance with certain standards that are required to make it accessible.
20
+
A component is accessible when it is implemented in accordance with recognized accessibility standards.
21
21
22
22
The accessibility of the components consists of the following standards and aspects:
23
23
24
24
[ADA](https://www.ada.gov/) - A law to ensure that people with disabilities have the same opportunities and access as people without disabilities.
25
25
26
-
[WCAG 2.2](https://www.w3.org/WAI/standards-guidelines/wcag/) - The Web Content Accessibility Guidelines (WCAG) provide guidelines developed by the World Wide Web Consortium (W3C) to ensure web content is accessible to people with disabilities. WCAG 2.2 establishes a framework of accessibility principles and their associated success criteria. The level of accessibility conformance achieved by a web application is determined by the extent to which it meets these success criteria, categorized into three levels: A, AA, and AAA.
26
+
[WCAG 2.2](https://www.w3.org/WAI/standards-guidelines/wcag/) - Guidelines from the W3C to ensure web content is accessible to people with disabilities, organized by success criteria at levels A, AA, and AAA.
27
27
28
-
[Section 508](https://www.section508.gov/) - It is a set of guidelines for making electronic and information technology (EIT) accessible to people with disabilities. These standards apply to federal agencies in the United States, and they are based on the Web Content Accessibility Guidelines (WCAG).
28
+
[Section 508](https://www.section508.gov/) - U.S. federal standards for making electronic and information technology accessible, aligned with WCAG.
29
29
30
-
[WAI-ARIA](https://www.w3.org/WAI/ARIA/) - WAI-ARIA stands for “Web Accessibility Initiative - Accessible Rich Internet Applications.” It is a set of technical specifications and guidelines developed by the World Wide Web Consortium (W3C) as part of the Web Accessibility Initiative (WAI). WAI-ARIA is designed to enhance the accessibility of dynamic web content, particularly web applications and rich internet applications (RIAs), for people with disabilities. WAI-ARIA provides a set of roles, states, and properties that can be added to HTML elements to provide additional context and information about the purpose and behavior of those elements. This can help assistive technologies better understand and interpret web content and interact with web applications.
30
+
[WAI-ARIA](https://www.w3.org/WAI/ARIA/) - Roles, states, and properties that enhance accessibility of dynamic web contentand applications for assistive technologies.
31
31
32
-
[Keyboard navigation](https://www.w3.org/TR/WCAG22/#keyboard-accessible) - It refers to the ability to use a keyboard to interact with and navigate through a user interface. It is an important aspect of web accessibility, as it allows people who cannot use a mouse or other pointing device to access and use web content and applications.
32
+
[Keyboard navigation](https://www.w3.org/TR/WCAG22/#keyboard-accessible) - The ability to use a keyboard to interact with and navigate a user interface.
33
33
34
34
Syncfusion<supstyle="font-size:70%">®</sup> Blazor components adhere to these established standards.
35
35
36
36
## Accessibility compliance
37
37
38
-
The accessibility support provided by Syncfusion<supstyle="font-size:70%">®</sup> Blazor components is based on a collection of methodologies for adhering to and [applying recognized standards and technical specifications](#accessibility-standards) to ensure an intuitive experience for people with disabilities.
38
+
Accessibility support in Syncfusion<supstyle="font-size:70%">®</sup> Blazor components is based on adhering to and [applying recognized standards and technical specifications](#accessibility-standards) to ensure an intuitive experience for people with disabilities.
39
39
40
40
There are several methodologies of accessibility validation that can be performed on the Syncfusion<supstyle="font-size:70%">®</sup> Blazor components, such as:
41
41
42
42
The [WAI-ARIA patterns](https://www.w3.org/WAI/ARIA/apg/patterns/) are followed by the Syncfusion<supstyle="font-size:70%">®</sup> Blazor components to enable appreciable accessibility.
43
43
44
-
Each Blazor component is subjected to manual testing with a screen reader and also automated test cases to ensure the component’s required attributes.
44
+
Each Blazor component is evaluated with manual screen reader testing and automated tests to ensure required attributes and behaviors are present.
45
45
46
-
Attributes are allocated and updated correctly during interaction as well. Each component has been assigned a distinct `Role` attribute and its own set of ARIA attributes defined by the [WCAG 2.2](https://www.w3.org/TR/WCAG22/) specification.
46
+
Attributes are assigned and updated correctly during interaction. Each component has an appropriate `role`and ARIA attributes defined by the [WCAG 2.2](https://www.w3.org/TR/WCAG22/) specification.
47
47
48
48
In addition to the methodologies mentioned above, Syncfusion<supstyle="font-size:70%">®</sup> Blazor components are constructed to support the following accessibility aspects.
49
49
50
50
### Screen reader support
51
51
52
-
A screen reader allows people who are blind or visually impaired to use a computer by reading aloud the text that is displayed on the screen. Syncfusion<supstyle="font-size:70%">®</sup> Blazor components followed the [WAI-ARIA](https://www.w3.org/WAI/ARIA/)standards to work properly in the screen readers such as [Narrator](https://support.microsoft.com/en-us/windows/complete-guide-to-narrator-e4397a0d-ef4f-b386-d8ae-c172f109bdb1) for Windows and [Embedded VoiceOver](https://support.apple.com/en-in/guide/voiceover/vo2706/mac) for MAC.
52
+
Syncfusion<supstyle="font-size:70%">®</sup> Blazor components follow [WAI-ARIA](https://www.w3.org/WAI/ARIA/) to work properly with screen readers such as [Narrator](https://support.microsoft.com/windows/complete-guide-to-narrator-e4397a0d-ef4f-b386-d8ae-c172f109bdb1) for Windows and [VoiceOver](https://support.apple.com/guide/voiceover/vo2706/mac) for macOS.
53
53
54
-
### Right-To-Left support
54
+
### Right-to-left support
55
55
56
56
Right-to-Left (RTL) support allows applications to effectively communicate with users who use languages that are written from right to left, such as Arabic, Hebrew, etc. Syncfusion<supstyle="font-size:70%">®</sup> Blazor components support the Right-to-Left feature. Refer to the [Right-to-Left documentation](https://blazor.syncfusion.com/documentation/common/right-to-left) to learn more about this support.
57
57
58
58
### Color contrast
59
59
60
-
Syncfusion<supstyle="font-size:70%">®</sup> Blazor components come equipped with [predefined themes](https://blazor.syncfusion.com/documentation/appearance/themes) that guarantee the presence of satisfactory color contrast, benefiting individuals with visual impairments.
60
+
Syncfusion<supstyle="font-size:70%">®</sup> Blazor components include [predefined themes](https://blazor.syncfusion.com/documentation/appearance/themes) that provide sufficient color contrast to benefit users with visual impairments.
61
61
62
62
### Mobile device support
63
63
@@ -71,15 +71,15 @@ Syncfusion<sup style="font-size:70%">®</sup> Blazor components support keybo
71
71
72
72
Ensuring the accessibility of Syncfusion<supstyle="font-size:70%">®</sup> Blazor components is crucial for making the product inclusive and user-friendly for individuals with disabilities. This process involves various types of accessibility testing, including:
73
73
74
-
***Automated testing**: The Syncfusion<supstyle="font-size:70%">®</sup> Blazor component's accessibility levels are ensured through an [axe-core](https://www.nuget.org/packages/Deque.AxeCore.Playwright) with playwright tests.
74
+
***Automated testing**: Accessibility is validated using [axe-core](https://www.nuget.org/packages/Deque.AxeCore.Playwright) with Playwright tests.
75
75
76
-
***Manual testing**: This type of testing involves manually evaluating the Syncfusion<supstyle="font-size:70%">®</sup> Blazor components. During manual accessibility testing, testers will ensure accessibility using the screen readers such as [Narrator](https://support.microsoft.com/en-us/windows/complete-guide-to-narrator-e4397a0d-ef4f-b386-d8ae-c172f109bdb1) for Windows and [Embedded VoiceOver](https://support.apple.com/en-in/guide/voiceover/vo2706/mac) for MAC.
76
+
***Manual testing**: Manual evaluation using screen readers such as [Narrator](https://support.microsoft.com/windows/complete-guide-to-narrator-e4397a0d-ef4f-b386-d8ae-c172f109bdb1) for Windows and [VoiceOver](https://support.apple.com/guide/voiceover/vo2706/mac) for macOS.
77
77
78
-
Syncfusion<supstyle="font-size:70%">®</sup> Blazor components will keep improving when there is anything required. It also involves client feedback to make the component more accessible.
78
+
Syncfusion<supstyle="font-size:70%">®</sup> Blazor components continually improve based on standards updates and user feedback to enhance accessibility.
79
79
80
80
## Accessibility support for specific components
81
81
82
-
Consult the component-specific documents below for detailed information about how Syncfusion<supstyle="font-size:70%">®</sup> Blazor components ensure compliance with accessibility standards, encompassing Section 508, WAI-ARIA, WCAG 2.2, keyboard navigation, and more.
82
+
Consult the component-specific documents below for details on how Syncfusion<supstyle="font-size:70%">®</sup> Blazor components ensure compliance with accessibility standards, including Section 508, WAI-ARIA, WCAG 2.2, keyboard navigation, and more. The table uses the legend shown below.
0 commit comments