EN 301 549 Report
Notes:
(Based on VPAT® Version 2.4)
This report covers the degree of conformance for the following accessibility standard/guidelines:
The terms used in the Conformance Level information are defined as follows:
Tables 1 and 2 also document conformance with:
Note: When reporting on conformance with the WCAG 2.1 Success Criteria, the criteria are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.1 Conformance Requirements.
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.
1.1.1 Non-text Content (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
Web: The product provides sufficient text alternatives for most instances of non-text content, such as images and icons. Exceptions include:
Some decorative icons, such as chevrons in the Breadcrumb and Accordion components, are not identified as decorative and have textual alternatives that are not descriptive.
A linked logo image in the PDF viewer lacks a textual alternative.
Product images in the Related Products and Product Carousel components lack alt attributes.
Product images in the Product Teaser component have URLs for text alternatives, instead of text that describes the image or link destination.
Provide alternatives for time-based media.
1.2.1 Audio-only and Video-only (Prerecorded) (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
1.2.2 Captions (Prerecorded) (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
1.2.4 Captions (Live) (Level AA)
Also applies to:
EN 301 549 Criteria
Revised Section 508
1.2.5 Audio Description (Prerecorded) (Level AA)
Also applies to:
EN 301 549 Criteria
Revised Section 508
Create content that can be presented in different ways (for example simpler layout) without losing information or structure.
1.3.1 Info and Relationships (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
Web: Most visual structure and relationship information, such as lists, headings, and landmarks, is provided through element semantics. Exceptions include:
The Language Navigation component does not have a label to distinguish it from other navigation landmarks.
Tables generated using the Text component lack programmatic row or column headers.
Visible heading text for PDFs in the PDF Viewer component is hidden from assistive technology.
Some changes in content, such as updates to the user's location in the search results in the PDF Viewer component, are not announced to screen reader users.
Heading levels for nested accordions in the Accordion component do not reflect the hierarchical structure of the content.
A modal dialog in the Commerce Navigation component lacks appropriate dialog structure.
Form field constraints and error messages are not associated with their fields programmatically in the Reset Password component.
1.3.2 Meaningful Sequence (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
1.3.3 Sensory Characteristics (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
1.3.4 Orientation (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria
Revised Section 508 – Does not apply
1.3.5 Identify Input Purpose (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria
Revised Section 508 – Does not apply
Make it easier for users to see and hear content including separating foreground from background.
1.4.1 Use of Color (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
Web: Most functions of the product do not convey information through color alone. Exception:
Links in List and PDF Viewer components are distinguished from surrounding text by color alone.
1.4.2 Audio Control (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
1.4.3 Contrast (Minimum) (Level AA)
Also applies to:
EN 301 549 Criteria
Revised Section 508
Web: Most text meets minimum contrast requirements. Exceptions include:
Text overlaid on background images, such as in the Product Teaser and Container components, lacks adequate color contrast depending on the colors in the background image.
Text identifying image file information in the Download component does not provide adequate contrast against its background.
1.4.4 Resize text (Level AA)
Also applies to:
EN 301 549 Criteria
Revised Section 508
1.4.5 Images of Text (Level AA)
Also applies to:
EN 301 549 Criteria
Revised Section 508
1.4.10 Reflow (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria
Revised Section 508 – Does not apply
Web: At the required width of 320 CSS pixels, most content is presented without loss of information or functionality, and without requiring scrolling in two dimensions. Exceptions include:
In the PDF Viewer component, controls are cut off and content requires scrolling in two dimensions.
Embedded videos do not resize proportionally.
1.4.11 Non-text Contrast (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria
Revised Section 508 – Does not apply
Web: Most meaningful non-text content elements have sufficient contrast. Exceptions include:
Completed and remaining portions of the bar in the Progress Bar component do not provide adequate contrast against each other.
Previous and Next icon buttons in the Product Carousel component, and navigation dot icon buttons in the Carousel component, lack adequate contrast.
1.4.12 Text Spacing (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria
Revised Section 508 – Does not apply
1.4.13 Content on Hover or Focus (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria
Revised Section 508 – Does not apply
Make all functionality available from a keyboard.
2.1.1 Keyboard (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
Web: Most product functionality can be operated through a keyboard interface. Exceptions include:
In the PDF Viewer component, focus is not managed correctly for some interactions and several controls either cannot receive focus or cannot be activated with keyboard alone.
In the Commerce Navigation component, focus is not managed correctly when the menu is opened and closed.
Actions menus in the Mini Cart component cannot be dismissed with keyboard alone without selecting from the menu.
In the Embed component, the Pinterest embed cannot be operated with a keyboard.
2.1.2 No Keyboard Trap (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
2.1.4 Character Key Shortcuts (Level A 2.1 only)
Also applies to:
EN 301 549 Criteria
Revised Section 508 – Does not apply
Provide users enough time to read and use content.
2.2.1 Timing Adjustable (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
2.2.2 Pause, Stop, Hide (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
Do not design content in a way that is known to cause seizures.
2.3.1 Three Flashes or Below Threshold (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
Provide ways to help users navigate, find content, and determine where they are.
2.4.1 Bypass Blocks (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
2.4.2 Page Titled (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
2.4.3 Focus Order (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
Web: Most components receive focus in a meaningful order. Exceptions include:
In the PDF Viewer component, an “Enable accessibility for screen readers” control receives focus although it is visually hidden and is placed in the focus order following the content that it would control, rather than preceding it.
In the Mini Cart component, some controls receive focus when they are visually hidden or obscured.
2.4.4 Link Purpose (In Context) (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
Web: The purpose of most links in the product can be determined from the link text alone or from the programmatic context of the link. Exceptions include:
In the Social Sharing component, the Pinterest link does not identify its purpose.
In the Quick Search component, some linked images have no textual alternative.
2.4.5 Multiple Ways (Level AA)
Also applies to:
EN 301 549 Criteria
Revised Section 508
2.4.6 Headings and Labels (Level AA)
Also applies to:
EN 301 549 Criteria
Revised Section 508
Web: Most headings and labels are descriptive. Exception:
In the Cart Trigger component, information about the number of items in the cart is visually part of the button, but it is not included in the accessible name or available to assistive technology.
2.4.7 Focus Visible (Level AA)
Also applies to:
EN 301 549 Criteria
Revised Section 508
Web: Most focusable elements have a visible keyboard focus indicator. Exceptions include:
Linked images in the Teaser component.
Some icon buttons in the PDF Viewer, Product Carousel, and Mini Cart components.
Accordion buttons in the Accordion component.
Make it easier for users to operate functionality through various inputs beyond keyboard.
2.5.1 Pointer Gestures (Level A 2.1 only)
Also applies to:
EN 301 549 Criteria
Revised Section 508 – Does not apply
2.5.2 Pointer Cancellation (Level A 2.1 only)
Also applies to:
EN 301 549 Criteria
Revised Section 508 – Does not apply
2.5.3 Label in Name (Level A 2.1 only)
Also applies to:
EN 301 549 Criteria
Revised Section 508 – Does not apply
Web: In most product functions, accessible names of controls contain the text of their visible labels. Exception:
In the Reset Password component, accessible names for fields do not match the visible label text.
2.5.4 Motion Actuation (Level A 2.1 only)
Also applies to:
EN 301 549 Criteria
Revised Section 508 – Does not apply
Make text content readable and understandable.
3.1.1 Language of Page (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
3.1.2 Language of Parts (Level AA)
Also applies to:
EN 301 549 Criteria
Revised Section 508
Make Web pages appear and operate in predictable ways.
3.2.1 On Focus (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
3.2.2 On Input (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
3.2.3 Consistent Navigation (Level AA)
Also applies to:
EN 301 549 Criteria
Revised Section 508
3.2.4 Consistent Identification (Level AA)
Also applies to:
EN 301 549 Criteria
Revised Section 508
Help users avoid and correct mistakes.
3.3.1 Error Identification (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
3.3.2 Labels or Instructions (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
Web: Labels are provided for most input fields. Exception:
The coupon code input in the Checkout component is labelled only with placeholder text.
3.3.3 Error Suggestion (Level AA)
Also applies to:
EN 301 549 Criteria
Revised Section 508
3.3.4 Error Prevention (Legal, Financial, Data) (Level AA)
Also applies to:
EN 301 549 Criteria
Revised Section 508
Maximize compatibility with current and future user agents, including assistive technologies.
4.1.1 Parsing (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
Web: In most product functions, 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. Exception:
The Product Carousel component includes duplicate IDs.
4.1.2 Name, Role, Value (Level A)
Also applies to:
EN 301 549 Criteria
Revised Section 508
Web: Most user interface components in the product provide accessible names, appropriate roles, and expose their state and/or value to assistive technology. Exceptions include:
Some icon buttons in the Product Carousel, PDF Viewer, Commerce Navigation, and Mini Cart components lack accessible names.
The Quantity input in the Mini Cart lacks an accessible name.
Progress bars in the Progress Bar component lack accessible names.
Invalid roles are used in the Product Carousel and Related Products components.
4.1.3 Status Messages (Level AA 2.1 only)
Also applies to:
EN 301 549 Criteria
Revised Section 508 – Does not apply
Web: Most product functions do not require status messages. In some cases, when status messages are present but do not receive focus, the update is not provided to assistive technology. Example:
In the Quick Search and Reset Password components, screen reader users are not alerted to status updates.
Notes:
Notes: This table documents instances of equivalent facilitation or instances of functions not addressed by technical requirements. Responses which cite technical requirements are informative only.
Web: Most functions of the product are usable without vision. Exceptions include:
As noted in 1.1.1 Non-text Content, some meaningful images lack textual alternatives, and some decorative images are not appropriately hidden from assistive technology.
As noted in 1.3.1 Info and Relationships, some tables are not structured correctly, some heading information is not appropriately conveyed to assistive technology, a dialog lacks appropriate structure, a navigation landmark is not labeled to distinguish it from other navigation landmarks, and some error and constraint text is not associated with the relevant input.
As noted in 2.1.1 Keyboard, focus is not managed correctly in some interface components, menus in one component cannot be dismissed with keyboard alone, and a Pinterest embed is not keyboard accessible.
As noted in 2.4.1 Bypass Blocks, a mechanism is not provided to bypass repeated blocks of content for users without assistive technology.
As noted in 2.4.3 Focus Order, focus order is not logical for a control in the PDF Viewer component, and some controls in the Mini Cart receive focus when they are visually hidden.
As noted in 2.4.4 Link Purpose (In Context), some links do not convey their purpose.
As noted in 3.3.2 Labels and Instructions, an input in the Checkout component lacks a persistent visible label.
As noted in 4.1.1 Parsing, the Product Carousel component includes duplicate IDs.
As noted in 4.1.2 Name, Role, Value, some controls lack accessible names, and an invalid role is used in some components.
Web: Most functions of the product are usable with limited vision.
As noted in 1.4.3 Contrast (Minimum), text overlaid on background images may not provide adequate contrast, and some text in the Download component lacks adequate contrast.
Web: Most functions of the product are usable without perception of color. Exception:
As noted in 1.4.1 Use of Color, some links are distinguished from surrounding text using color alone.
Web: Most functions of the product are usable without vision. Exceptions include:
As noted in 1.1.1 Non-text Content, some meaningful images lack textual alternatives, and some decorative images are not appropriately hidden from assistive technology.
As noted in 1.3.1 Info and Relationships, some tables are not structured correctly, some heading information is not appropriately conveyed to assistive technology, a dialog lacks appropriate structure, a navigation landmark is not labeled to distinguish it from other navigation landmarks, and some error and constraint text is not associated with the relevant input.
As noted in 2.1.1 Keyboard, focus is not managed correctly in some interface components, menus in one component cannot be dismissed with keyboard alone, and a Pinterest embed is not keyboard accessible.
As noted in 2.4.1 Bypass Blocks, a mechanism is not provided to bypass repeated blocks of content for users without assistive technology.
As noted in 2.4.3 Focus Order, focus order is not logical for a control in the PDF Viewer component, and some controls in the Mini Cart receive focus when they are visually hidden.
As noted in 2.4.4 Link Purpose (In Context), some links do not convey their purpose.
As noted in 3.3.2 Labels and Instructions, an input in the Checkout component lacks a persistent visible label.
As noted in 4.1.1 Parsing, the Product Carousel component includes duplicate IDs.
As noted in 4.1.2 Name, Role, Value, some controls lack accessible names, and an invalid role is used in some components.
Web: Most functions of the product are usable with limited language, cognitive, and learning abilities. Users with cognitive disabilities have varying needs for features that allow them to adapt content and work with assistive technology or accessibility features of the platform. The product provides descriptive labels, instructions, and error identification and suggestions for most user input. Exceptions include:
As noted in 3.3.2 Labels and Instructions, an input in the Checkout component lacks a persistent visible label.
Notes: Not Applicable
Notes: Not Applicable
Notes: Information regarding Support Documentation and Services is available in the Accessibility Conformance Report for the Adobe Help Center on the Adobe Accessibility Compliance website.
Notes:
Notes: According to C.4 Functional Performance, this section is informative only.
Web: Most functions of the product are usable without vision. Exceptions include:
As noted in 1.1.1 Non-text Content, some meaningful images lack textual alternatives, and some decorative images are not appropriately hidden from assistive technology.
As noted in 1.3.1 Info and Relationships, some tables are not structured correctly, some heading information is not appropriately conveyed to assistive technology, a dialog lacks appropriate structure, a navigation landmark is not labeled to distinguish it from other navigation landmarks, and some error and constraint text is not associated with the relevant input.
As noted in 2.1.1 Keyboard, focus is not managed correctly in some interface components, menus in one component cannot be dismissed with keyboard alone, and a Pinterest embed is not keyboard accessible.
As noted in 2.4.1 Bypass Blocks, a mechanism is not provided to bypass repeated blocks of content for users without assistive technology.
As noted in 2.4.3 Focus Order, focus order is not logical for a control in the PDF Viewer component, and some controls in the Mini Cart receive focus when they are visually hidden.
As noted in 2.4.4 Link Purpose (In Context), some links do not convey their purpose.
As noted in 3.3.2 Labels and Instructions, an input in the Checkout component lacks a persistent visible label.
As noted in 4.1.1 Parsing, the Product Carousel component includes duplicate IDs.
As noted in 4.1.2 Name, Role, Value, some controls lack accessible names, and an invalid role is used in some components.
As noted in 4.1.3 Status Messages, some status messages are not conveyed to assistive technology.
As noted in 7.2.1 Audio description playback and 7.3 User controls for captions and audio description, embedded YouTube videos do not provide a mechanism to play closed audio descriptions.
Web: Most functions of the product are usable with limited vision.
As noted in 1.4.3 Contrast (Minimum), text overlaid on background images may not provide adequate contrast, and some text in the Download component lacks adequate contrast.
As noted in 1.4.10 Reflow, content in the PDF Viewer component and embedded video in the Embed component do not reflow without content loss.
As noted in 1.4.11 Non-text Contrast, progress bars and navigation icon buttons in some components lack adequate contrast.
Web: Most functions of the product are usable without perception of color. Exception:
As noted in 1.4.1 Use of Color, some links are distinguished from surrounding text using color alone., some links are distinguished from surrounding text using color alone.
Web: Most functionality in the product is usable with limited manipulation and strength. Exceptions include:
As noted in 2.1.1 Keyboard, focus is not managed correctly in some interface components, menus in one component cannot be dismissed with keyboard alone, and a Pinterest embed is not keyboard accessible.
As noted in 2.4.1 Bypass Blocks, a mechanism is not provided to bypass repeated blocks of content for users without assistive technology.
As noted in 2.4.3 Focus Order, focus order is not logical for a control in the PDF Viewer component, and some controls in the Mini Cart receive focus when they are visually hidden.
As noted in 2.4.7 Focus Visible, some focusable elements lack a visible focus indicator.
As noted in 2.5.3 Label in Name, accessible names for inputs in the Reset Password component do not match the visible label text.
Web: Users with limited reach will have no difficulty navigating to controls. Exceptions include:
As noted in 2.1.1 Keyboard, image buttons, menu, tooltips are not keyboard accessible, modal does not have a method to dismiss it using keyboard alone.
As noted in 1.4.13 Content on Hover or Focus, the additional content disappears when the user moves the mouse pointer to the content and also it is not dismissible via keyboard without moving mouse hover or keyboard focus.
Web: Most functions of the product are usable with limited language, cognitive, and learning abilities. Users with cognitive disabilities have varying needs for features that allow them to adapt content and work with assistive technology or accessibility features of the platform. The product provides descriptive labels, instructions, and error identification and suggestions for most user input. Exception:
As noted in 3.3.2 Labels and Instructions, an input in the Checkout component lacks a persistent visible label.
Web: The product maintains user privacy when accessibility features are used. Example:
The product gives screen reader users sufficient opportunity to use their own private listening devices when reading personal data.
Notes:
The product has only non-mechanical operable parts, such as on-screen buttons. Most operable parts have an accessible name which enables them to be discernible without user vision. Exception:
Some graphical on-screen buttons do not have an accessible name.
Notes: Not Applicable
Notes: Not Applicable
Notes: Not Applicable
Notes: See WCAG 2.x section
Notes: Not Applicable
Notes: Not Applicable
Notes: Information regarding Support Documentation and Services is available in the Accessibility Conformance Report for the Adobe Help Center on the Adobe Accessibility Compliance website.
Notes: Not Applicable
Voluntary Product Accessibility Template® and VPAT® are a registered trademark of Information Technology Industry Council (ITI)