Accessibility Conformance Report
Level Access AMP, Access Assistant, Access University, Access Analytics and Electronic Docs Accessibility Conformance Report
Revised Section 508 Edition
Name of Product/Version: AMP (Level Access’s Accessibility Management Platform), including Access Assistant, Access University, Access Analytics and its Electronic Docs.
Product Description: AMP is an accessibility management platform that provides the structure to facilitate and organize all aspects of successful digital accessibility initiatives. AMP’s powerful testing engine and workflow, intelligent reporting, accessible development best practices, and extensive training course library allow organizations to quickly and efficiently build, test, and maintain accessible software. Access Assistant, which comes with AMP, is a browser plug-in for Chrome, Firefox, and Internet Explorer that integrates with AMP to support dynamic testing directly in the browser, with the option to save results directly into AMP. Testing results can be exported to Excel and PDF documents (for the purposes of this ACR, only PDFs were tested).
Date: May 28, 2019
Contact information:
Notes: Testing was performed on Microsoft Windows 10 desktop PCs with the Firefox 61 browser.
Evaluation Methods Used: Testing AMP with Access Assistant, Access University, Access Analytics and its Electronic Docs involved a combination of manual and functional testing. Level Access (Level) comprehensively tested a selection of pages representative of AMP, Access Assistant, Access University, Access Analytics and its Electronic Docs using, among other methodology, the screen reader JAWS 2018, exclusive use of the keyboard, and manual inspection of code and Accessibility API output (through the use of tools, such as Microsoft Inspect).
Applicable Standards/Guidelines
This report covers the degree of conformance for the following accessibility standard/guidelines:
| Standard/Guideline | Included in Report |
|---|---|
| Web Content Accessibility Guidelines 2.0, at http://www.w3.org/TR/2008/REC-WCAG20-20081211/ | Level A (Yes) Level AA (Yes) Level AAA (No) |
| Revised Section 508 standards as published by the U.S. Access Board in the Federal Register on January 18, 2017 Corrections to the ICT Final Rule as published by the US Access Board in the Federal Register on January 22, 2018 |
(Yes) |
Terms
The terms used in the Conformance Level information are defined as follows:
- Supports: The functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation.
- Partially Supports: Some functionality of the product does not meet the criterion.
- Does Not Support: The majority of product functionality does not meet the criterion.
- Not Applicable: The criterion is not relevant to the product.
- Not Evaluated: The product has not been evaluated against the criterion. This can be used only in WCAG 2.0 Level AAA.
WCAG 2.0 Report
Tables 1 and 2 also document conformance with:
- Chapter 5 – 501.1 Scope, 504.2 Content Creation or Editing
- Chapter 6 – 602.3 Electronic Support Documentation
Note: When reporting on conformance with the WCAG 2.0 Success Criteria, they are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.0 Conformance Requirements.
Table 1: Success Criteria, Level A
Notes:
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.1.1 Non-text Content(Level A) Also applies to: Revised Section 508
|
AMP: Partially Supports
Access Assistant: Supports Electronic Docs: Partially Supports Access University: Partially Supports Access Analytics: Supports |
AMP: AMP provides appropriate text equivalents to most non-text content, with infrequent exceptions. A small number of controls are missing or have inappropriate accessible names. In two tree controls, certain elements are incorrectly conveyed as being expandable when they are not. Some controls have redundant content in their accessible names.
Access Assistant: Access Assistant provides textual equivalents for non-text content. Electronic Docs: Visually-hidden artifact logos are still announced by screen readers in the PDFs. Access University: Graded quiz results, i.e., checkmarks or X icons, do not have a text equivalent. Access Analytics: A text equivalent is included for all non-text content. |
| 1.2.1 Audio-only and Video-only (Prerecorded)(Level A)
Also applies to: Revised Section 508
|
AMP: Supports
Access Assistant: Supports Electronic Docs: Supports Access University: Supports Access Analytics: Supports |
AMP: Neither audio-only nor video-only content is present in AMP.
Access Assistant: Neither audio-only nor video-only content is present in Access Assistant. Electronic Docs: Neither audio-only nor video-only content is present in the PDFs. Access University: All pre-recorded video content includes the same content in text. Access Analytics: Neither audio-only nor video-only content is present in AMP. |
| 1.2.2 Captions (Prerecorded)(Level A)
Also applies to: Revised Section 508
|
AMP: Supports
Access Assistant: Supports Electronic Docs: Supports Access University: Supports Access Analytics: Supports |
AMP: No content requiring captions is present in AMP.
Access Assistant: No content requiring captions is present in Access Assistant. Electronic Docs: No content requiring captions is present in the PDFs. Access University: All prerecorded videos include captions. Access Analytics: No content requiring captions is present in Access Analytics. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded)(Level A)
Also applies to: Revised Section 508
|
AMP: Supports
Access Assistant: Supports Electronic Docs: Supports Access University: Supports Access Analytics: Supports |
AMP: No content requiring audio description, or a media alternative is present in AMP.
Access Assistant: No content requiring audio description, or a media alternative, is present in Access Assistant. Electronic Docs: No content requiring audio descriptions, or a media alternative is present in the PDFs. Access University: All prerecorded video has a text equivalent to the video content. Access Analytics: No content requiring audio description, or a media alternative is present in Access Analytics. |
| 1.3.1 Info and Relationships(Level A)
Also applies to: Revised Section 508
|
AMP: Partially Supports
Access Assistant: Partially Supports Electronic Docs: Partially Supports Access University: Partially Supports Access Analytics: Partially Supports |
AMP: In most respects, AMP correctly conveys information and relationships. In key data tables, column headers have been removed from the table structure due to the invalid reassignment of the table header elements to be sorting buttons, which prevents proper association between header and data cells. In a modest number of cases, form controls have missing, incorrect, or inappropriate names, such as some Dashboard customization fields and certain controls in Filter panels. In isolated cases, layout tables do not declare their presentational role, related sets of links are not grouped, or list markup is used inappropriately.
Access Assistant: Most information and relationships in Access Assistant are appropriately conveyed, with some exceptions. The Asset search field lacks a valid label. In the Module table for confirmed violations, the column headers and data cells are not properly associated, while in the Assets table, the column header for asset actions is empty. Electronic Docs: Two of the reference tables in the Use Case Results PDF do not have valid table headers. Access University: Within the quizzes and quiz results radio buttons and checkboxes are not contained within a <fieldset>. Access Analytics: In key data tables, column headers have been removed from the table structure due to the invalid reassignment of the table header elements to be sorting buttons, which prevents proper association between header and data cells. |
| 1.3.2 Meaningful Sequence(Level A)
Also applies to: Revised Section 508
|
AMP: Partially Supports
Access Assistant: Partially Supports Electronic Docs: Partially Supports Access University: Supports Access Analytics: Supports |
AMP: The sequence and reading order of content in AMP is appropriate in nearly all cases. Some AMP pages offer a Filter panel or a section with contextual links that are displayed on the right side of the page, but their location in the reading and tab order of the page comes after the main page heading element but before the primary content in the center. In these pages, assistive technology users can most quickly reach the main content in the center by either activating AMP’s skip link or navigating to the ‘main’ landmark. Also, in certain graphical Dashboard widgets, the visual order of content is different than the order conveyed by screen readers.
Access Assistant: In the Headings preview, all of the elements that are highlighted in the target webpage are appended to the end of the page, where they are separated from the context of the page contents for which they are headings. Electronic Docs: Visually-hidden artifact logos are still announced by screen readers in the PDFs. Access University: All content can be navigated and read in a meaningful sequence. Access Analytics: All content can be navigated and read in a meaningful sequence. |
| 1.3.3 Sensory Characteristics (Level A)
Also applies to: Revised Section 508
|
AMP: Supports
Access Assistant: Supports Electronic Docs: Supports Access University: Supports Access Analytics: Supports |
AMP: Instructions that rely on sensory characteristics are not present in AMP.
Access Assistant: Instructions that rely on sensory characteristics are not present in Access Assistant. Electronic Docs: Instructions that rely on sensory characteristics are not present in the PDFs. Access University: Instructions that rely on sensory characteristics are not present in Access Assistant. Access Analytics: Instructions that rely on sensory characteristics are not present in Access Analytics. |
| 1.4.1 Use of Color(Level A)
Also applies to: Revised Section 508
|
AMP: Partially Supports
Access Assistant: Partially Supports Electronic Docs: Supports Access University: Partially Supports Access Analytics: Supports |
AMP: AMP provides equivalents for the uses of color in most cases. Within a set of pagination links, the current page is indicated solely by color. Also, Best Practices in AMP have both a numerical rating of Severity and a corresponding color-based severity level that generally represents high, medium, or low severity, but where AMP defines each Best Practice, the severity level is conveyed solely by color with no textual equivalent.
Access Assistant: The error message from an unsuccessful AMP login uses color alone to render the error message without also indicating the error textually. Electronic Docs: Color is not the only means of distinguishing an element or indicating an action in the PDFs. Access University: Within pagination links, the current page is indicated solely by color. Button controls that are selected within the user profile picture settings are indicated solely by color. Access Analytics: Color is not the only means of distinguishing an element or indicating an action in Access Analytics. |
| 1.4.2 Audio Control(Level A)
Also applies to: Revised Section 508
|
AMP: Supports
Access Assistant: Supports Electronic Docs: Supports Access University: Supports Access Analytics: Supports |
AMP: No audio content that plays automatically is present in AMP.
Access Assistant: No audio content that plays automatically is present in Access Assistant. Electronic Docs: No audio content that plays automatically is present in thePDFs. Access University: No audio content that plays automatically is present in Access University. Access Analytics: No audio content that plays automatically is present in Access Analytics. |
| 2.1.1 Keyboard(Level A)
Also applies to: Revised Section 508
|
AMP: Partially Supports
Access Assistant: Supports Electronic Docs: Supports Access University: Supports Access Analytics: Supports |
AMP: In nearly every respect, the AMP user interface is fully accessible from the keyboard. In a modest number of components, inactive elements are included in the tab order, such as non-functional pagination links. In one ARIA-based page tab widget, the expected keyboard paradigm of using arrow keys to move from one tab to the next is supported, but in addition, each tab gets its own tab stop, which is inappropriate. Also, informational tooltips can only be activated by tabbing to the button; screen reader users cannot activate them after navigating to them with arrow keys. And for the infrequent use of links that occur within tooltips, the links cannot be activated from the keyboard.
Access Assistant: Access Assistant provides keyboard functionality for all content. Electronic Docs: The PDFs’ Table of Contents links are keyboard accessible. Access University: Access University provides keyboard functionality for all content. Access Analytics: Access Analytics provides keyboard functionality for all content. |
| 2.1.2 No Keyboard Trap(Level A)
Also applies to: Revised Section 508
|
AMP: Supports
Access Assistant: Supports Electronic Docs: Supports Access University: Supports Access Analytics: Supports |
AMP: No keyboard traps are observed in AMP.
Access Assistant: No keyboard traps are observed in AMP. Electronic Docs: No keyboard traps are observed in the PDFs. Access University: No keyboard traps are observed in Access University. Access Analytics: No keyboard traps are observed in Access Analytics. |
| 2.2.1 Timing Adjustable(Level A)
Also applies to: Revised Section 508
|
AMP: Partially Supports
Access Assistant: Partially Supports Electronic Docs: Supports Access University: Supports Access Analytics: Supports |
AMP: AMP automatically times out a user’s session after 12 hours of inactivity but does not offer an accessible mechanism to extend the session. The WCAG 2.0 success criteria requires a 20-hour session to pass without such a mechanism.
Access Assistant: Access Assistant integrates with AMP and has the same session management as described above for AMP. Electronic Docs: The PDFs do not have time limits. Access University: Access University integrates with AMP and has the same session management as described above for AMP. Access Analytics: Access Analytics integrates with AMP and has the same session management as described above for AMP. |
| 2.2.2 Pause, Stop, Hide (Level A)
Also applies to: Revised Section 508
|
AMP: Supports
Access Assistant: Does Not Support Electronic Docs: Supports Access University: Supports Access Analytics: Supports |
AMP: AMP provides the functionality to pause and hide any of its auto-updating content.
Access Assistant: Access Assistant does not provide the functionality to pause and hide any of its auto-updating content. Electronic Docs: There is no moving, blinking, scrolling or auto-updating content in the PDFs. Access University: There is no moving, blinking, scrolling or auto-updating content in Access University. Access Analytics:There is no moving, blinking, scrolling or auto-updating content in Access Analytics. |
| 2.3.1 Three Flashes or Below Threshold(Level A)
Also applies to: Revised Section 508
|
AMP: Supports
Access Assistant: Supports Electronic Docs: Supports Access University: Supports Access Analytics: Supports |
AMP: No flashing content is present in AMP.
Access Assistant: No flashing content is present in Access Assistant. Electronic Docs: No flashing content is present in the PDFs. Access University: No flashing content is present in Access University. Access Analytics: No flashing content is present in Access Analytics. |
| 2.4.1 Bypass Blocks(Level A)
Also applies to: Revised Section 508
|
AMP: Supports
Access Assistant: Does not Support Electronic Docs: Supports Access University: Supports Access Analytics: Supports |
AMP: AMP provides a mechanism for skipping repetitive content. The skip link works as expected in Firefox and Chrome, but may not work properly in Internet Explorer.
Access Assistant: Access Assistant does not provide a mechanism for skipping repetitive content. Electronic Docs: There are no repetitive blocks of content in the PDFs. Access University: Access University provides a mechanism for skipping repetitive content. Access Analytics: Access Analytics provides a mechanism for skipping repetitive content. |
| 2.4.2 Page Titled(Level A)
Also applies to: Revised Section 508
|
AMP: Supports
Access Assistant: Supports Electronic Docs: Supports Access University: Supports Access Analytics: Supports |
AMP: AMPhas meaningful page titles that describe their topic or purpose.
Access Assistant: Access Assistanthas meaningful page titles that describe their topic or purpose. Electronic Docs: The PDFs are all appropriately titled. Access University: Access University has meaningful page titles that describe their topic or purpose. Access Analytics: Access Analytics has meaningful page titles that describe their topic or purpose. |
| 2.4.3 Focus Order(Level A)
Also applies to: Revised Section 508
|
AMP: Partially Supports
Access Assistant: Partially Supports Electronic Docs: Supports Access University: Supports Access Analytics: Partially Supports |
AMP: In nearly all cases, the focus order when using AMP is correct, including the management of focus, such as to set focus to the start of a custom dialog when one appears or to an error message at the top of a form. In a small number of cases, the focus order or management of focus is not appropriate.
Access Assistant: The tab order of active elements in the header is somewhat illogical. And after a successful login, no element was focused or announced to indicate success. Electronic Docs: The focus order in the PDFs is logical. Access University: The focus order in the Access University is logical. Access Analytics: The table within the disclosure widget in Access Analytics receives focus even when it is not visible. |
| 2.4.4 Link Purpose (In Context)(Level A)
Also applies to: Revised Section 508
|
AMP: Partially Supports
Access Assistant: Supports Electronic Docs: Supports Access University: Supports Access Analytics: Supports |
AMP: Nearly all links in AMP identify their purpose, within context. Most links that trigger the display of custom dialogs indicate this special action, but a small number do not. Some links have redundant text in their accessible name or description. And some graphical links may not be reliably announced by their intended accessible names in certain situations.
Access Assistant: Access Assistantcomponents receive focus in an order that preserves meaning and operability. Electronic Docs: Links in the PDFs have meaningful text. Access University: Access University components receive focus in an order that preserves meaning and operability. Access Analytics: Access Analytics components receive focus in an order that preserves meaning and operability. |
| 3.1.1 Language of Page(Level A)
Also applies to: Revised Section 508
|
AMP: Supports
Access Assistant: Does Not Support Electronic Docs: Does Not Support Access University: Supports Access Analytics: Supports |
AMP: AMP’s default human language on each web page can be programmatically determined.
Access Assistant: The primary language of Access Assistant’s screens is not indicated in the opening HTML tag. Electronic Docs: The PDFs do not specify a valid language. Access University: The default human language on each web page in Access University can be programmatically determined. Access Analytics: The default human language on each web page in Access Analytics can be programmatically determined. |
| 3.2.1 On Focus(Level A)
Also applies to: Revised Section 508
|
AMP: Supports
Access Assistant: Supports Electronic Docs: Supports Access University: Supports Access Analytics: Supports |
AMP: No component in AMP activates or changes content when a user places focus on that component.
Access Assistant: No component in the Access Assistant activates or changes content when a user places focus on that component. Electronic Docs: No component in the PDFs activates or changes content when a user places focus on that component. Access University: No component in Access University activates or changes content when a user places focus on that component. Access Analytics: No component in Access Analytics activates or changes content when a user places focus on that component. |
| 3.2.2 On Input(Level A)
Also applies to: Revised Section 508
|
AMP: Supports
Access Assistant: Supports Electronic Docs: Supports Access University: Supports Access Analytics: Supports |
AMP: No component in AMP activates or changes context when the setting of a user interface component is changed, except where a user has been advised of that behavior.
Access Assistant: No component in Access Assistant activates or changes context when the setting of a user interface component is changed, except where a user has been advised of that behavior. Electronic Docs: No component in the PDFs activates or changes context when the setting of a user interface component is changed, except where a user has been advised of that behavior. Access University: No component in Access University activates or changes context when the setting of a user interface component is changed, except where a user has been advised of that behavior. Access Analytics: No component in Access Analytics activates or changes context when the setting of a user interface component is changed, except where a user has been advised of that behavior. |
| 3.3.1 Error Identification(Level A)
Also applies to: Revised Section 508
|
AMP: Supports
Access Assistant: Supports Electronic Docs: Supports Access University: Supports Access Analytics: Supports |
AMP: AMP identifies fields in error at the top of the form and offers links to navigate directly to the affected fields.
Access Assistant: Access Assistant identifies fields in error at the top of the form. Electronic Docs: The PDFs do not have error messages. Access University: Access University identifies fields in error at the top of the form and offers links to navigate directly to the affected fields. Access Analytics: Error messages are not used with Access Analytics. |
| 3.3.2 Labels or Instructions(Level A)
Also applies to: Revised Section 508
|
AMP: Partially Supports
Access Assistant: Partially Supports Electronic Docs: Supports Access University: Partially Supports Access Analytics: Supports |
AMP: AMP provides labels and instructions in nearly all applicable cases. Its forms display asterisks to indicate fields that are required, but while this is a common convention, its meaning is not stated explicitly.
Access Assistant: The Asset search field in Access Assistant lacks a valid label. Also, regarding keyboard use of the Node Capture feature, the instructions in the online support site are insufficient. Electronic Docs: No user input is required in the PDFs. Access University: Required fields within the Profile section of Access University are visually indicated with an asterisk but are not announced by a screen reader. Access Analytics: Fields in Access Analytics are labelled correctly. |
| 4.1.1 Parsing(Level A)
Also applies to: Revised Section 508
|
AMP: Partially Supports
Access Assistant: Supports Electronic Docs: Supports Access University: Partially Supports Access Analytics: Partially Supports |
AMP: Most markup in AMP is valid and well-formed. A small number of pages have elements whose ‘id’ references are not unique or are not valid, and in one tree control, list container elements have been repurposed with ARIA roles, but without nullifying the list item elements.
Access Assistant: Pages in Access Assistantdo not have parsing issues. Electronic Docs: The PDFs do not have parsing issues. Access University: Most markup in Access University is valid and well-formed. A small number of pages have elements whose ‘id’ references are not unique or are not valid. Access Analytics:Most markup in Access Analytics is valid and well-formed. A small number of pages have elements whose ‘id’ references are not unique or are not valid. |
| 4.1.2 Name, Role, Value(Level A)
Also applies to: Revised Section 508
|
AMP: Partially Supports
Access Assistant: Partially Supports Electronic Docs: Partially Supports Access University: Partially Supports Access Analytics:Partially Supports |
AMP: For the vast majority of elements, AMP provides appropriate names, and values. In key data tables, column headers have been removed from the table structure due to the invalid reassignment of the table header elements to be sorting buttons, which prevents proper association between header and data cells. In a modest number of cases, form controls have missing, incorrect, or inappropriate names, such as some Dashboard customization fields and certain controls in Filter panels. Key active elements related to the use of certain data tables resemble buttons but have no role. The button that hides or shows the Filter panel is inappropriately hidden from screen readers due to the inappropriate use of aria-hidden. In two tree controls, certain elements are incorrectly conveyed as being expandable when they are not, and the selection state may also be incorrect. Some controls have redundant content in their accessible names and descriptions. Some data tables update a counter as the user selects rows, while some combo boxes offer auto-suggestions, but this information is not dynamically rendered to users who are blind. AMP uses the ARIA role ‘alertdialog’ inappropriately to render certain system messages.
Access Assistant: The Asset search field in Access Assistant lacks a valid label. Electronic Docs: Visually-hidden artifact logos are still announced by screen readers in the PDFs. |
Table 2: Success Criteria, Level AA
Notes:
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.2.4 Captions (Live)(Level AA)
Also applies to: Revised Section 508
|
AMP: Supports
Access Assistant: Supports Electronic Docs: Supports Access University: Supports Access Analytics: Supports |
AMP: No content requiring live captions is present in AMP.
Access Assistant: No content requiring live captions is present in Access Assistant. Electronic Docs: No content requiring live captions is present in the PDFs. Access University: No content requiring live captions is present in Access University. Access Analytics: No content requiring live captions is present in Access Analytics. |
| 1.2.5 Audio Description (Prerecorded)(Level AA)
Also applies to: Revised Section 508
|
AMP: Supports
Access Assistant: Supports Electronic Docs: Supports Access University: Partially Supports Access Analytics: Supports |
AMP: No content requiring audio description is present in AMP.
Access Assistant: No content requiring audio description is present in Access Assistant. Electronic Docs: No content requiring audio description is present in the PDFs. Access University: No audio descriptions are available for prerecorded videos in Access University. The videos do include a full text version directly before or after the videos. Access Analytics: No content requiring audio description is present in the Access Analytics. |
| 1.4.3 Contrast (Minimum)(Level AA)
Also applies to: Revised Section 508
|
AMP: Supports
Access Assistant: Supports Electronic Docs: Supports Access University: Partially Supports Access Analytics: Supports |
AMP: AMP’s visual representation of text has a sufficient contrast ratio.
Access Assistant: Access Assistant’s visual representation of text has a sufficient contrast ratio. Electronic Docs: Contrast standards are met in the PDFs. Access University: There are instances within Access University that do not provide sufficient color contrast. These areas include, error messages within the Profile preferences page, headings within the My Report page and a minor insufficiency with links in odd numbered table rows. Access Analytics: Access Analytics’ visual representation of text has a sufficient contrast ratio. |
| 1.4.4 Resize text(Level AA)
Also applies to: Revised Section 508
|
AMP: Partially Supports
Access Assistant: Supports Electronic Docs: Partially Supports Access University: Supports Access Analytics: Supports |
AMP: AMP utilizes responsive design and generally adjusts the page layout in response to browser zoom. However, some components do not adjust properly, such as the dialog to choose which columns to display in a data grid and to offer to export to Excel. In such cases, the content may be cut off and unreachable without lowering the browser zoom level.
Access Assistant: Text can be resized without assistive technology up to 200% without the loss of content or functionality in Access Assistant. Electronic Docs: In the Use Case Results PDF, some portions of the document to not reflow properly and are not readable. Access University: Text can be resized without assistive technology up to 200% without the loss of content or functionality in Access Assistant. Access Analytics:Text can be resized without assistive technology up to 200% without the loss of content or functionality in Access Analytics. |
| 1.4.5 Images of Text(Level AA)
Also applies to: Revised Section 508
|
AMP: Supports
Access Assistant: Supports Electronic Docs: Supports Access University: Supports Access Analytics: Supports |
AMP: AMP uses text instead of images of text except where essential.
Access Assistant: Access Assistant uses text instead of images of text except where essential. Electronic Docs: The PDFs do not contain any text, only images of text. Access University: Access Universityuses text instead of images of text except where essential. Access Analytics: Access Analyticsuses text instead of images of text except where essential. |
| 2.4.5 Multiple Ways(Level AA)
Also applies to: Revised Section 508
|
AMP: Supports
Access Assistant: Supports Electronic Docs: Partially Supports Access University: Supports Access Analytics: Supports |
AMP: AMP has more than one way to locate a web page, except where the web page is a step in a process.
Access Assistant: Access Assistant has more than one way to locate a web page, except where the web page is a step in a process. Electronic Docs: The Best Practice Detail PDF does not provide bookmarks to highlight important sections and to facilitate navigation though this lengthy document. Access University: Access University has more than one way to locate a web page, except where the web page is a step in a process. Access Analytics: Access Analytics has more than one way to locate a web page, except where the web page is a step in a process. |
| 2.4.6 Headings and Labels(Level AA)
Also applies to: Revised Section 508
|
AMP: Supports
Access Assistant: Partially Supports Electronic Docs: Supports Access University: Supports Access Analytics: Supports |
AMP: Headings and labels accurately describe content in AMP.
Access Assistant: View, Edit, and Delete buttons do not specify their unique target in Access Assistant. Electronic Docs: The PDFs do not contain descriptive labels or headings. Access University: Headings and labels accurately describe content in Access University. Access Analytics: Headings and labels accurately describe content in Access Analytics. |
| 2.4.7 Focus Visible(Level AA)
Also applies to: Revised Section 508
|
AMP: Supports
Access Assistant: Supports Electronic Docs: Partially Supports Access University: Partially Supports Access Analytics: Supports |
AMP: AMP provides a visible indication of keyboard focus for actionable elements on the pages.
Access Assistant: Access Assistant provides a visible indication of keyboard focus for actionable elements on the pages. Electronic Docs: The Best Practice Detail PDF does not provide bookmarks to highlight important sections and to facilitate navigation though this lengthy document. Access University: The Columns Visible menu within the My Report in Access University does not have a visible focus indicator, the columns that it controls are all viewable by default. Access Analytics:Access Analytics provides a visible indication of keyboard focus for actionable elements on the pages. |
| 3.1.2 Language of Parts(Level AA)
Also applies to: Revised Section 508
|
AMP: Supports
Access Assistant: Supports Electronic Docs: Supports Access University: Supports Access Analytics: Supports |
AMP: AMP does not use inline languages in its pages.
Access Assistant: Access Assistant does not use inline languages in its pages. Electronic Docs: The PDFs do not use inline languages in its pages. Access University: Access University does not use inline languages in its pages. Access Analytics:Access Analytics does not use inline languages in its pages. |
| 3.2.3 Consistent Navigation(Level AA)
Also applies to: Revised Section 508
|
AMP: Supports
Access Assistant: Supports Electronic Docs: Supports Access University: Supports Access Analytics: Supports |
AMP: Navigation is consistent throughout the AMP.
Access Assistant: Navigation is consistent throughout Access Assistant. Electronic Docs: This criterion does not apply to non-web documents. Access University: Navigation is consistent throughout Access University. Access Analytics:Navigation is consistent throughout Access Analytics. |
| 3.2.4 Consistent Identification(Level AA)
Also applies to: Revised Section 508
|
AMP: Supports
Access Assistant: Supports Electronic Docs: Supports Access University: Supports Access Analytics:Supports |
AMP: AMP identifies components with the same functionality consistently across the website.
Access Assistant: Access Assistant identifies components with the same functionality consistently across the website. Electronic Docs: This criterion does not apply to non-web documents. Access University: Access University identifies components with the same functionality consistently across the website. Access Analytics:Access Analytics identifies components with the same functionality consistently across the website. |
| 3.3.3 Error Suggestion(Level AA)
Also applies to: Revised Section 508
|
AMP: Supports
Access Assistant: Supports Electronic Docs: Supports Access University: Supports Access Analytics:Supports |
AMP: Error messages in AMP provide suggestions for fixing the errors where appropriate.
Access Assistant: Error messages in Access Assistant provide suggestions for fixing the errors where appropriate. Electronic Docs: The PDFs do not have error messages. Access University: Error messages in Access University provide suggestions for fixing the errors where appropriate. Access Analytics:Error messages in Access Analytics provide suggestions for fixing the errors where appropriate. |
| 3.3.4 Error Prevention (Legal, Financial, Data)(Level AA)
Also applies to: Revised Section 508
|
AMP: Supports
Access Assistant: Supports Electronic Docs: Supports Access University: Supports Access Analytics:Supports |
AMP:AMP does not contain financial or legal transactions.
Access Assistant: Access Assistant does not contain financial or legal transactions. Electronic Docs: The PDFs do not contain financial or legal transactions. Access University: Access University does not contain financial or legal transactions. Access Analytics:Access Analytics does not contain financial or legal transactions. |
Revised Section 508 Report
Notes:
Chapter 3: Functional Performance Criteria (FPC)
Notes:
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 302.1Without Vision | AMP: Partially Supports
Access Assistant: Partially Supports Electronic Docs: Partially Supports Access University: Partially Supports Access Analytics:Partially Supports |
AMP: All core functionality and most secondary functionality is usable by people without vision with the following exceptions:
Access Assistant: All core functionality and most secondary functionality is usable by people without vision with the following exceptions:
Electronic Docs: All core functionality and most secondary functionality is usable by people without vision with the following exceptions:
Access University: All core functionality and most secondary functionality is usable by people without vision with the following exceptions:
|
| 302.2 With Limited Vision | AMP: Partially Supports
Access Assistant: Partially Supports Electronic Docs: Partially Supports Access University: Partially Supports Access Analytics:Partially Supports |
AMP: All core functionality and most secondary functionality is usable by people with limited vision with the following exceptions:
Access Assistant: All core functionality and most secondary functionality is usable by people with limited vision with the following exceptions:
Electronic Docs: All core functionality and most secondary functionality is usable by people with limited vision with the following exceptions:
Access University: All core functionality and most secondary functionality is usable by people with limited vision with the following exceptions:
|
| 302.3Without Perception of Color | AMP: Partially Supports
Access Assistant: Partially Supports Electronic Docs: Supports Access University: Partially Supports Access Analytics:Supports |
AMP: All core functionality and most secondary functionality is usable by people without the perception of color with the following exceptions:
Access Assistant: All core functionality and most secondary functionality is usable by people without the perception of color with the following exceptions:
Electronic Docs: All core functionality and most secondary functionality is usable by people without the perception of color. Access University: All core functionality and most secondary functionality is usable by people without the perception of color with the following exceptions:
Access Analytics:All core functionality and most secondary functionality is usable by people without the perception of color. |
| 302.4Without Hearing | AMP: Supports
Access Assistant: Supports Electronic Docs: Supports Access University: Supports Access Analytics:Supports |
AMP: Does not include any content or control which relies on the user’s ability to hear.
Access Assistant: Does not include any content or control which relies on the user’s ability to hear. Electronic Docs: Does not include any content or control which relies on the user’s ability to hear. Access University: Does not include any content or control which relies on the user’s ability to hear. Access Analytics:Does not include any content or control which relies on the user’s ability to hear. |
| 302.5With Limited Hearing | AMP: Supports
Access Assistant: Supports Electronic Docs: Supports Access University: Supports Access Analytics:Supports |
AMP: Does not include any content or control which relies on the user’s ability to hear.
Access Assistant: Does not include any content or control which relies on the user’s ability to hear. Electronic Docs: Does not include any content or control which relies on the user’s ability to hear. Access University: Does not include any content or control which relies on the user’s ability to hear. Access Analytics:Does not include any content or control which relies on the user’s ability to hear. |
| 302.6Without Speech | AMP: Supports
Access Assistant: Supports Electronic Docs: Supports Access University: Supports Access Analytics:Supports |
AMP: Does not include any content or control which relies on the user’s ability to speak.
Access Assistant: Does not include any content or control which relies on the user’s ability to speak. Electronic Docs: Does not include any content or control which relies on the user’s ability to speak. Access University: Does not include any content or control which relies on the user’s ability to speak. Access Analytics:Does not include any content or control which relies on the user’s ability to speak. |
| 302.7With Limited Manipulation | AMP: Partially Supports
Access Assistant: Partially Supports Electronic Docs: Supports Access University: Supports Access Analytics:Partially Supports |
AMP: All core functionality and most secondary functionality is usable by people with limited ability to manipulate controls with the following exceptions:
Access Assistant: All core functionality and most secondary functionality is usable by people with limited ability to manipulate controls with the following exception:
Electronic Docs: All core functionality and most secondary functionality is usable by people with limited ability to manipulate controls. Access University: All core functionality and most secondary functionality is usable by people with limited ability to manipulate controls. Access Analytics: All core functionality and most secondary functionality is usable by people with limited ability to manipulate controls with the following exception: As noted in 2.4.3 Focus Order, the table within the disclosure widget receives focus even when it is not visible. |
| 302.8With Limited Reach and Strength | AMP: Supports
Access Assistant: Supports Electronic Docs: Supports Access University: Supports Access Analytics:Supports |
AMP: Does not include any content or control which relies on the user’s ability to reach or rely on strength.
Access Assistant: Does not include any content or control which relies on the user’s ability to reach or rely on strength. Electronic Docs: Does not include any content or control which relies on the user’s ability to reach or rely on strength. Access University: Does not include any content or control which relies on the user’s ability to reach or rely on strength. Access Analytics:Does not include any content or control which relies on the user’s ability to reach or rely on strength. |
| 302.9With Limited Language, Cognitive, and Learning Abilities | AMP: Supports
Access Assistant: Supports Electronic Docs: Supports Access University: Supports Access Analytics:Supports |
AMP: Does not include any content or control which impacts a user’s limited language, cognitive or learning abilities.
Access Assistant: Does not include any content or control which impacts a user’s limited language, cognitive or learning abilities. Electronic Docs: Does not include any content or control which impacts a user’s limited language, cognitive or learning abilities. Access University: Does not include any content or control which impacts a user’s limited language, cognitive or learning abilities. Access Analytics:Does not include any content or control which impacts a user’s limited language, cognitive or learning abilities. |
Get in touch
Want to get in touch? We’d love to hear from you. Here’s how you can reach us…