WID/Current/Developer/Accessibility - Revision history

WikiSysop at 20:46, May 24, 2022

2022-05-24T20:46:12Z

Ed.jamer@genesys.com: Text replacement - "Genesys Cloud" to "Genesys Cloud CX"

2021-11-09T21:27:48Z

Text replacement - "Genesys Cloud" to "Genesys Cloud CX"

Chrissy.forrest@genesys.com: Published

2021-03-17T12:39:21Z

Published

Chrissy.forrest@genesys.com: Published

2021-03-05T14:15:54Z

Published

Chrissy.forrest@genesys.com: Published

2021-02-03T20:56:12Z

Published

Chrissy.forrest@genesys.com: Published

2020-11-10T21:47:07Z

Published

Chrissy.forrest@genesys.com: Published

2020-11-02T19:42:21Z

Published

Chrissyforrest: Published

2020-10-22T16:49:59Z

Published

Chrissyforrest: Published

2020-07-30T21:51:29Z

Published

Show changes

WikiSysop: Text replacement - "\|Platform=([^\|])GenesysEngage-onpremises([\|])" to "|Platform=$1GenesysEngage-cloud$2"

2020-07-25T02:39:20Z

Text replacement - "\|Platform=([^\|]*)GenesysEngage-onpremises([\|]*)" to "|Platform=$1GenesysEngage-cloud$2"

@@ Line 76: / Line 76: @@
 |anchor=ka
 |alignment=Vertical
-|structuredtext=[[File:Screen-Recording-2020-03-25-at-1.gif|472x472px]]
+|structuredtext=[[File:Screen-Recording-2020-03-25-at-1.gif|472x472px|alt=Webchat transcript showing tabbing to and from each option, which include the "Type your message here" section, the emoji button, and the attachment button.]]
 Supported Widgets are accessible via the keyboard. Users may navigate to and within any widget using the '''tab''' key or '''shift+tab''' key combo. For dropdowns and the date picker, the user can highlight a selection using the '''arrow''' keys. The '''enter''' or '''space''' key can then be used to make a selection, send a message, or activate a button.
@@ Line 110: / Line 110: @@
 {{!}}-
 {{!}}As per the “1.4.11 Non-text contrast” success criterion, icon color has been modified to meet the contrast requirement of at least 3:1 ratio against the adjacent/background color.
-{{!}}[[File:Before 5.png{{!}}center{{!}}thumb{{!}}100x100px]]
+{{!}}[[File:Before 5.png{{!}}center{{!}}thumb{{!}}100x100px{{!}}alt=Icon color before modifications.]]
-{{!}}[[File:After 5.png{{!}}thumb{{!}}100x100px{{!}}center]]
+{{!}}[[File:After 5.png{{!}}thumb{{!}}100x100px{{!}}center{{!}}alt=Icon color after modifications.]]
 {{!}}-
 {{!}}As per the “1.4.3 Contrast (minimum)” success criterion, background color of the primary button has been modified to ensure that the contrast ratio of at least 4.5:1 exists between text and background.
-{{!}}[[File:Before 6.png{{!}}center{{!}}thumb{{!}}100x100px]]
+{{!}}[[File:Before 6.png{{!}}center{{!}}thumb{{!}}100x100px{{!}}alt=Background color of the primary button before modifications.]]
-{{!}}[[File:After 6.png{{!}}center{{!}}thumb{{!}}100x100px]]
+{{!}}[[File:After 6.png{{!}}center{{!}}thumb{{!}}100x100px{{!}}alt=Background color of the primary button after modifications.]]
 {{!}}-
 {{!}}As per the “1.4.3 Contrast (minimum)” success criterion, placeholder text color has been modified to ensure that the contrast ratio of at least 4.5:1 exists between text and background.
