ACR Index Accessibility Conformance Reports for software

Packback Application (https://dev-app.packback.ca/)

Accessibility Conformance Report published by Packback

Conformance by level

Reported by the vendor. WCAG Level AA is the benchmark referenced by ADA Title II, Section 508 and the European Accessibility Act; Level AAA is optional and often left unevaluated.

Source: View the original report published by Packback.

These figures are extracted from that document. They are the vendor's own statements, not an independent assessment, and automated extraction can misread a table.

All reported criteria (55)

Conformance as stated by Packback in its published report.
CriterionNameLevel ConformanceRemarks from vendor
1.1.1 Non-text Content A Supports Most of the informative images/icons available in the application have appropriate text alternatives that present equivalent information to visually impaired users using screen readers and the images used solely for decorative purposes have been hidden from these assistive technologies. However, there are a few exceptions where text alternatives are missing, unclear, or do not fully convey the intended meaning. Update: In June 2026, the Packback team resolved these exceptions, and moved this criterion to “Supports” from “Partially Supports”. Previously Noted Exceptions: 1. [Global] Select any Community > Course Details > Screen reader focus moves to decorative separator. 2. Account Settings > Edit Avatar > Decorative separator is exposed to assistive technologies. 3. Sign Up > Step 2 > Password pass/fail criteria information is not available for screen reader users.
1.2.1 Audio-only and Video-only (Prerecorded) A Not Applicable There is no audio-only or video-only content present in the application.
1.2.2 Captions (Prerecorded) A Supports Captions are available for all the multimedia content in the application.
1.2.3 Audio Description or Media Alternative (Prerecorded) A Supports All meaningful visual information is conveyed through the audio track; no additional audio description or media alternative is required.
1.3.1 Info and Relationships A Partially Supports Most of the elements available in the application have been correctly marked up using HTML semantics that allows assistive technologies like screen readers to identify their appropriate structure and relationships. However, there are a few exceptions, where screen reader users face difficulties in identifying the information, structure, and relationships of some elements conveyed via visual representation. Few Exceptions: 1. Content Library > My Templates > Heading hierarchy is not logical on page. 2. Admin Details > <dl>, <dt> and <dd> elements are not structured properly. 3. Manage Discussion Assignment > Incorrect screen reader announcement for tab options. 4. Communities > Select any Community > Course grade value is not announced by screen reader.
1.3.2 Meaningful Sequence A Partially Supports Screen readers read most of the content available in the application in a logical sequence using arrow keys or other reading methods that perceive their meaning and context for visually impaired users. However, there are a few exceptions where screen reader users face difficulties in perceiving the content in a logical sequence.
1.3.3 Sensory Characteristics A Supports Most of the visual cues and symbols used in the application that convey specific meanings are provided with equivalent text alternatives. However, there are a few exceptions where the information conveyed through symbols does not have equivalent text alternatives. Update: In June 2026, the Packback team resolved these exceptions, and moved this criterion to “Supports” from “Partially Supports”. Previously Noted Exceptions: 1. Course Goals > Video > Tooltip or visible text is missing for share icon control. 2. Communities > Footer > Tooltip is missing for social media icon controls. 3. Product Updates Modal > Tooltip is missing for reaction options in emoji menu.
1.4.1 Use of Color A Supports Most of the information conveyed through color highlights is also presented with text labels and meaningful icons, ensuring it is accessible to users with color vision deficiencies. However, there are a few exceptions where color alone is used to convey information.
1.4.2 Audio Control A Not Applicable There is no such audio available in the application that plays automatically as soon as any page is launched.
2.1.1 Keyboard A Partially Supports Application has many interactive user interface components like buttons, links, checkboxes, etc. Most of these elements are operable using keyboard and keyboard interfaces. However, there are a few exceptions, where users dependent upon keyboard operation, such as visually impaired users and motor-impaired users, face difficulties in accessing some components. Few Exceptions: 1. Communities > Header > My Account menu is not getting collapsed using Esc key. 2. Writing Assignments > Original Document > 'Adobe' icon control is not accessible with keyboard. 3. Login > 'Product Updates' control is not accessible with keyboard. 4. Course Goals > Video > 'Share' modal is not getting collapsed using Esc key.
2.1.2 No Keyboard Trap A Supports Keyboard focus is not trapped anywhere in the application.
2.1.4 Character Key Shortcuts A Not Applicable Single key character shortcuts are not used anywhere in the application.
2.2.1 Timing Adjustable A Not Applicable There is no such time-based activity available in the application.
2.2.2 Pause, Stop, Hide A Not Applicable The application does not feature any moving, blinking, or auto-updating content that would need to be paused or stopped for individuals with certain disabilities.
2.3.1 Three Flashes or Below Threshold A Supports There is no flashing / blinking content available anywhere in the application.
2.4.1 Bypass Blocks A Partially Supports The “Skip to main Content’ link is available on most of the pages of the application to help screen reader users and keyboard users to bypass the repetitive block of header content in a single activation to locate the page main content. However, there is an exception on ‘Invite Students’ page under community settings where skip to main content link is not accessible via keyboard.
2.4.2 Page Titled A Supports All pages in the application are given a unique and descriptive title to help users understand the context.
2.4.3 Focus Order A Partially Supports Focus order is logical for most of the interactive elements/widgets available in the application using the keyboard and keyboard interfaces. However, there are a few exceptions, where TAB order is incorrect for some components, and logical focus has not been maintained in some custom dialogs. Few Exceptions: 1. Course Goals > Video > Keyboard focus is moving to hidden elements within video frame. 2. Select any community > Keyboard focus does not move inside the expanded menu when hamburger control is activated. 3. Gradebook > Automated Grading Report > Keyboard focus moves to top of the page when 'Next' or 'Previous' control is activated.
2.4.4 Link Purpose (In Context) A Partially Supports All the links available in the application are provided with sufficient link text that clearly describes the purpose/ target destination of these elements. However, there are few exceptions where link text is not sufficient and does not describe the purpose of target/destination clearly. Few Exceptions: 1. [Global] Homepage > Packback logo link has insufficient accessible name. 2. Product Updates Modal > Descriptive aria-label is required for 'here' links.
2.5.1 Pointer Gestures A Not Applicable This application does not require multipoint or path-based gestures for operation.
2.5.2 Pointer Cancellation A Supports All the user interface controls available in the application get activated on an UP event. Even if a user accidentally clicks on a control, she/he can move away from its target area and lift the pointer to abort the action.
2.5.3 Label in Name A Partially Supports Most of the visible labels of the active user interface elements match their accessible names. Motor-impaired users can activate these interactive elements by calling their visible text labels using a speech recognition tool like 'Dragon'. However, there is an exception on the ‘Subscribe Now’ page under the writing lab where the accessible name of the link does not match its visual label.
3.1.1 Language of Page A Supports Application content is available in English language, and this language is programmatically defined using the lang = “en” attribute in the <html> tag on all the web pages.
3.2.1 On Focus A Supports There is no change in context when keyboard focus moves to any element in most of the components in the application.
3.2.2 On Input A Supports This application ensures that interactive components do not initiate a change in context when the component setting is changed unless followed by an explicit user action such as activation of a button or link.
3.2.6 Consistent Help A Supports Help mechanisms such as contact details links and contact us links are occurring in the same order on every page of the application, which helps the user to locate help options on every screen consistently.
3.3.1 Error Identification A Supports All error messages/warnings available in the application are available in textual form that is readable using screen readers.
3.3.2 Labels or Instructions A Supports The form fields available in the application are associated with meaningful text labels that explain their purpose. However, there are a few exceptions where appropriate labels and instructions are missing some input elements. Update: In June 2026, the Packback team resolved these exceptions, and moved this criterion to “Supports” from “Partially Supports”. Previously Noted Exceptions: 1. Products Updates Modal > Ideas Tab > Vote > Let us Know Who You Are Modal > Visual label is missing for input fields. 2. Product Updates Modal > Visual label is missing for 'Add a comment' input field.
3.3.7 Redundant Entry A Supports For all multi-step processes present in the application having repeated input fields, previously entered information would not need to be re-entered.
4.1.2 Name, Role, Value A Partially Supports Application has many interactive elements like buttons, links, edit fields, etc., which are provided with meaningful
1.2.4 Captions (Live) AA Not Applicable There is no live multimedia content available in the application.
1.2.5 Audio Description (Prerecorded) AA Supports All meaningful visual information is conveyed through the audio track; no additional audio description or media alternative is required.
1.3.4 Orientation AA Supports This application does not restrict its view and operation to a single display orientation, such as portrait or landscape [unless a specific orientation is essential].
1.3.5 Identify Input Purpose AA Supports The application ensures that all forms that collect users’ personal information include appropriate autocomplete attributes. However, there is an exception on ‘Sign Up’ page where ‘First name’ and ‘Last name’ input fields do not have the autocomplete attribute. Update: In June 2026, the Packback team resolved the exception above, and moved this criterion to “Supports” from “Partially Supports”.
1.4.3 Contrast (Minimum) AA Partially Supports Application has a sufficient contrast ratio of 4.5:1 or greater for most of the color combinations used for regular text and its background, and 3:1 for the large text. However, there are few exceptions where the color contrast ratio is not sufficient. Few Exceptions: 1. Community Settings > Edit Community Details > Date Picker > Color contrast ratio fails for 'Close Calendar' control. 2. Account Settings > Writing Lab Subscription > The color contrast ratio of text "Cancel subscription" control is less than standard ratio 4.5:1. 3. Login > Product Updates Modal > Placeholder text has insufficient color contrast ratio.
1.4.4 Resize text AA Supports The application components remain easily operable and accessible when the application pages are resized up to 200% browser zoom.
1.4.5 Images of Text AA Not Applicable Application does not have images of text, instead Regular text, HTML and CSS are used to provide different visual presentations to all the meaningful content.
1.4.10 Reflow AA Partially Supports Most of the web pages in the application properly reflow into a vertical single column when the viewport width is set to 320px, which is equivalent to 400% zoom on a 1280px-wide screen. However, there are a few exceptions where some content is lost at that width. Few Exceptions: 1. Publish and Share Course > At 320 CSS Pixels, main section content is not visible properly. 2. Match & Message > Sent Messages > At 320 CSS Pixels, combo box value is not visible properly. 3. Community Settings > Edit Community Details > Date Picker > At 320 CSS Pixels, content present in date picker flyout is not visible properly.
1.4.11 Non-text Contrast AA Partially Supports Application has sufficient contrast for different active user interface components. Non-Text UI elements such as buttons, input form fields, etc. have a contrast ratio of at least 3:1 to their adjacent colors. However, there are a few exceptions where the color contrast ratio is not sufficient. Few Exceptions: 1. Publish and Share Course > Color contrast ratio fails for focus indicator on form steps. 2. Writing Assignments > Select any Deep Dive Assignment > Color contrast ratio fails for focus indicator on 'Back to deep dive assignments' control. 3. Product Updates Modal > The color contrast ratio of graphical element is less than standard ratio 3:1.
1.4.12 Text Spacing AA Supports This success criteria have been validated for persons with low vision and reading disabilities using Steve Faulkner’s Text Spacing Bookmarklet, and all the application content is easily readable and accessible after adjusting the text spacing using this tool.
1.4.13 Content on Hover or Focus AA Partially Supports Most of the additional content in the application triggered by keyboard focus or mouse hover is dismissible, hoverable, and remains persistent. However, there are few exceptions where tooltip content is not dismissible, persistent or hoverable. Few Exceptions: 1. Course Goals > Video > Packback logo tooltip text is not dismissible using Esc key. 2. My Profile > My Grades > Tooltip of table headers are not dismissible using Esc key. 3. Account Settings > Edit Avatar > Radio buttons tooltip is not getting closed using Esc key.
2.5.4 Motion Actuation A Not Applicable This application does not contain functionality that requires device motion or user motion.
2.4.5 Multiple Ways AA Supports All application sections are directly accessible via the navigation menu located at the top of the page, and there is a navigation menu available on the left side of the page to access all features.
2.4.6 Headings and Labels AA Partially Supports Headings and labels throughout the application are generally descriptive, providing clear context and purpose. Most user interface components are appropriately labeled. However, there is an exception on the ‘Notifications’ page where pagination control buttons do not have descriptive accessible names.
2.4.7 Focus Visible AA Supports Most of the interactive elements receive a clear visual focus indicator while using the keyboard. Users are able to identify the currently focused element while navigating the page using the Tab key. However, there are a few exceptions where the focus indicator is not visible on elements. Update: In June 2026, the Packback team resolved these exceptions, and moved this criterion to “Supports” from “Partially Supports”. Previously Noted Exceptions: 1. Course Goals > Video > Keyboard focus is not visible on social media links in Share Modal. 2. Content Library > My Templates > Focus indicator is not proper on 'Back' control. 3. Products Updates Modal > Ideas Tab > Vote > Let us Know Who You Are Modal > Keyboard focus is not visible on checkbox control in checked state. 4. Product Updates Modal > Keyboard focus is not visible on reaction options.
2.4.11 Focus Not Obscured (Minimum) AA Supports Most of the user interface components are clearly visible when they receive keyboard focus, which helps keyboard users, low vision users, and people with attention limitations to locate the components easily. However, there are exceptions where the currently focused elements are not visible. Update: In June 2026, the Packback team resolved these exceptions, and moved this criterion to “Supports” from “Partially Supports”. Previously Noted Exceptions: 1. Course Goals > Video > 'Forward' and 'Backward' icons in video are not visible on screen. 2. Course Goals > Video > 'Packback' logo is not visible while receiving keyboard focus.
2.5.7 Dragging Movements AA Not Applicable Application does not have any author created draggable components.
2.5.8 Target Size (Minimum) AA Partially Supports Most of the interactive elements available in the application have target size of 24 by 24 or above for the pointer inputs, that helps users with dexterity impairment to activate these controls independently while using specialized inputs or touch interfaces. However, there is an exception in the ‘Products Updates’ modal where target size fails for emoji icon control.
3.1.2 Language of Parts AA Not Applicable Application uses only one language “English” throughout web pages. There is no passage or phrase available in another language where the language of that content needs to be defined.
3.2.3 Consistent Navigation AA Supports Repeated components, such as navigation links, are occurring in the same order on every page of the application, which helps the user predict the location of various UI elements on every screen.
3.2.4 Consistent Identification AA Supports All the elements that have the same functionality across multiple pages in the application are identified with the same label and role.
3.3.3 Error Suggestion AA Supports All the Feedback/ Error messages available in the application are descriptive enough to understand and correct the errors. However, there is an exception (Contact Us) where the error messages are not descriptive.
3.3.4 Error Prevention (Legal, Financial, Data) AA Not Applicable This success criterion pertains to legal commitments, financial data, and other areas that carry significant risks if users are not given the opportunity to review or revert to their data before submission. However, this application does not include any forms associated with such risks.
3.3.8 Accessible Authentication (Minimum) AA Supports The authentication process of the application is not dependent solely upon the cognitive function test, such as remembering the password or solving the puzzle. Users with cognitive disabilities can enter the login credentials by pasting them from the clipboard, by using the browser's autofill service, or using the password managers.
4.1.3 Status Messages AA Partially Supports Most dynamic changes and alerts are automatically identified by assistive technology (screen readers). However, there are a few exceptions where status messages are not announced by assistive technology.

Is this your product? If this report is out of date or misrepresented, we will correct or remove it. Contact us to claim this listing.

Get told when this changes

This report is dated May 6, 2026. An ACR can be quietly replaced at any time, and the published date is the only signal a buyer gets. We will email you when this one is updated.

Double opt-in — we email you once to confirm, and send nothing until you do. One-click unsubscribe on every message. We store your address and what you are watching, nothing else. Privacy.