Thank you for your feedback.
Form temporarily unavailable. Please try again or contact docfeedback@servicenow.com to submit your comments.

Web Content Accessibility Guidelines (WCAG) 2.0

Log in to subscribe to topics and get notified when content changes.

Web Content Accessibility Guidelines (WCAG) 2.0

This page details the level of accessibility support for the Jakarta release, according to the Web Content Accessibility Guidelines (WCAG) 2.0.

W3C Recommendation 11 December 2008

Date: June 21, 2017

Product Name: ServiceNow Service Automation

Product Version Number: Jakarta

Vendor Company Name: ServiceNow

Vendor Contact Name: ServiceNow Compliance

Vendor Contact Email: compliance@servicenow.com

Table 1. Summary table
Guidelines Level of Support & Supporting Features Remarks and Explanations
Principle 1: Perceivable Supports with exceptions
Principle 2: Operable Supports with exceptions
Principle 3: Understandable Supports with exceptions
Principle 4: Robust Supports with exceptions

Principle 1: Perceivable - Information and user interface components must be presentable to users in ways they can perceive

Table 2. Guideline 1.1 Text Alternatives: Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols, or simpler language
Criteria Level of Support & Supporting Features Remarks and Explanations
1.1.1 Non-text Content: All non-text content that is presented to the user has a text alternative that serves the equivalent purpose, except for the situations listed below. (Level A) Supports with exceptions
Dependency Views (BSM map)
Business Service Map: Map options inaccessible without mouse scroll wheel or track pad.
Dependency graph structure is not conveyed to non-visual users.
Discovery
.NET/ Flex application control inaccessible with assistive technologies.
Service Catalog
Some images lack appropriate text alternatives.
Service Mapping
Build Segment Hierarchy drag and drop inaccessible without mouse.
Decorative calendar icons and Service Mapping arrow icons are missing alternative text.
Map tooltips contents inaccessible with screen reader.
Several unlabeled 0 buttons on the Business Service Map Toolbar dashboard.
System Properties
Reference lookup icons on the following system properties pages do not have the correct markup and are not treated as buttons.
  • System Properties > UI Properties
  • System Properties > System
1.2.1 Audio-only and Video-only (Prerecorded): For prerecorded audio-only and prerecorded video-only media, the following are true, except when the audio or video is a media alternative for text and is clearly labeled as such: (Level A) Not applicable
1.2.2 Captions (Prerecorded): Captions are provided for all prerecorded audio content in synchronized media, except when the media is a media alternative for text and is clearly labeled as such. (Level A) Not applicable
1.2.3 Audio Description or Media Alternative (Prerecorded): An alternative for time-based media or audio description of the prerecorded video content is provided for synchronized media, except when the media is a media alternative for text and is clearly labeled as such. (Level A) Not applicable
1.2.4 Captions (Live): Captions are provided for all live audio content in synchronized media. (Level AA) Not applicable
1.2.5 Audio Description (Prerecorded): Audio description is provided for all prerecorded video content in synchronized media. (Level AA) Not applicable
1.2.6 Sign Language (Prerecorded): Sign language interpretation is provided for all prerecorded audio content in synchronized media. (Level AAA) Not applicable
1.2.7 Extended Audio Description (Prerecorded): Where pauses in foreground audio are insufficient to allow audio descriptionsto convey the sense of the video, extended audio description is provided for all prerecorded video content in synchronized media. (Level AAA) Not applicable
Table 3. Guideline 1.3 Adaptable: Create content that can be presented in different ways (for example simpler layout) without losing information or structure
Criteria Level of Support & Supporting Features Remarks and Explanations
1.3.1 Info and Relationships: Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. (Level A) Supports with exceptions
Mobile
Mobile pages contain multiple Level 1 headings.
Project Management
Portfolio Workbench pages missing appropriate heading markup.
Service Catalog
Some headings missing appropriate markup on Emerging Products and ITSM CORE Service Catalog
Service Mapping
Incorrectly structured content
Markup is missing or incorrectly used.
Service Portal
Service Portal landing page contains multiple Level 1 headings.
Survey Management
Questionnaire template components lack appropriate markup for lists
UI components
Fiscal Calendar tables are used for layout purposes.
Some headings missing appropriate markup in Fiscal Calendar
Some headings missing appropriate markup on Example SLA Definitions page
Some pop-out panels are not accessible to screen readers
1.3.2 Meaningful Sequence: When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined. (Level A) Supports with exceptions
Service Mapping
Service Mapping (ITOM) pages have unexpected focus order
Workflow
Tab does not work inside workflow of admin role's Workflow Editor
Tab skips help and refresh button in admin role's Workflow Editor