-{{!}}[[File:Before 10.png{{!}}center{{!}}thumb{{!}}100x100px]]
+{{!}}[[File:Before 10.png{{!}}center{{!}}thumb{{!}}100x100px{{!}}alt=Placeholder text color before modifications.]]
-{{!}}[[File:After 10.png{{!}}center{{!}}thumb{{!}}100x100px]]
+{{!}}[[File:After 10.png{{!}}center{{!}}thumb{{!}}100x100px{{!}}alt=Placeholder text color after modifications.]]
 {{!}}-
 {{!}}As per the “2.4.7 Focus visible & 1.4.11 Non-text contrast” success criterion, borders with 3:1 contrast ratio have been added to highlight the focused state of the menu items.
-{{!}}[[File:Before 20.png{{!}}center{{!}}thumb{{!}}115x115px]]
+{{!}}[[File:Before 20.png{{!}}center{{!}}thumb{{!}}115x115px{{!}}alt=Non-text contrast before modifications.]]
-{{!}}[[File:After 20.png{{!}}center{{!}}thumb{{!}}115x115px]]
+{{!}}[[File:After 20.png{{!}}center{{!}}thumb{{!}}115x115px{{!}}alt=Non-text contrast after modifications.]]
 {{!}}}
 |Status=No

@@ Line 32: / Line 32: @@
 {{{!}} class="wikitable"
 !Plugin
-!Genesys Cloud
+!Genesys Cloud CX
 {{!}}-
 {{!}}{{Link-SomewhereInThisVersion|manual=SDK|topic=WebChat-combined|display text=WebChat}}

@@ Line 62: / Line 62: @@
 |structuredtext=Supported widgets are accessible via screen readers, which announce the following: all the textual and non-textual content on the Widgets window elements, new chat messages sent by the agent to the user, outgoing messages sent by the user to the agent, and error messages. To achieve a consistent reading behavior of live data across all the screen readers and the browsers, recommended ARIA live regions have been implemented in WebChat for reading new messages.
-Genesys Widgets is built and maintained following WCAG A/AA accessibility standards. These standards are supported by popular screenreaders, such as JAWS, VoiceOver (MacOS, iOS), TalkBack, and others.
+Genesys Widgets is built and maintained following WCAG A/AA accessibility standards. These standards are supported by popular screen readers, such as JAWS, VoiceOver (MacOS, iOS), TalkBack, and others.
 Genesys supports compatibility with most commonly used screen readers in the following cases:
-* '''PC Windows OS:''' JAWS with Chrome and Internet Explorer 11 or Edge
+*'''PC Windows OS:''' JAWS with Chrome and Internet Explorer 11 or Edge
-* '''Mac OS''': VoiceOver with Chrome and Safari
+*'''Mac OS''': VoiceOver with Chrome and Safari
-* '''iOS''': VoiceOver with Safari
+*'''iOS''': VoiceOver with Safari
-* '''Android''': TalkBack with Chrome
+*'''Android''': TalkBack with Chrome
 {{NoteFormat|Not all screen readers may read all the textual and non-textual window functionality. There are known issues around Firefox and Internet Explorer with some screen readers. The content is read as long as the screen reader model is supported on that particular browser. |1}}
 |Status=No

@@ Line 60: / Line 60: @@
 |anchor=srs
 |alignment=Vertical
-|structuredtext=Supported widgets are accessible via screen readers, which announce the following: all the textual and non-textual content on the Widgets window elements, new chat messages sent by the agent to the user, outgoing messages sent by the user to the agent, and error messages. To achieve a consistent reading behavior of live data across all the screen readers and the browsers, recommended ARIA live regions have been implemented in Web Chat for reading new messages.
+|structuredtext=Supported widgets are accessible via screen readers, which announce the following: all the textual and non-textual content on the Widgets window elements, new chat messages sent by the agent to the user, outgoing messages sent by the user to the agent, and error messages. To achieve a consistent reading behavior of live data across all the screen readers and the browsers, recommended ARIA live regions have been implemented in WebChat for reading new messages.
-Widgets has been tested and verified in the following desktop environments:
+Genesys Widgets is built and maintained following WCAG A/AA accessibility standards. These standards are supported by popular screenreaders, such as JAWS, VoiceOver (MacOS, iOS), TalkBack, and others.
-*'''Windows 10''': JAWS Professional Edition Version 2020.1912.11 with Chrome and Internet Explorer 10
+Genesys supports compatibility with most commonly used screen readers in the following cases:
 {{NoteFormat|Not all screen readers may read all the textual and non-textual window functionality. There are known issues around Firefox and Internet Explorer with some screen readers. The content is read as long as the screen reader model is supported on that particular browser. |1}}
 |Status=No

@@ Line 137: / Line 137: @@
 |alignment=Vertical
 |structuredtext====Localization===
-Aria labels are used throughout Genesys Widgets to supply callouts and context for screenreaders. These labels have been added to the standard localization language pack definition, allowing you to customize these labels yourself. All aria label strings are prefixed with "aria" to make them easy to identify. Review each widget's localization reference page to find these new aria labels. Example: {{Link-SomewhereInThisVersion|manual=SDK|topic=WebChat-combined|anchor=localize|display text=WebChat Widget Localization}} reference.
+Aria labels are used throughout Genesys Widgets to supply callouts and context for screen readers. These labels have been added to the standard localization language pack definition, allowing you to customize these labels yourself. All aria label strings are prefixed with "aria" to make them easy to identify. Review each widget's localization reference page to find these new aria labels. Example: {{Link-SomewhereInThisVersion|manual=SDK|topic=WebChat-combined|anchor=localize|display text=WebChat Widget Localization}} reference.
 ===Configuration options===
 {{{!}} class="wikitable"

@@ Line 11: / Line 11: @@
 |anchor=overview
 |alignment=Vertical
-|structuredtext=Genesys provides a Voluntary Product Accessibility Template® - {{#Widget:ExtLink|link=https://www.itic.org/policy/accessibility/vpat/|displaytext=VPAT® report from ITI}}, to document conformance of Widgets to {{#Widget:ExtLink|link=https://www.w3.org/TR/WCAG21/|displaytext=WCAG 2.1 specification}}. The VPAT® report is a standardized template for documenting conformance to various accessibility specifications. The VPAT® report provided by Genesys follows the W3C/WAI’s {{#Widget:ExtLink|link=https://www.w3.org/TR/WCAG21/|displaytext=WCAG 2.1 specification}}, as this is an international standard adopted and recognized by our customers worldwide. The Genesys VPAT®  can be downloaded here: {{Repository|Genesys_Widgets_WCAG_2.1_AA_VPAT_version2.4.pdf|3=Genesys Widgets WCAG 2.1 AA VPAT®}}.
+|structuredtext=Genesys provides a Voluntary Product Accessibility Template® - [https://www.itic.org/policy/accessibility/vpat VPAT® report from ITI], to document conformance of Widgets to [https://www.w3.org/TR/WCAG21 WCAG 2.1 specification]. The VPAT® report is a standardized template for documenting conformance to various accessibility specifications. The VPAT® report provided by Genesys follows the W3C/WAI’s [https://www.w3.org/TR/WCAG21/ WCAG 2.1 specification], as this is an international standard adopted and recognized by our customers worldwide. The Genesys VPAT®  can be downloaded here: {{Repository|Genesys_Widgets_WCAG_2.1_AA_VPAT_version2.4.pdf|3=Genesys Widgets WCAG 2.1 AA VPAT®}}.
 |Status=No
 }}{{Section
@@ Line 17: / Line 17: @@
 |anchor=wiwcag
 |alignment=Vertical
-|structuredtext={{#Widget:ExtLink|link=https://www.w3.org/TR/WCAG21|displaytext=Web Content Accessibility Guidelines (WCAG) 2.1}} covers a wide range of recommendations for making Web content more accessible. Following these guidelines will make content more accessible to a wider range of people with disabilities and will also often make Web content more usable to users in general. WCAG relies on four guiding principles for building accessible UIs:
+|structuredtext=[https://www.w3.org/TR/WCAG21 Web Content Accessibility Guidelines (WCAG) 2.1] covers a wide range of recommendations for making Web content more accessible. Following these guidelines will make content more accessible to a wider range of people with disabilities and will also often make Web content more usable to users in general. WCAG relies on four guiding principles for building accessible UIs:
 #Perceivable: Information and user interface components must be presentable to users in ways they can perceive.
@@ Line 73: / Line 73: @@
 |sectionHeading=Keyboard accessibility
 |anchor=ka
-|alignment=Horizontal
+|alignment=Vertical
-|Media=GIF
+|structuredtext=[[File:Screen-Recording-2020-03-25-at-1.gif|472x472px]]
-|image=Screen-Recording-2020-03-25-at-1.gif
-|structuredtext=Supported Widgets are accessible via the keyboard. Users may navigate to and within any widget using the '''tab''' key or '''shift+tab''' key combo. For dropdowns and the date picker, the user can highlight a selection using the '''arrow''' keys. The '''enter''' or '''space''' key can then be used to make a selection, send a message, or activate a button.
+Supported Widgets are accessible via the keyboard. Users may navigate to and within any widget using the '''tab''' key or '''shift+tab''' key combo. For dropdowns and the date picker, the user can highlight a selection using the '''arrow''' keys. The '''enter''' or '''space''' key can then be used to make a selection, send a message, or activate a button.
 *'''tab''' - step forward to the next element
@@ Line 84: / Line 84: @@
 *'''space''' - make a selection or activate a button
-{{NoteFormat|In macOS, Safari Browser's accessibility {{#Widget:ExtLink|link=https://support.apple.com/en-in/guide/mac-help/mchlp1399/mac/ |displaytext=settings}} must be enabled to allow for proper keyboard navigation in Widgets.}}
+{{NoteFormat|In macOS, Safari Browser's accessibility [https://support.apple.com/en-in/guide/mac-help/mchlp1399/mac settings] must be enabled to allow for proper keyboard navigation in Widgets.|}}
 |Status=No
 }}{{Section
@@ Line 90: / Line 90: @@
 |anchor=ft
 |alignment=Vertical
-|structuredtext=In desktop browsers, when the {{Link-SomewhereInThisVersion|manual=SDK|topic=Engagement-combined|anchor=offer|display text=Engage Offer Widget}} is rendered in an overlay modal dialog with the background disabled, the focus is trapped within the content until it is closed. In mobile devices, all the widget layouts are expanded to full screen modal dialog. These mobile layouts contain the aria-modal property as recommended in the {{#Widget:ExtLink|link=https://www.w3.org/TR/wai-aria-practices/#dialog_modal|displaytext=W3C ARIA Dialog modal best practices}}.
+|structuredtext=In desktop browsers, when the {{Link-SomewhereInThisVersion|manual=SDK|topic=Engagement-combined|anchor=offer|display text=Engage Offer Widget}} is rendered in an overlay modal dialog with the background disabled, the focus is trapped within the content until it is closed. In mobile devices, all the widget layouts are expanded to full screen modal dialog. These mobile layouts contain the aria-modal property as recommended in the [https://www.w3.org/TR/wai-aria-practices/#dialog_modal W3C ARIA Dialog modal best practices].
 {{NoteFormat|Widgets does not add the "aria-hidden" attribute on the customer page html elements. Due to this limitation, when using screen reader gestures in some Android devices, the focus may not be trapped within the widget. To trap the focus, a custom event handling script needs to be added subscribing to the widget [[WID/Current/SDK/WebChat-combined#events|opened]] event. Also, add the "aria-hidden" attribute on the host page html elements, and remove them from subscribing to the corresponding [[WID/Current/SDK/WebChat-combined#events|closed/minimized]] events.|1}}
@@ Line 165: / Line 165: @@
 |structuredtext====Online===
-*{{#Widget:ExtLink|link=https://wave.webaim.org/|displaytext=webaim.org}}
+*[https://wave.webaim.org webaim.org]
-*{{#Widget:ExtLink|link=https://www.deque.com/axe/|displaytext=deque.com}}
+*[https://www.deque.com/axe deque.com]
-*{{#Widget:ExtLink|link=https://contrastchecker.com/|displaytext=contrastchecker.com}}
+*[https://contrastchecker.com contrastchecker.com]
 ===Screen readers===

@@ Line 9: / Line 9: @@
 |Section={{Section
 |sectionHeading=Overview
 |alignment=Vertical
 |structuredtext=Genesys provides a Voluntary Product Accessibility Template® - {{#Widget:ExtLink|link=https://www.itic.org/policy/accessibility/vpat/|displaytext=VPAT® report from ITI}}, to document conformance of Widgets to {{#Widget:ExtLink|link=https://www.w3.org/TR/WCAG21/|displaytext=WCAG 2.1 specification}}. The VPAT® report is a standardized template for documenting conformance to various accessibility specifications. The VPAT® report provided by Genesys follows the W3C/WAI’s {{#Widget:ExtLink|link=https://www.w3.org/TR/WCAG21/|displaytext=WCAG 2.1 specification}}, as this is an international standard adopted and recognized by our customers worldwide. The Genesys VPAT®  can be downloaded here: {{Repository|Genesys_Widgets_WCAG_2.1_AA_VPAT_version2.4.pdf|3=Genesys Widgets WCAG 2.1 AA VPAT®}}.
@@ Line 14: / Line 15: @@
 }}{{Section
 |sectionHeading=What is WCAG?
 |alignment=Vertical
 |structuredtext={{#Widget:ExtLink|link=https://www.w3.org/TR/WCAG21|displaytext=Web Content Accessibility Guidelines (WCAG) 2.1}} covers a wide range of recommendations for making Web content more accessible. Following these guidelines will make content more accessible to a wider range of people with disabilities and will also often make Web content more usable to users in general. WCAG relies on four guiding principles for building accessible UIs:
@@ Line 24: / Line 26: @@
 }}{{Section
 |sectionHeading=Support
 |alignment=Vertical
-|structuredtext=Widgets provides support for WCAG 2.1 Level AA for [[Draft:WID/Current/Developer/GWCSupportedBrowsers|desktop and mobile web browsers]]. However, not all Widgets meet these guidelines. The table below lists the Widgets that address and meet the standard accessibility requirements to help assist users with vision, hearing, or mobility impairments in gaining greater access to the customer support.
+|structuredtext=Widgets provides support for WCAG 2.1 Level AA for {{Link-SomewhereInThisVersion|manual=Developer|topic=GWCSupportedBrowsers|display text=desktop and mobile web browsers}}. However, not all Widgets meet these guidelines. The table below lists the Widgets that address and meet the standard accessibility requirements to help assist users with vision, hearing, or mobility impairments in gaining greater access to the customer support.
 ====Web Content Accessibility Guidelines (WCAG) 2.1, Level AA Plugin Support by Platform====
 {{{!}} class="wikitable"
@@ Line 55: / Line 58: @@
 }}{{Section
 |sectionHeading=Screen reader support
 |alignment=Vertical
 |structuredtext=Supported widgets are accessible via screen readers, which announce the following: all the textual and non-textual content on the Widgets window elements, new chat messages sent by the agent to the user, outgoing messages sent by the user to the agent, and error messages. To achieve a consistent reading behavior of live data across all the screen readers and the browsers, recommended ARIA live regions have been implemented in Web Chat for reading new messages.
@@ Line 84: / Line 88: @@
 }}{{Section
 |sectionHeading=Focus trap
-|anchor=Focus trap
+|anchor=ft
 |alignment=Vertical
 |structuredtext=In desktop browsers, when the {{Link-SomewhereInThisVersion|manual=SDK|topic=Engagement-combined|anchor=offer|display text=Engage Offer Widget}} is rendered in an overlay modal dialog with the background disabled, the focus is trapped within the content until it is closed. In mobile devices, all the widget layouts are expanded to full screen modal dialog. These mobile layouts contain the aria-modal property as recommended in the {{#Widget:ExtLink|link=https://www.w3.org/TR/wai-aria-practices/#dialog_modal|displaytext=W3C ARIA Dialog modal best practices}}.
@@ Line 92: / Line 96: @@
 }}{{Section
 |sectionHeading=Color contrast
 |alignment=Vertical
 |structuredtext=Text and background colors and buttons now meet WCAG 2.1 Level AA accessibility contrast guidelines. This allows text to be read clearly. There are changes in the default Widgets themes to increase color contrast in our Dark and Light themes. Changes include border, button, link, text, and background color adjustments to meet the contrast requirements while maintaining the same look and feel. In addition, there is an outline to indicate which element or section of each widget is in focus.
@@ Line 121: / Line 126: @@
 }}{{Section
 |sectionHeading=Browser zoom and text resizing
 |alignment=Vertical
 |structuredtext=Genesys Widgets supports zooming in and out, or resizing text using the browser's built-in controls. This makes it easier for some viewers to read text on the screen.
@@ Line 128: / Line 134: @@
 }}{{Section
 |sectionHeading=Customization
 |alignment=Vertical
 |structuredtext====Localization===
@@ Line 154: / Line 161: @@
 }}{{Section
 |sectionHeading=Resources and tools used
 |alignment=Vertical
 |structuredtext====Online===

@@ Line 15: / Line 15: @@
 |sectionHeading=What is WCAG?
 |alignment=Vertical
-|structuredtext={{#Widget:ExtLink|link=https://www.w3.org/TR/WCAG21/#abstract|displaytext=Web Content Accessibility Guidelines (WCAG) 2.1}} covers a wide range of recommendations for making Web content more accessible. Following these guidelines will make content more accessible to a wider range of people with disabilities and will also often make Web content more usable to users in general. WCAG relies on four guiding principles for building accessible UIs:
+|structuredtext={{#Widget:ExtLink|link=https://www.w3.org/TR/WCAG21|displaytext=Web Content Accessibility Guidelines (WCAG) 2.1}} covers a wide range of recommendations for making Web content more accessible. Following these guidelines will make content more accessible to a wider range of people with disabilities and will also often make Web content more usable to users in general. WCAG relies on four guiding principles for building accessible UIs:
 #Perceivable: Information and user interface components must be presentable to users in ways they can perceive.
@@ Line 31: / Line 31: @@
 !Genesys Cloud
 {{!}}-
-{{!}}{{Link-AnywhereElse|product=WID|version=Current|manual=SDK|topic=WebChat-combined | display text=Web Chat}}
+{{!}}{{Link-SomewhereInThisVersion|manual=SDK|topic=WebChat-combined|display text=WebChat}}
 {{!}}Level AA
 {{!}}-
-{{!}}{{Link-AnywhereElse|product=WID|version=Current|manual=SDK|topic=CallUs-combined | display text=Call Us}}
+{{!}}{{Link-SomewhereInThisVersion|manual=SDK|topic=CallUs-combined|display text=CallUs}}
 {{!}}Level AA
 {{!}}-
-{{!}}{{Link-AnywhereElse|product=WID|version=Current|manual=SDK|topic=ChannelSelector-combined | display text=Channel Selector}}
+{{!}}{{Link-SomewhereInThisVersion|manual=SDK|topic=ChannelSelector-combined|display text=ChannelSelector}}
 {{!}}Level AA
 {{!}}-
-{{!}}{{Link-AnywhereElse|product=WID|version=Current|manual=SDK|topic=Engagement-combined | display text=Engage}}
+{{!}}{{Link-SomewhereInThisVersion|manual=SDK|topic=Engagement-combined|display text=Engage}}
 {{!}}Level AA
 {{!}}-
-{{!}}{{Link-AnywhereElse|product=WID|version=Current|manual=SDK|topic=SideBar-combined | display text=Side Bar}}
+{{!}}{{Link-SomewhereInThisVersion|manual=SDK|topic=SideBar-combined|display text=SideBar}}
 {{!}}Level AA
 {{!}}-
-{{!}}[[WID/Current/SDK/Callback-combined{{!}}Callback]]
+{{!}}{{Link-SomewhereInThisVersion|manual=SDK|topic=Callback-combined|display text=Callback}}
 {{!}}Level AA
 {{!}}}
@@ Line 68: / Line 68: @@
 }}{{Section
 |sectionHeading=Keyboard accessibility
 |alignment=Horizontal
 |Media=GIF
@@ Line 85: / Line 86: @@
 |anchor=Focus trap
 |alignment=Vertical
-|structuredtext=In desktop browsers, when the [[WID/Current/SDK/Engagement-combined|Engage Offer Widget]] is rendered in an overlay modal dialog with the background disabled, the focus is trapped within the content until it is closed. In mobile devices, all the widget layouts are expanded to full screen modal dialog. These mobile layouts contain the aria-modal property as recommended in the {{#Widget:ExtLink|link=https://www.w3.org/TR/wai-aria-practices/#dialog_modal|displaytext=W3C ARIA Dialog modal best practices}}.
+|structuredtext=In desktop browsers, when the {{Link-SomewhereInThisVersion|manual=SDK|topic=Engagement-combined|anchor=offer|display text=Engage Offer Widget}} is rendered in an overlay modal dialog with the background disabled, the focus is trapped within the content until it is closed. In mobile devices, all the widget layouts are expanded to full screen modal dialog. These mobile layouts contain the aria-modal property as recommended in the {{#Widget:ExtLink|link=https://www.w3.org/TR/wai-aria-practices/#dialog_modal|displaytext=W3C ARIA Dialog modal best practices}}.
-{{NoteFormat|Widgets does not add the "aria-hidden" attribute on the customer page html elements. Due to this limitation, when using screen reader gestures in some Android devices, the focus may not be trapped within the widget. To trap the focus, a custom event handling script needs to be added subscribing to the widget [[WID/Current/SDK/WebChat-combined#API events|opened]] event. Also, add the "aria-hidden" attribute on the host page html elements, and remove them from subscribing to the corresponding [[WID/Current/SDK/WebChat-combined#API events|closed/minimized]] events.|1}}
+{{NoteFormat|Widgets does not add the "aria-hidden" attribute on the customer page html elements. Due to this limitation, when using screen reader gestures in some Android devices, the focus may not be trapped within the widget. To trap the focus, a custom event handling script needs to be added subscribing to the widget [[WID/Current/SDK/WebChat-combined#events|opened]] event. Also, add the "aria-hidden" attribute on the host page html elements, and remove them from subscribing to the corresponding [[WID/Current/SDK/WebChat-combined#events|closed/minimized]] events.|1}}
 |Status=No
 }}{{Section
@@ Line 123: / Line 124: @@
 |structuredtext=Genesys Widgets supports zooming in and out, or resizing text using the browser's built-in controls. This makes it easier for some viewers to read text on the screen.
-{{NoteFormat|The SideBar Widget can only support the zoom feature properly if it contains six or fewer rows. |1}}
+{{NoteFormat|The {{Link-SomewhereInThisVersion|manual=SDK|topic=SideBar-combined|display text=SideBar}} Widget can only support the zoom feature properly if it contains six or fewer rows. |1}}
 |Status=No
 }}{{Section
@@ Line 129: / Line 130: @@
 |alignment=Vertical
 |structuredtext====Localization===
-Aria labels are used throughout Genesys Widgets to supply callouts and context for screenreaders. These labels have been added to the standard localization language pack definition, allowing you to customize these labels yourself. All aria label strings are prefixed with "aria" to make them easy to identify. Review each widget's localization reference page to find these new aria labels. Example: {{Link-AnywhereElse|product=WID|version=Current|manual=SDK|topic=WebChat-combined#Localization |display text=WebChat Widget Localization Reference}}.
+Aria labels are used throughout Genesys Widgets to supply callouts and context for screenreaders. These labels have been added to the standard localization language pack definition, allowing you to customize these labels yourself. All aria label strings are prefixed with "aria" to make them easy to identify. Review each widget's localization reference page to find these new aria labels. Example: {{Link-SomewhereInThisVersion|manual=SDK|topic=WebChat-combined|anchor=localize|display text=WebChat Widget Localization}} reference.
 ===Configuration options===
 {{{!}} class="wikitable"
@@ Line 138: / Line 139: @@
 {{!}}-
 {{!}}WebChat
-{{!}}{{Link-AnywhereElse|product=WID|version=Current|manual=SDK|topic=WebChat-combined#Options |display text=ariaIdleAlertIntervals}}
+{{!}}{{Link-SomewhereInThisVersion|manual=SDK|topic=WebChat-combined|anchor=options|display text=ariaIdleAlertIntervals}}
 {{!}}An array containing the intervals as a percentage at which the screen reader will announce the remaining idle time. By default, it is enabled with the following time intervals, and it is customizable according to the user's needs. Configuring a value of <tt>false</tt> will let the screen reader call out idle time for every change.
 {{!}}-
 {{!}}WebChat
-{{!}}{{Link-AnywhereElse|product=WID|version=Current|manual=SDK|topic=WebChat-combined#Options |display text=ariaCharRemainingIntervals}}
+{{!}}{{Link-SomewhereInThisVersion|manual=SDK|topic=WebChat-combined|anchor=options|display text=ariaCharRemainingIntervals}}
 {{!}}An array containing the intervals as a percentage at which the screen reader will announce the remaining characters when the user inputs text into the message area. By default, it is enabled with the following intervals, and it is customizable according to user needs. Configuring a value of <tt>false</tt> will let the screen reader call out remaining characters for every change.
 {{!}}-
 {{!}}WebChat
-{{!}}{{Link-AnywhereElse|product=WID|version=Current|manual=SDK|topic=WebChat-combined#Customizable_Emoji_Menu | display text=emojiList}}
+{{!}}{{Link-SomewhereInThisVersion|manual=SDK|topic=WebChat-combined|anchor=options|display text=emojiList}}
 {{!}}emojiList must be configured with display names to support the screen reader calling out the emoji name. These emoji names are applied as '''aria-label''' attributes on the non-text emoji markup.
 {{!}}-

@@ Line 5: / Line 5: @@
 |Context=Learn how Widgets aligns with the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA.
 |ComingSoon=No
-|Platform=GenesysEngage-onpremises, PureConnect, GenesysCloud
+|Platform=GenesysEngage-cloud, PureConnect, GenesysCloud
 |Prereq=
 |Section={{Section

WID/Current/Developer/Accessibility - Revision history

WikiSysop at 20:46, May 24, 2022

Ed.jamer@genesys.com: Text replacement - "Genesys Cloud" to "Genesys Cloud CX"

Chrissy.forrest@genesys.com: Published

Chrissy.forrest@genesys.com: Published

Chrissy.forrest@genesys.com: Published

Chrissy.forrest@genesys.com: Published

Chrissy.forrest@genesys.com: Published

Chrissyforrest: Published

Chrissyforrest: Published

WikiSysop: Text replacement - "\|Platform=([^\|]*)GenesysEngage-onpremises([\|]*)" to "|Platform=$1GenesysEngage-cloud$2"

WikiSysop: Text replacement - "\|Platform=([^\|])GenesysEngage-onpremises([\|])" to "|Platform=$1GenesysEngage-cloud$2"