Criteria | Supporting Features | Remarks (e.g., definition, equivalent facilitation, scope of support provided) |
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) - Controls, Input: If non-text content is a control or accepts user input, then it has a name that describes its purpose. (Refer to Guideline 4.1 for additional requirements for controls and content that accepts user input.)
- Time-Based Media: If non-text content is time-based media, then text alternatives at least provide descriptive identification of the non-text content. (Refer to Guideline 1.2 for additional requirements for media.)
- Test: If non-text content is a test or exercise that would be invalid if presented in text, then text alternatives at least provide descriptive identification of the non-text content.
- Sensory: If non-text content is primarily intended to create a specific sensory experience, then text alternatives at least provide descriptive identification of the non-text content.
- CAPTCHA: If the purpose of non-text content is to confirm that content is being accessed by a person rather than a computer, then text alternatives that identify and describe the purpose of the non-text content are provided, and alternative forms of CAPTCHA using output modes for different types of sensory perception are provided to accommodate different disabilities.
- Decoration, Formatting, Invisible: If non-text content is pure decoration, is used only for visual formatting, or is not presented to users, then it is implemented in a way that it can be ignored by assistive technology.
| Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Images that convey information have meaningful alternative text using ALT
- Images that are decorative are marked up using ALT=”” or CSS background images
- Controls have an associated name
- Non-text characters are not used or have meaningful alternative text
Exceptions: - Expand/Collapse icons on data forms in screen reader mode are not correctly defined. As a result screen readers don’t read it correctly, e.g. when expanding a column in a data form, it would not read the dimension member name being expanded. Bug ID: 19245678
- In the simplified interface of Planning mode, toolbar buttons are read as "radio button links" by screen reader. Bug ID: 19150252
- The Instructions feature on Planning web pages, e.g. Instructions for a Task list etc., are shown with HTML tags making it difficult to be read by screen reader. Bug ID: 17037429
|
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) Prerecorded Audio-only: An alternative for time-based media is provided that presents equivalent information for prerecorded audio-only content. Prerecorded Video-only: Either an alternative for time-based media or an audio track is provided that presents equivalent information for prerecorded video-only content.
| Product has been developed to conform to this standard subject to the remarks on the right. | The product does not include audio-only or video-only supported functionality. |
| 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) | Product has been developed to conform to this standard subject to the remarks on the right. | The product has no audio-only content. |
| 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) | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Pre-recorded video includes an alternative to the video
|
| 1.2.4 Captions (Live): Captions are provided for all live audio content in synchronized media. (Level AA) | Product has been developed to conform to this standard subject to the remarks on the right. | The product has no live media content. |
| 1.2.5 Audio Description (Prerecorded): Audio description is provided for all prerecorded video content in synchronized media. (Level AA) | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Pre-recorded video includes an alternative to the video
|
| 1.3.1 Info and Relationships: Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. (Level A) | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for : - User interface component labels are associated with the fields they are labeling
- Headings are encoded with HTML heading tags
- List markup is used for marking up lists
- Table markup is used for marking up data tables, including row and column headers and table captions/summaries where appropriate
- Data tables specify SUMMARY or CAPTION
- Layout tables use appropriate markup
- Groups of components are marked up with their description
- Style sheets are used only to change the layout and presentation on the screen
Exceptions - Task list status and Task list in Right pane are not read with their row and column context and hence it's difficult for screen reader user to understand the content. Bug ID: 20121519
- There are places in application where data is presented as tabular data but not presented as a data table, e.g. Point of View (POV). Bug ID: 20108314
- In the simplified interface, headers are not defined correctly in create dashboard screen. Bug ID: 19489584
|
| 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) | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - The sequence of elements in the Document object model (DOM) matches a logical reading sequence
Exceptions: - In the simplified interface, tab order is not correctly defined. Action items for screens, e.g. save, cancel, finish, next etc., are on the top of the page and hence these are first in tab order, where as the user would want to complete other operations on the page and then reach these action buttons. Bug ID: 19362240
- Tab order is not correct in form folder. Bug ID: 19863667
- Navigation through the left-hand pane to select a form or task list requires the end user to press the down arrow until they reach the desired task. The end user is not able to navigate directly to the parent (folder) to find the task. Bug ID: 16402997
|
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)
Note: For requirements related to color, refer to Guideline 1.4. | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Instructions provided do not refer to things solely based on their sensory characteristics such as shape, size, visual location, orientation, color, or sound
|
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)
Note: This success criterion addresses color perception specifically. Other forms of perception are covered in Guideline 1.3 including programmatic access to color and other visual presentation coding. | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Information conveyed by color is available in alternative formats, such as shape, text, font weight
- Information conveyed by color has a contrast ratio of at least 3:1
|
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)
Note: Since any content that does not meet this success criterion can interfere with a user's ability to use the whole page, all content on the Web page (whether or not it is used to meet other success criteria) must meet this success criterion. See Conformance Requirement 5: Non-Interference. | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - No automatically playing audio is used.
|
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)
- Large Text: Large-scale text and images of large-scale text have a contrast ratio of at least 3:1;
- Incidental: Text or images of text that are part of an inactive user interface component, that are pure decoration, that are not visible to anyone, or that are part of a picture that contains significant other visual content, have no contrast requirement.
- Logotypes: Text that is part of a logo or brand name has no minimum contrast requirement.
| Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Large-scale text and images of large-scale text have a contrast ratio of at least 3:1
- Other text and images of text have a contrast ratio of at least 4.5:1
Exceptions: - Color Contrast issues are seen on a few workspace and simplified screens. Bug ID: 20222366 & 20222398
|
| 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) | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Text can be resized up to 200% without loss of content or functionality
Exceptions: - Perform text resize/zoom results in the following elements not being seen correctly: right-click menus and Composite forms. Bug ID: 19903852, 19903355, & 19902918
- With browser display re-sized to 200%, a portion of the data forms is not rendered correctly when user scrolls through it. Bug ID: 19276427
|
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) - Customizable: The image of text can be visually customized to the user's requirements;
- Essential: A particular presentation of text is essential to the information being conveyed.
Note: Logotypes (text that is part of a logo or brand name) are considered essential. | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Images of text are not used
|
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)
Note 1: This exception relates to the underlying function, not the input technique. For example, if using handwriting to enter text, the input technique (handwriting) requires path-dependent input but the underlying function (text input) does not.
Note 2: This does not forbid and should not discourage providing mouse input or other input methods in addition to keyboard operation. | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Ability to perform functions from the keyboard only, and without requiring specific timings for individual keystrokes
- Proper operation of unique keystrokes and access keys, including those listed in the product documentation
Exceptions: - Simple and Composite data forms have problems in navigating with data cells. Bug ID: 19864504
- Tab order is not correct in form folder. Bug ID: 19863667
- All popup messages are not read by Screen reader. Bug ID: 20174067
- Business rule attached to data form cannot be invoked in normal mode. Bug ID: 20121519
- In Screen reader mode, confirmation and Error messages are not displayed. Bug ID: 20094508
- Forms in Form folders are read twice by screen readers. Bug ID: 20121519
- Screen reader doesn't announce the label "Opening Form" or "Opening Task List" when opening a form or task list that takes time. Bug ID: 9059986
- Every page refresh (server-side call) like saving data or changing smart lists takes focus out of the data entry forms. Bug ID: 13775131
- Column Header isn't associated with the expand/collapse action in all data entry forms. The expand/collapse icon precedes the column headers making it difficult for users to know what columns they will be expanding/collapsing. Bug ID: 13637387
- Navigation through the left-hand pane to select form or task list requires the end user to press the down arrow until they reach the desired task. The end user is not able to navigate directly to the parent (folder) to find the task. Bug ID: 16402997
- On opening a form with tabs then using Ctrl+Shift+T to move from the current tab to the next tab, the screen reader control will be on the previous tab and announce it again. Bug ID: 16410412
- The left hand task list accordion is shown twice upon invoking screen reader mode. Bug ID: 13637414
- In the simplified interface, there is limited support for navigation using short-cut keys. User will need to use tab and Shift+tab key as primary navigation key. Bug ID: 19276639
- In non-screen reader mode, when working with tree controls, e.g. Task lists and data forms, focus does not move to lower level elements and hence these cannot be invoked using keyboard only navigation. Bug ID: 19467568
- In the simplified interface, tab order is not correctly defined. Action items for screens, e.g. save, cancel, finish, next etc. are on the top of the page and hence these are first in tab order, where as user would want to complete other operations on the page and then reach these action buttons. Bug ID: 19362240
- In the simplified interface, there is limited support for Accelerator Keys. Many of the commonly used actions, e.g. Refresh, Actions, Save, Create and Close, Clear, Apply, Schedule and Next, etc. would need to be invoked using tab or Shift+Tab keys. Bug ID: 19274748
- In the simplified interface of Planning, keyboard navigation does not work on supporting details page. Bug ID: 19364819
- In Planning data forms, page drop downs for dimensions are shown as disabled even when the selected values can be changed using member selector. Bug ID: 19365122
- In Tree view or Tree table type components e.g. Dimension editor, Task lists, leaf level members without any children are also shown with the expand icon. This confuses the user to think that these items have a child and they need to click or expand even when these are leaf level members. Bug ID: 17218454
- In the Planning simplified interface, if a popup dialogue does not have close button on it, it can not be closed. Bug ID: 19300287
- In non-screen reader mode, focus does not move to confirmation or error message dialogs. Bug ID: 19467568
- In Screen reader mode, activating an error message in the Data Validation Summary popup doesn't take focus back to the cell in the Planning gird showing validation error. Bug ID: 13713254. Workaround: users have to tab through each cell to find out which cells encountered an error.
- In the non-screen reader mode, navigating through tree structures using key board has issues as moving control would keep on opening the elements even if user did not want to, e.g. if you are trying to open a certain data form in data form list using arrow keys, all data forms will keep opening when focus moves to them. Bug ID: 20671089
- Simplified UI data forms - There are issues with navigation and reading of cells intersections by screen reader. Bug ID: 20371852 & 20292129
- Provide feedback feature is not accessible using keyboard. Bug ID: 20973480
|
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)
Note: Since any content that does not meet this success criterion can interfere with a user's ability to use the whole page, all content on the Web page (whether it is used to meet other success criteria or not) must meet this success criterion. See Conformance Requirement 5: Non-Interference. | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Movement of focus through each control only using the keyboard, with no "keyboard trap" that prevents focus from moving away from any control
|
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)
- Turn off: The user is allowed to turn off the time limit before encountering it; or
- Adjust: The user is allowed to adjust the time limit before encountering it over a wide range that is at least ten times the length of the default setting; or
- Extend: The user is warned before time expires and given at least 20 seconds to extend the time limit with a simple action (for example, "press the space bar"), and the user is allowed to extend the time limit at least ten times; or
- Real-time Exception: The time limit is a required part of a real-time event (for example, an auction), and no alternative to the time limit is possible; or
- Essential Exception: The time limit is essential and extending it would invalidate the activity; or
- 20 Hour Exception: The time limit is longer than 20 hours.
Note: This success criterion helps ensure that users can complete tasks without unexpected changes in content or context that are a result of a time limit. This success criterion should be considered in conjunction with Success Criterion 3.2.1, which puts limits on changes of content or context as a result of user action. | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Application timeout options to continue or exit are provided after a period of application inactivity.
|
2.2.2 Pause, Stop, Hide: For moving, blinking, scrolling, or auto-updating information, all of the following are true: (Level A)
- Moving, blinking, scrolling: For any moving, blinking or scrolling information that (1) starts automatically, (2) lasts more than five seconds, and (3) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it unless the movement, blinking, or scrolling is part of an activity where it is essential; and
- Auto-updating: For any auto-updating information that (1) starts automatically and (2) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it or to control the frequency of the update unless the auto-updating is part of an activity where it is essential.
Note 1: For requirements related to flickering or flashing content, refer to Guideline 2.3.
Note 2: Since any content that does not meet this success criterion can interfere with a user's ability to use the whole page, all content on the Web page (whether it is used to meet other success criteria or not) must meet this success criterion. See Conformance Requirement 5: Non-Interference.
Note 3: Content that is updated periodically by software or that is streamed to the user agent is not required to preserve or present information that is generated or received between the initiation of the pause and resuming presentation, as this may not be technically possible, and in many situations could be misleading to do so.
Note 4: An animation that occurs as part of a preload phase or similar situation can be considered essential if interaction cannot occur during that phase for all users and if not indicating progress could confuse users or cause them to think that content was frozen or broken. | Product has been developed to conform to this standard subject to the remarks on the right. | There is no moving, blinking, or scrolling content. |
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)
Note: Since any content that does not meet this success criterion can interfere with a user's ability to use the whole page, all content on the Web page (whether it is used to meet other success criteria or not) must meet this success criterion. See Conformance Requirement 5: Non-Interference. | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - No portion of the screen flickers or flashes with a frequency between 2 Hz and 55 Hz
|
| 2.4.1 Bypass Blocks: A mechanism is available to bypass blocks of content that are repeated on multiple Web pages. (Level A) | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - “Skip link target” is provided to skip to main content directly. However, you will not find it in each and every page.
|
| 2.4.2 Page Titled: Web pages have titles that describe topic or purpose. (Level A) | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Pages have a meaningful title specified in the TITLE element
|
| 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) | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Logical movement through the focusable components using only the keyboard, in an order that follows a meaningful sequence
Exceptions: - In the simplified interface, tab order is not correctly defined. Action items for screens, e.g. save, cancel, finish, next etc., are on the top of the page and hence these are first in tab order, whereas the user would want to complete other operations on the page and then reach these action buttons. Bug ID: 19362240
- Tab order is not correct in form folder. Bug ID: 19863667
- Navigation through the left-hand pane to select form or task list requires the end user to press the down arrow until they reach the desired task. The end user is not able to navigate directly to the parent (folder) to find the task. Bug ID: 16402997
|
| 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) | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - The text of links and their surrounding paragraph, list, table cell (with marked up table headers), or preceding heading is sufficient to describe their purpose
|
| 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) | Product has been developed to conform to this standard subject to the remarks on the right. | This product was tested for: - Page contains controls that enable reaching all pages
|
| 2.4.6 Headings and Labels: Headings and labels describe topic or purpose. (Level AA) | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for : - Headers describe the topic or purpose of the content below them
- Labels describe the purpose of the associated field
Exceptions: - Header element is not defined in data forms, rule launch page, and Dashboards screens of simplified UI. Bug ID: 19911565
|
| 2.4.7 Focus Visible: Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible. (Level AA) | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Visual indication of the location of the focus
Exception: - On normal mode, focus is not highlighted on Administrator menu and info tile boxes of task on simplified UI. Bug ID: 20113992
|
| 3.1.1 Language of Page: The default human language of each Web page can be programmatically determined. (Level A) | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Screen readers can determine language of the pages based on browser locale.
|
| 3.1.2 Language of Parts: The human language of each passage or phrase in the content can be programmatically determined except 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) | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Screen readers can determine language of the page contents based on browser locale.
|
| 3.2.1 On Focus: When any component receives focus, it does not initiate a change of context. (Level A) | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - When an element receives focus, it does not result in a substantial change to the page, an additional change of keyboard focus, or the spawning of a pop-up window
|
| 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) | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Changes in the value of user interface components does not result in a substantial change to the page, an additional change of keyboard focus, or the spawning of a pop-up window
|
| 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) | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Pages that are grouped together into sets with a common navigation mechanism utilize that navigation mechanism in the same fashion, with navigation elements appearing in the same relative order each time
|
| 3.2.4 Consistent Identification: Components that have the same functionality within a set of Web pages are identified consistently. (Level AA) | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Images and controls are used and identified consistently throughout the product
Exception: - Expand/Collapse icons are not consistently defined in left-hand and right-hand panes. Bug ID: 19785710
|
| 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) | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - When input errors are detected, they are described to the user in text, including identifying the item where the error occurred
Exceptions: - In non-screen reader mode, focus does not move to confirmation or error message dialogs. Bug ID: 19467568
- In Screen reader mode, confirmation and Error messages are not displayed. Bug ID: 20094508
- Error message is displayed upon saving the form, which is incorrect as users should be prompted with the error upon entering wrong value. Bug ID: 19780130
|
| 3.3.2 Labels or Instructions: Labels or instructions are provided when content requires user input. (Level A) | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Labels or instructions are provided when the product requires user input
Exceptions: - Label is missing for a few Web elements in simplified UI screen and Dashboard create screen. Labels are missing in Forms Access control Reports screen. Bug ID: 20271359
- The following screens have missing labels, incorrect row/column headers, and screen reader issues: Copy Versions, Data form editor - Business rule and other options page. Bug ID: 19780545 & 19686332
- In the data forms, page selection fields do not name the dimension to which it belongs. Bug ID: 20094474
- Missing labels for: Business Rules Run-time Prompt (RTP) window - Prompt text. Bug ID: 13871180
|
| 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) | Does not Support | The product needs improvement in Error suggestions to meet this requirement and currently does not support this requirement. Bug ID: 19780130 |
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)
- Reversible: Submissions are reversible.
- Checked: Data entered by the user is checked for input errors and the user is provided an opportunity to correct them.
- Confirmed: A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission.
| Product has been developed to conform to this standard subject to the remarks on the right. | The product is not meant to be used for Legal or Financial user commitments. |
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)
Note: Start and end tags that are missing a critical character in their formation, such as a closing angle bracket or a mismatched attribute value quotation mark are not complete. | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Elements in HTML content have complete start and end tags, are properly nested, do not contain duplicate attributes, and have unique IDs
- Pages validate to the HTML specification
|
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)
Note: This success criterion is primarily for Web authors who develop or script their own user interface components. For example, standard HTML controls already meet this success criterion when used according to specification. | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - HTML controls have a programmatically associated name, derived from the appropriate HTML elements and attributes including LABEL, TITLE, SUMMARY, CAPTION, etc.
- Additional state information is programmatically exposed for HTML controls, such as whether a field is ‘required’.
- Frames have a meaningful title specified in the title attribute
Exceptions: - Expand/Collapse icons on data forms in screen reader mode are not correctly defined. As a result screen readers don’t read it correctly, e.g. when expanding a column in a data form, it would not read the dimension member name being expanded. Bug ID: 19245678
- In the simplified interface of Planning mode, toolbar buttons are read as "radio button links" by screen reader. Bug ID: 19150252
- The Instructions feature on Planning web pages, e.g. Instructions for a Task list etc., are shown with HTML tags making it difficult to be read by screen reader. Bug ID: 17037429
|