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 on the ALT attribute
- Images that are decorative have an empty ALT attribute
- Non-text characters are not used or have meaningful alternative text
- Row and column headers for data tables are identified and their meaning is clear
- Data tables have a meaningful summary attribute or caption element
- Each page/pop up/modal, applet has a meaningful and unique title
- Form elements have a meaningful labels
- Information shown in complex images such as charts is also available in an alternative textual form
- CAPTCHAS are not used
- The product does not contain time-based media
|
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 present audio or video. |
| 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 does not present audio or video. |
| 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 does not present audio or 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 does not present audio or video. |
| 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 does not present audio or 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: - Form elements have a meaningful labels
- Data tables have a meaningful summary attribute or caption element
- Each new section of content has a meaningful header (text only no links) and their structure and hierarchy is meaningful and groups of components are marked up with their description
- Style sheets are used only to change the layout and presentation on the screen
Exceptions - The calendar picker on the date picker on the 'Schedule Publishing' page is not marked up appropriately as a table, but the date can be entered as text (20403171)
- A row header is missing in Shipping Method modal (21162712)
- A label is missing for the product picker field in the Manage Products modal in Related Products (21854418)
- A label is missing for SKU checkboxes when the user adds SKUs to a product (21860973)
- The Assisted Selling Application Settings page has some missing and empty labels. (21840167)
- The editor for adding Price Groups to Promotions has duplicate labels. (22968796)
- The Date and Time fields on the Schedule Publish page are missing table markup elements. (21056009)
|
| 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 DOM matches a logical reading sequence
Exceptions: - In the Site Settings area, the header "Site Settings" should be read prior to the titles of the General, Location, and Price Groups tabs; these items are not read in logical sequence. (22346091)
|
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
- Instructions provided which refer to graphics include a reference to the text alternative of the graphic
|
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 i.e. no information is conveyed by color alone
|
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 does not present audio or video. |
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: - Text and images of text have a contrast ratio of at least 4.5:1
- Large-scale text and images of large-scale text have a contrast ratio of at least 3:1
Exceptions: - Date picker controls, including on the 'Schedule Publishing' page and the 'New Product' modal, do not comply with the color contrast requirements. (20403171)
- In the Manage Products tab of the Related Products modal, the Sale banner on the product image does not comply with the color contrast requirements. (21854255)
- In the Media Library modal, Search for media text does not comply with the color contrast requirements. (21856186)
- The Login text placeholder does not comply with the color contrast requirements. (21866628)
- In Design Studio, disabled fields do not comply with the color contrast requirements. (21897673)
- In the Catalog area, placeholder text for fields in the Create New Product modal do not comply with the color contrast requirements. (21860985)
|
| 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: - When some Design Studio screens are resized to 200%, field frames obscure part of the text. (21897670)
|
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. | 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: - Fields and controls are accessible via the keyboard (by tabbing, enter, arrows or by documented shortcuts/access keys)
- Mouse-overs are not used unless they don't provide information essential for usage and comprehension of the application (image zoom hover over would be ok for example) or the information is provided some other way for assistive technologies to access.
- Proper operation of unique keystrokes and access keys, including those listed in the product documentation
- The ability to use the product with OS keyboard aids: FilterKeys (feature names may be different on different platforms)
Exceptions: - In the Collections section, there is no keyboard alternative to the drag and drop approach for the re-sequencing of sibling collections or the reassignment of the a collection to another parent (21217910)
- On the Media Tab within a Product, pressing the ESC key to close the 'Add Images' drop down list instead closes the product modal (21056082)
- A keyboard user cannot collapse an expanded collection tree in the Catalog. (21377721)
- In the Shipping Charges section of the Shipping Methods area, if the user enters invalid data, tabbing to the error message does not expand it, so it cannot be read using the keyboard only. (22346102)
- In the Reports area, in some cases, focus does not move properly through graphical data (22669410)
- In Design Studio, in some cases, tabbing to a new widget element and pressing Enter does not open a modal as expected. (22748658)
- In Design Studio, in the Product Details widget, the user cannot navigate to the About tab or the Name element when using Safari on a Mac. (23018704)
|
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: - Time limits in the product can be extended with at least 20 seconds warning up to 10 times
Exceptions: - The business user tools UI does not provide a warning prompt before session timeout, nor allow the end user to extend the session. (21860981)
- The business user tools UI includes growl messages that disappear after a short time, but does not provide a way to configure growl dismissal time as a user preference. (22353273)
|
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. | The product was tested for: - The product does not contain moving or blinking information
|
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: - A ‘Skip to Main Content’ link is provided to skip repetitive navigation links at the top of the page.
- Structure and hierarchy is marked up with header elements outside of repetitive navigation link
|
| 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 some situations, the focus order is incorrect - this was observed when modals are closed or the user tabs beyond the last element in a page (20396171, 20397740, 20396250, 20397539, 20397546, 21056049)
- Focus is going out of 'Additional Store Languages' control after removing a language through keyboard (21162718)
- In the Media library, when the user is tabbing through the list, focus goes back to top of list instead of continuing linearly. (21860982)
- On the Media tab, when the user removes an image and then responds to the confirmation dialog, focus returns to the first image on the page instead of the next image. (21860990, 22644991)
- When the user tabs through the promotions in the Marketing tab for a second time, the tab order is incorrect and not every promotion is reached. (21854072)
- In the Locations tab of the Site Settings page, after the user selects a language, focus moves to start of the page instead of staying on the language selector. (21854072)
- In some situations, focus is shifted behind a modal (21377694, 21860971, 22721611)
- Under some conditions, focus moves to the Dashboard page instead of staying in the Location tab of the Site Settings page. (21162718)
- In Design Studio, in grid view for the product details layout, backwards tabbing does not behave as expected. (21897682)
- On the Reports page, State/Region fields are skipped in the tab order; the keyboard user must tab backwards to access them. (22353265)
- In the "All Products" view in the Catalog area, focus does not behave correctly when the screen refreshes after the user removes a product. (22676401)
- In the Catalog area, focus does not return to the "Manage Catalog" button after the Product Type modal closes. (20396238)
|
| 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 purpose of each link can be determined by its text
|
| 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. | The product was tested for: - Pages are fully inter-linked to each other
- 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: - Form elements have a meaningful label either as a displayed label or using title
- Row and column headers are identified for data tables and their meaning is clear
|
| 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
Exceptions - In Gridview when focus is moved away from a selected widget, the state of that widget is not changed (21056108)
- In the 'Media' section, focus is not clearly visible on the Grid/ List view buttons and the Sort By dropdown (21056108)
- Focus location is not clear when, in the Catalog, the user selects a media image and tabs to the image's thumbnails. (21860577)
- In the Related Products tab, the carousel arrows are not highlighted when the user tabs to them. (21860576)
- In Firefox, when arranging the products in a collection, there is no visual indication when focus in on an up-arrow. (21866631)
|
| 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: - Properly set lang attribute for each page
|
| 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: - Proper use of lang attribute for text passages that are in a different language than that of the page
|
| 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, or 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
- In circumstances where changing the value of the components causes a substantial change to the page, an additional change of keyboard focus, or the spawning of a pop-up window, warning is given prior to the user interacting with those user-interface components
|
| 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: - Navigation mechanisms that are used in multiple pages are consistent
|
| 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
|
| 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: - When the user skips a required field when scheduling publishing, the error described is not specific enough to help a non-sighted user. (21377700)
- In the Payment Processing area of Settings, there is inconsistent error message behavior when required fields are skipped. In some cases, the system generates an error message with links to the fields with missing values; this should be true in all cases. (22632893)
- In the Web APIs area of Settings, invalid input does not generate a sufficiently specific message with a link to the field with the error. (22484054)
|
| 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: - Form elements have a meaningful labels (input, select, textarea), either as a displayed label or using title
Exceptions: Labels or Instructions are not present or misleading in a number of circumstances, including: - For the 'Shipping Charges'input field within the Shipping Method modal (20403162)
- For the 'Browse' button on the Upload Media modal and the 'Add Image' button on the Media tab (20397503)
- For the Collapse Collection Tree button on the Catalog page (20396106)
- For the Option Values within the Add SKUs modal (20397544)
- For each value label on Variant Property Settings modal (20403165)
|
| 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) | Product has been developed to conform to this standard subject to the remarks on the right. | The product was tested for: - Where suggestions for fixing an input error are known, they are provided to the user
|
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 was tested for: - Submissions can be reversed by the user
- Data is checked for input errors with an opportunity for the user to correct them
- Data can be reviewed, corrected, and confirmed by the user before they are finalized
|
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: - Pages validate to the HTML specification
Exceptions - Duplicate IDs are present in the following UI areas: Order Reporting, Catalog, Theme View, Product Type, Payment Gateways, Promotions, Media Library, Assisted Selling Application Settings, Site Settings (21856020, 21854170, 21866629, 21856175, 21866626, 21854437, 21860912, 21856174, 21840167, 22346104, 22652125)
|
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’.
- Custom controls have appropriate roles specified using the role attribute
- Custom controls have appropriate state and property information conveyed using the relevant WAI-ARIA or HTML5 attributes
- Custom controls have a meaningful programatically exposed name
- Frames have a meaningful title specified in the title attribute
Exceptions - An issue exists within the List picker tool where selected values are not read out by the screen reader (20402368)
- In the Inventory and Stock Thresholds areas of Catalog configuration, if the user enters invalid values, a screen reader does not read the error message because the role "alert" is missing. (21866625)
- In the Catalog area, when the user searches, the results are not announced by the screen reader because the role "alert" is missing. (21851839)
- In the Web APIs area of Settings, when the user edits an existing application and tabs to the Application Key field, the screen reader does not read the field. (21377752)
- In the Coupon creation area, some inline error messages are read of out context. (22346089)
- In the Coupon creation area, some inline error messages are not read (22346094)
- In the Add SKU modal, the error that appears when invalid data are entered is missing an ARIA label, and thus is not read by the screen reader. (22346097)
- In the Shipping Charges section of the Shipping Methods area, if the user enters invalid data, the error message is missing an ARIA label, and thus is not read by the screen reader. (22346102)
- In the Catalog area, when the user tabs to the Long Description field of a Collection, the screen reader reads "Edit Text" but does not read the existing field contents. (22346228)
- When the user skips a required field when creating a promotion, the error that appears visually is not read by the screen reader. (22346073, 23018843)
- In Design Studio, the Close button is not read by the screen reader when the user tabs onto it.(22748662)
- On the Access Control page, the screen reader does not read helper text on the New User modal (21377696)
|