1.3.3 Sensory Characteristics: Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, size, visual location, orientation, or sound. (Level A)

Supports with exceptions
Dependency Views (BSM map)
Zoom (+ or -) buttons on Dependency Views Map not part of tab order
Survey Management
Left control panel in Survey Designer is not read in logical order
Table 4. Guideline 1.4 Distinguishable: Make it easier for users to see and hear content including separating foreground from background
Criteria Level of Support & Supporting Features Remarks and Explanations
1.4.1 Use of Color: Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. (Level A) Supports with exceptions
Dependency Views (BSM map)
Dependency Views Map not accessible for color blind users.
Field Service Management
My Schedule page for Field Service Management relies solely on color to convey information.
Survey Management
Questionnaire Template Designer not accessible to color-blind users.
UI components
Error messages indicated by color alone in Fiscal Calendar
Some pages have links without underlining, making it difficult for color blind users to differentiate links from regular text.
1.4.2 Audio Control: If any audio on a Web page plays automatically for more than 3 seconds, either a mechanism is available to pause or stop the audio, or a mechanism is available to control audio volume independently from the overall system volume level. (Level A) Not applicable
1.4.3 Contrast (Minimum): The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, except for the following: (Level AA) Supports with exceptions
Change Management
Elements may not have sufficient color contrast
Knowledge Management
Color contrast is insufficient
Mobile
Some mobile pages have insufficient contrast ratio
Reporting
Color contrast is insufficient throughout
Reporting page elements are not honored in Windows High Contrast mode
Service Mapping
ITOM Service Mapping page elements are not honored in Windows High Contrast mode
UI components
Ask Question button and cursor do not have sufficient contrast in Open Questions module
Color contrast is insufficient throughout
Default color setting for UI16 left-hand navigation does not meet minimum color contrast ratio
Default UI16 theme does not meet minimum accessible contrast ratio.
Fiscal Calendar color contrast is insufficient
Page elements are not honored in Windows High Contrast mode
Profile circles and card text do not meet minimum color contrast requirements.

1.4.4 Resize text: Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality. (Level AA)

Supports with exceptions
Financial Management
Some contents in Emerging Products do not render properly when zoomed
Schedules
Zooming and scaling must not be disabled.
Service Portal
Zoom is disabled in Service Portal
UI components
Some forms have text that do not resize correctly
Zoom gestures are disabled
1.4.5 Images of Text: If the technologies being used can achieve the visual presentation, text is used to convey information rather than images of text except for the following: (Level AA) Not applicable
1.4.6 Contrast (Enhanced): The visual presentation of text and images of text has a contrast ratio of at least 7:1, except for the following: (Level AAA) Supports with exceptions See 1.4.3
1.4.7 Low or No Background Audio: For prerecorded audio-only content that (1) contains primarily speech in the foreground, (2) is not an audio CAPTCHA or audio logo, and (3) is not vocalization intended to be primarily musical expression such as singing or rapping, at least one of the following is true: (Level AAA) Not applicable
1.4.8 Visual Presentation: For the visual presentation of blocks of text, a mechanism is available to achieve the following: (Level AAA) Not supported
1.4.9 Images of Text (No Exception): Images of text are only used for pure decoration or where a particular presentation of text is essential to the information being conveyed. (Level AAA) Not applicable

Principle 2: Operable - User interface components and navigation must be operable

Table 5. Guideline 2.1 Keyboard Accessible: Make all functionality available from a keyboard
Criteria Level of Support & Supporting Features Remarks and Explanations

2.1.1 Keyboard: All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints. (Level A)

Supports with exceptions
Application Portfolio Management (APM)
Bubble chart bubble right-click action is not accessible by keyboard
Scalable Vector Graphics tooltips not accessible without keyboard and not readable by VoiceOver in Safari.
Configuration Management Database (CMDB)
Many controls are skipped from the tab order in CMDB Query Builder
The following controls are not part of the tab order:
  • Dashboard Menu - CI dashboard shows health reports at CI level
  • Timeline slider - CI dashboard shows health reports at CI level
  • Form controls - CI dashboard shows health reports at CI level
  • Graph bars - Relationship Dashboard
  • Refresh icon - Relationship Dashboard
Unable to create connections on the canvas via keyboard in CMDB Query Builder
Unable to move items onto canvas using only keyboard in CMDB Query Builder
Dependency Views (BSM map)
Cannot select save view, load view, last view and export image options of Dependency Views Map using keyboard
Cannot toggle between options via keyboard on Dependency Views Map
Dependency Views Map indicators not part of tab order
Dependency Views Map reset button is not accessible via keyboard
Dependency Views Map settings options are not part of tab order
Menu buttons are not keyboard accessible
No keyboard equivalent to right-click functions on Dependency Views Map
Pop-out panels in the dependency map are not accessible by keyboard
Search for CI works with arrows+ space+enter and not with tab and enter
Unable to open any closed regions of Relationship Formatter with keyboard
View button in Relationship Formatter not part of tab order
Discovery
It is not possible to edit a set of pattern steps using the keyboard
It is not possible to walk through the steps tree using the keyboard
Names within steps not in the tab order of Pattern Designer
No keyboard equivalent to right-click functions in Pattern Designer
The Listed CI Types button is not in the tab order in Pattern Designer
Unable to edit items in the Pattern Designer list via keyboard
Field Service Management
Elements of Field Service Management are not keyboard accessible
Financial Management
Emerging Products drag and drop functionality on the build segment hierarchy cannot be performed using the keyboard.
No keyboard equivalent for Building segment hierarchy
Tooltips in Expense Summary table inaccessible via keyboard
Knowledge Management
Knowledge Home Page does not use appropriate heading markup
Some Knowledge Management buttons are inaccessible by keyboard
Mobile
Advance Filter button not part of tab order
Reporting
Fly-out panels are not keyboard accessible
Service Mapping
Context menu of Business Service Map not accessible with keyboard
Expand/Collapse behavior on Service Mapping page is not accessible via keyboard.
Information beyond second column of Change List are not accessible by keyboard.
Items on the Service Mapping view map are not keyboard accessible
Items on the topology map are not accessible by keyboard.
Map Navigation Widget is not accessible via keyboard
No keyboard equivalent to right-click functions on Business Service Map
Operations in the Business Service Tree are not accessible by keyboard.
Pop-out panels on Service Mapping page are not accessible via keyboard.
Scalable Vector Graphics controls not accessible by keyboard
Service Mapping tabbed navigations experiences some unexpected behaviors.
Service Mapping tooltip is not available to keyboard-only users, speech input users, and screen reader users
The Services tree is not navigable via keyboard
Unable to access Adding Manual Connection and Add Management IP menus via keyboard
Survey Management
Properties dialog box cannot be dismissed with the keyboard in Questionnaire Templates Designer
Questionnaire Template Designer drag and drop functionality on the build segment hierarchy cannot be performed using the keyboard.
UI components
Custom buttons in Fiscal Calendar are not accessible via keyboard
Edit Module and Add To Favorites buttons are not accessible via keyboard.
Get Help form instructions are not accessible without mouse.
Tooltip for Info icon is inaccessible via keyboard
Unable to close pop-up from List v3 debug pop up icon via keyboard.
Workflow
Stage rendering and Stage order dropdowns in admin role's Workflow Editor are not accessible by keyboard

2.1.2 No Keyboard Trap: If keyboard focus can be moved to a component of the page using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, the user is advised of the method for moving focus away. (Level A)

Supports with exceptions
Dependency Views (BSM map)
Unable to set focus on Dependecy Views Map indicators
Service Mapping
Delete linked identification section/connection section pop-up does not get focus when invoked in Pattern Designer
Unable to set focus on expand/collapse icons of Business Service Map
2.1.3 Keyboard (No Exception): All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes. (Level AAA) Not supported See 2.1.1
Table 6. Guideline 2.2 Enough Time: Provide users enough time to read and use content
Criteria Level of Support & Supporting Features Remarks and Explanations
2.2.1 Timing Adjustable: For each time limit that is set by the content, at least one of the following is true: (Level A) Supports
2.2.2 Pause, Stop, Hide: For moving, blinking, scrolling, or auto-updating information, all of the following are true: (Level A) Supports
2.2.3 No Timing: Timing is not an essential part of the event or activity presented by the content, except for non-interactive synchronized media and real-time events. (Level AAA) Not applicable
2.2.4 Interruptions: Interruptions can be postponed or suppressed by the user, except interruptions involving an emergency. (Level AAA) Not applicable
2.2.5 Re-authenticating: When an authenticated session expires, the user can continue the activity without loss of data after re-authenticating. (Level AAA) Supports with exceptions Support depends on customer customization. If the instance permits the user to use the Remember me flag on their sessions, the whole re-authorization process is entirely invisible.
Table 7. Guideline 2.3 Seizures: Do not design content in a way that is known to cause seizures
Criteria Level of Support & Supporting Features Remarks and Explanations
2.3.1 Three Flashes or Below Threshold: Web pages do not contain anything that flashes more than three times in any one second period, or the flash is below the general flash and red flash thresholds. (Level A) Supports
2.3.2 Three Flashes: Web pages do not contain anything that flashes more than three times in any one second period. (Level AAA) Supports
Table 8. Guideline 2.4 Navigable: Provide ways to help users navigate, find content, and determine where they are
Criteria Level of Support & Supporting Features Remarks and Explanations

2.4.1 Bypass Blocks: A mechanism is available to bypass blocks of content that are repeated on multiple Web pages. (Level A)

Supports with exceptions
Dependency Views (BSM map)
Question Template Designer landmarks are not identified by screen readers.
Survey Management
Question Template Designer landmarks are not identified by screen readers.
2.4.2 Page Titled: Web pages have titles that describe topic or purpose. (Level A) Supports
2.4.3 Focus Order: If a Web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability. (Level A) Supports with exceptions
Automated Test Framework
Unexpected tab order in Glide Modal. User is allowed to tab to elements outside the modal.
Dependency Views (BSM map)
CI search box not included in tab order
Dependency Views pages contain several cases where the tab order behaves in unexpected ways.
Focus does not center on Dependency Views Map
Tab order on BSM does not follow logical order.
Tab sometimes skips both vertical and horizontal tab on Dependency Views Map
Discovery
Focus moves outside form after the list selections in Pattern Designer
Knowledge Management
Article rating bar not accessible via keyboard with Chrome and Safari browsers
Lists
Date/Time field in v2 list editor is loses focus
Password Reset Application
Hidden elements fall into focus order
Service Catalog
Hidden elements of Service Catalog fall into focus order
Unexpected focus order on Catalog home page
Elements of Service Catalog lack focus indication
Service Mapping
Connect to and Create New business service options are not part of tab order
Business Service timeline is not part of tab order
Captions and values of the Properties Panel of Technical Business Service are not part of the tab order
Comparison drop down panel of Business Service Map is not part of tab order
Data from the dashboard is skipped in the tab order
Icons on the Properties Panel of the Discovered Service Map are not part of the tab order
Some items on Compliance Dashboard are not part of tab order
Survey Management
Focus moves in unexpected order in Questionnaire Templates Designer.
UI components
Expand/Collapse behavior on Performance Analytics and Reporting Create a Report page is not accessible via keyboard.
Mobile
In mobile lists, the Sort menu has inadequate focus, making some functions difficult for screen reader users.
2.4.4 Link Purpose (In Context): The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general. (Level A) Supports with exceptions
Knowledge Management
Links used to perform a function in Knowledge Base where it is preferable to use buttons.
Service Portal
Service Portal landing page uses links as buttons and may be confusing with assistive technologies
2.4.5 Multiple Ways: More than one way is available to locate a Web page within a set of Web pages except where the Web Page is the result of, or a step in, a process. (Level AA) Supports
2.4.6 Headings and Labels: Headings and labels describe topic or purpose. (Level AA) Supports with exceptions
Dependency Views (BSM map)
Settings button in Relationship Formatter do not have labels
Field Service Management
Page and iFrame titles are not sufficient to describe content on Central Dispatch page
2.4.7 Focus Visible: Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible. (Level AA) Supports with exceptions
Service Mapping
Focus indication is inadequate
UI components
Focus for "Display Aging Report" is not adequate for in IE11
Focus indication is inadequate
Focus indication is inadequate on global header
Some pages have elements that are not visible to focus indicator
Some pages contain elements with visible focus indicators that are inadequate, depending on the browser and whether high contrast mode is in use

2.4.8 Location: Information about the user's location within a set of Web pages is available. (Level AAA)

Supports with exceptions Not available for all pages. Breadcrumbs and workflow ribbons allow user to jump back through pages where user must go from Page A to B to C.
2.4.9 Link Purpose (Link Only): A mechanism is available to allow the purpose of each link to be identified from link text alone, except where the purpose of the link would be ambiguous to users in general. (Level AAA) Supports with exceptions Not all links in the system have been evaluated against this criterion.

2.4.10 Section Headings: Section headings are used to organize the content. (Level AAA)

Not applicable

Principle 3: Understandable - Information and the operation of user interface must be understandable

Table 9. Guideline 3.1 Readable: Make text content readable and understandable
Criteria Level of Support & Supporting Features Remarks and Explanations
3.1.1 Language of Page: The default human language of each Web page can be programmatically determined. (Level A) Supports with exceptions
Dependency views (BSM map)
Default language is not tagged for some pages.
3.1.2 Language of Parts: The human language of each passage or phrase in the content can be programmatically determinedexcept for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text. (Level AA) Supports with exceptions See 3.1.1
Note: In cases where a language switch could occur within the same page, it happens because an end-user comments in a different language than what the viewer is currently set to.
3.1.3 Unusual Words: A mechanism is available for identifying specific definitions of words or phrases used in an unusual or restricted way, including idioms and jargon. (Level AAA) Not supported
3.1.4 Abbreviations: A mechanism for identifying the expanded form or meaning of abbreviations is available. (Level AAA) Not supported
3.1.5 Reading Level: When text requires reading ability more advanced than the lower secondary education level after removal of proper names and titles, supplemental content, or a version that does not require reading ability more advanced than the lower secondary education level, is available. (Level AAA) Not supported
3.1.6 Pronunciation: A mechanism is available for identifying specific pronunciation of words where meaning of the words, in context, is ambiguous without knowing the pronunciation. (Level AAA) Not supported
Table 10. Guideline 3.2 Predictable: Make Web pages appear and operate in predictable ways
Criteria Level of Support & Supporting Features Remarks and Explanations
3.2.1 On Focus: When any component receives focus, it does not initiate a change of context. (Level A) Supports with exceptions
Reporting
Unexpected behavior associated with autocomplete menus
3.2.2 On Input: Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component. (Level A) Supports with exceptions
Survey management
Properties dialog box in Questionnaire Templates Designer not accessible by keyboard.
3.2.3 Consistent Navigation: Navigational mechanisms that are repeated on multiple Web pages within a set of Web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user. (Level AA) Supports with exceptions Consistent as long as user is navigating the UI within the frameset at all times.
3.2.4 Consistent Identification: Components that have the same functionality within a set of Web pages are identified consistently. (Level AA) Supports with exceptions
Password Reset Application
Password reset: Some headings are missing the appropriate markup
Reporting
Report designer does not use appropriate heading markup
3.2.5 Change on Request: Changes of context are initiated only by user request or a mechanism is available to turn off such changes. (Level AAA) Supports with exceptions
Core platform
Some headings are missing the appropriate markup
Table 11. Guideline 3.3 Input Assistance: Help users avoid and correct mistakes
Criteria Level of Support Remarks and Explanations
3.3.1 Error Identification: If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text. (Level A) Supports
3.3.2 Labels or Instructions: Labels or instructions are provided when content requires user input. (Level A) Supports with exceptions
Automated Test Framework
Fields using CodeMirror are not compatible with screen readers.
Configuration Management Database (CMDB)
Some actions that cause a change to the UI don't announce that the changes occurred in CMDB Query Builder
Dependency Views (BSM map)
Form controls are labeled incorrectly
On clicking Expand and Collapse of Dependency Views Map, user is not informed of change
Discovery
No notification of the new information upon save, delete or publish in Pattern Designer
Service Mapping
Service Mapping View Map form controls are not correctly labeled
Survey Management
Configuration and Availability panels for admin users do not have appropriate labels
Instructions for WYSIWYG editor in Questionnaire Templates Designer is not accessible to assistive technology.
UI components
Required or invalid fields are not indicated in an accessible way
There is no visible label for the toggle column search button in lists.
3.3.3 Error Suggestion: If an input error is automatically detected and suggestions for correction are known, then the suggestions are provided to the user, unless it would jeopardize the security or purpose of the content. (Level AA) Supports with exceptions Not all input error messages provide suggestions for correction.
3.3.4 Error Prevention (Legal, Financial, Data): For Web pages that cause legal commitments or financial transactions for the user to occur, that modify or delete user-controllable data in data storage systems, or that submit user test responses, at least one of the following is true: (Level AA) Supports Supported out of the box. Customization may affect support.
3.3.5 Help: Context-sensitive help is available. (Level AAA) Supports with exceptions A number of context-sensitive help features are available in the platform.
3.3.6 Error Prevention (All): For Web pages that require the user to submit information, at least one of the following is true: (Level AAA) Supports Supported out of the box. Customization may affect support.

Principle 4: Robust - Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies

Criteria Level of Support Remarks and Explanations
4.1.1 Parsing: In content implemented using markup languages, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique, except where the specifications allow these features. (Level A) Supports with exceptions
Knowledge Management
Parsing errors that can hinder assistive technologies are present
Service Mapping
Parsing errors that can hinder assistive technologies are present
The slider widget within the Service Mapping (ITOM) section of the website is not fully operable using the keyboard
UI components
IDs on some UI pages are not unique which can cause problems for assistive technologies when they are trying to interact with the page
4.1.2 Name, Role, Value: For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies. (Level A) Supports with exceptions
Assessments
Voice Over selects input content instead of input of admin role's Survey Designer configuration page when using Chrome on Mac.
Connect
In Connect, screen readers announce placeholder text in the conversation filter and the message field.
In Connect, some tooltips are not accessible via keyboard.
Dependency views (BSM map)
Map Settings are not marked up appropriately for assistive technology.
Saving success message is not stated by Assistive Technologies
Sortable data tables do not indicate sorted state
Toggle buttons are not accessible to screen readers.
Discovery
Patter Designer OS (Operations System) field has no label for JAWS
Field Service Management
Central Dispatch page contains menu buttons that are not tab-accessible; navigation is available via arrow keys.
Field Service Management messages are not read by screen readers.
Financial Management
Content in Add New Segment dialog box inaccessible to assistive technology
Forms and fields
Security Incident: Post Incident Review reports is not announced by screen reader
Human resources
Assistive tool does not announce campus building name inside the campus map.
Knowledge Management
Assistive Technologies do not tell the user anything about the results of a search
Lists
Progress bar for activating/upgrading a plugin does not announce to screen readers
Project Management
Project and Portfolio Management elements do not have the correct role applied
Reporting
Table column sort behavior on Performance Analytics and Reporting Create a Report page is not accessible with assistive technology.
Service Catalog
The controls within the Add Panel dialog box have incorrect labels
Service Mapping
Messages about starting and cancelling discovery are not stated by assistive technologies.
Service Mapping (ITOM) form within pop-up is not read by assistive technologies.
Service Mapping toggle buttons have some compatibility issues with accessibility tools:
  • State of button is not correctly exposed to assistive technologies
  • Correct role is not applied to some buttons.
  • Some buttons incorrectly coded as a tablist.
Service Portal
Assistive tool does not announce links on SP landing page
Form controls are labeled incorrectly on Service Portal landing page, making it difficult for users with screen readers using IE11 + JAWS
Survey Management
Controls within the "Properties" dialog box do not necessarily respond correctly to assistive technologies
Question Template Designer messages are not read by screen readers.
UI components
After receiving error message, a second console error message appears
NVDA reads the same label twice for several items in the banner frame
Screen reader does not announce alert text to notify of missing mandatory fields for My Notifications Preferences of Self-Service.
System Administrator menu in global header contains excessive text
Using VoiceOver and Safari you cannot tell the current sort order of the table
VoiceOver does not read pop up options for List v3
Visual Task Boards
The Create Data-Driven Board screen is inaccessible with VoiceOver in Safari
Workflow
JAWS does not announce current stage or stage details for the admin role's Workflow Editor
Feedback