Standard/Guideline

Included In Report

Web Content Accessibility Guidelines 2.0

Level A (Yes)
Level AA (Yes)

Web Content Accessibility Guidelines 2.1

Level A (Yes)
Level AA (Yes)

Web Content Accessibility Guidelines 2.2

Level A (Yes)
Level AA (Yes)

Criteria

Conformance Level

Remarks and Explanations

1.1.1 Non-text Content (Level A)

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.

• 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.

Supports

All non-text elements (like images, icons, buttons, charts, etc.) have appropriate text alternatives — such as alt text or ARIA labels — so screen readers can convey their purpose or meaning to users with disabilities.

1.2.1 Audio-only and Video-only (Prerecorded) (Level A)

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:
• 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.

N/A

All prerecorded audio-only content has a text transcript, and all prerecorded video-only content has a text or audio description — making the media content accessible to users who are deaf, hard of hearing, or blind.

1.2.2 Captions (Prerecorded) (Level A)

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.

N/A

All prerecorded videos with audio include captions that convey spoken dialogue and important sounds, making the content accessible to deaf or hard of hearing users.

1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)

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.

Supports

All prerecorded video content with important visual information has either:
• An audio description (narration of visual content), or
• A text alternative (like a transcript) that describes the visual parts —
so blind or visually impaired users can understand what’s happening.

1.3.1 Info and Relationships (Level A)

Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.

Partially Supports

• Classroom Page: Table Header <th> Element Lacks Descriptive Text (Table Header)
• Marco Polo – Reading and Film: Non-Sequential Heading Levels (Skipped Heading Levels)
• Marco Polo – Reading and Film: Heading Element Is Empty
• Schedules: <select> Element Missing Accessible Name (Classroom and Journey Collapsed Select Element)
• Schedules: Missing form label (Search Bar)
• Licenses: Empty Heading Element Present in Markup
• Setting: <dt> and <dd> Elements Used Outside of a <dl> Container
• Setting: Orphaned form label (Image)

1.3.2 Meaningful Sequence (Level A)

When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined.

Supports

Content is presented in a meaningful sequence.

1.3.3 Sensory Characteristics (Level A)

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.

Supports

No instruction for operating content was found to rely on sensory characteristics.

1.4.1 Use of Color (Level A)

Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.

Supports

Color is not the only method used to convey information — meaning all important information (like errors, links, or required fields) is also shown using text, icons, or patterns, so it’s accessible to colorblind users.

1.4.2 Audio Control (Level A)

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.

N/A

Any audio that plays automatically for more than 3 seconds has a way to pause, stop, or control the volume, so it doesn’t interfere with screen reader users or cause distractions.

2.1.1 Keyboard (Level A)

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.

Partially Supports

Mobile Header: Mobile Menu Button Is Not Focusable via Keyboard

2.1.2 No Keyboard Trap (Level A)

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.

Supports

No keyboard trap is found on any page.

2.1.4 Character Key Shortcuts (Level A 2.1 and 2.2)

If a keyboard shortcut is implemented in content using only letter (including upper- and lower-case letters), punctuation, number, or symbol characters, then at least one of the following is true:
Turn off: A mechanism is available to turn the shortcut off;
Remap: A mechanism is available to remap the shortcut to include one or more non-printable keyboard keys (e.g., Ctrl, Alt);
Active only on focus: The keyboard shortcut for a user interface component is only active when that component has focus.

Supports

No custom keyboard shortcuts were found on this site.

2.2.1 Timing Adjustable (Level A)

For each time limit that is set by the content, at least one of the following is true:
• 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.

Supports

User sessions are indefinite; no limitations are set.

2.2.2 Pause, Stop, Hide (Level A)

For moving, blinking, scrolling, or auto-updating information, all of the following are true:
• 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.

Supports

Any moving, blinking, scrolling, or auto-updating content (like carousels or animations) that lasts more than 5 seconds has a way to pause, stop, or hide it — ensuring it doesn’t distract users or interfere with screen readers.

2.3.1 Three Flashes or Below Threshold (Level A)

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.

Supports

There is no flashing content featured on this site.

2.4.1 Bypass Blocks (Level A)

A mechanism is available to bypass blocks of content that are repeated on multiple Web pages.

Supports

The site provides a way (like a “Skip to main content” link) to bypass repeated content (e.g., navigation menus), so keyboard and screen reader users can quickly reach the main content.

2.4.2 Page Titled (Level A)

Web pages have titles that describe the topic or purpose.

Supports

Each page has a unique, clear, and descriptive <title> element that accurately describes the page’s content or purpose. ✅

2.4.3 Focus Order (Level A)

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.

Supports

Keyboard navigation (Tab key) moves through interactive elements (like links, buttons, form fields) in a logical, meaningful order — matching the visual flow and expected usage without confusing jumps.

2.4.4 Link Purpose (In Context) (Level A)

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.

Partially Supports

• Main Classroom: Links Lack Discernible Text (Action Column Table)
• Marco Polo – Reading and Film: Links Lack Discernible Text (Plus Icon Button Lesson Resources)

2.5.1 Pointer Gestures (Level A 2.1 and 2.2)

All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture, unless a multipoint or path-based gesture is essential.

Supports

No non-essential path-based operational gestures are required to operate any functionality.

2.5.2 Pointer Cancellation (Level A 2.1 and 2.2)

For functionality that can be operated using a single pointer, at least one of the following is true:
No Down-Event: The down-event of the pointer is not used to execute any part of the function;
Abort or Undo: Completion of the function is on the up-event, and a mechanism is available to abort the function before completion or to undo the function after completion;
Up Reversal: The up-event reverses any outcome of the preceding down-event;
Essential: Completing the function on the down-event is essential.

Supports

No functionality is activated on the down-event; all functions get activated on the up-event.

2.5.3 Label in Name (Level A 2.1 and 2.2)

For user interface components with labels that include text or images of text, the name contains the text that is presented visually.

Supports

UI components (such as buttons, form fields, links, etc.) that have text labels (or images of text) include that same text in the accessible name — which can be provided via aria-label, aria-labelledby, or the alt attribute for images.

2.5.4 Motion Actuation (Level A 2.1 and 2.2)

Functionality that can be operated by device motion or user motion can also be operated by user interface components and responding to the motion can be disabled to prevent accidental actuation, except when:
Supported Interface: The motion is used to operate functionality through an accessibility-supported interface;
Essential: The motion is essential for the function, and doing so would invalidate the activity.

Supports

No functionality requires the user or device’s relative motion to operate.

3.1.1 Language of Page (Level A)

The default human language of each Web page can be programmatically determined.

N/A

3.2.1 On Focus (Level A)

When any component receives focus, it does not initiate a change of context.

Partially Supports

• Header: Collapsed Button Remains Expanded When Focus Moves Away

3.2.2 On Input (Level A)

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.

Supports

No unexpected change in context was observed when any element received user input.

3.2.6 Consistent Help (Level A 2.2 only)

If a Web page contains any of the following help mechanisms, and those mechanisms are repeated on multiple Web pages within a set of Web pages, they occur in the same order relative to other page content, unless a change is initiated by the user:
• Human contact details;
• Human contact mechanism;
• Self-help option;
• A fully automated contact mechanism.

Supports

The help mechanism (Support page) is consistently implemented across multiple pages.

3.3.1 Error Identification (Level A)

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.

Supports

Simulated errors were properly communicated to the user.

3.3.2 Labels or Instructions (Level A)

Labels or instructions are provided when content requires user input.

Partially Supports

Classroom Page: Form Field Missing Associated Label (Search Bar)

3.3.7 Redundant Entry (Level A 2.2 only)

Information previously entered by or provided to the user that is required to be entered again in the same process is either:
• auto-populated, or
• available for the user to select.
Except when:
• re-entering the information is essential.
• the information is required to ensure the security of the content, or
• previously entered information is no longer valid.

Supports

Autocomplete mechanisms were implemented in non-sensitive form fields across the app.

4.1.1 Parsing (Level A)
WCAG 2.0 and 2.1 – Always answer ‘Supports’
WCAG 2.2 (obsolete and removed) – Does not apply

Does Not Apply

For WCAG 2.0 and 2.1, the September 2023 errata update indicates this criterion is always supported. See the WCAG 2.0 Editorial Errata and the WCAG 2.1 Editorial Errata.

4.1.2 Name, Role, Value (Level A)

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.

Partially Supports

• Sidebar: ARIA Controls Missing Required Child Elements
• Mobile Header: Unclear ARIA Label Provided for Collapsed Button (Language Button)

Criteria

Conformance Level

Remarks and Explanations

1.2.4 Captions (Live) (Level AA)

Captions are provided for all live audio content in synchronized media.

N/A

1.2.5 Audio Description (Prerecorded) (Level AA)

Audio description is provided for all prerecorded video content in synchronized media.

N/A

1.3.4 Orientation (Level AA 2.1 and 2.2)

Content does not restrict its view and operation to a single display orientation, such as portrait or landscape, unless a specific display orientation is essential.

Supports

This site is responsive, the content looks great in portrait.

1.3.5 Identify Input Purpose (Level AA 2.1 and 2.2)

The purpose of each input field collecting information about the user can be programmatically determined when:
• The input field serves a purpose identified in the Input Purposes for user interface components section; and
• The content is implemented using technologies with support for identifying the expected meaning for form input data.

Supports

Input forms on this site were implemented with programmatically determinable codes.

1.4.3 Contrast (Minimum) (Level AA)

The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, except for the following:
• 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.

Partially Supports

• Marco Polo – Reading and Film: Low Text Contrast Between Foreground and Background Colors (Text using the foreground color #FFFFFF (white) on a background color of #FF3860) [New Attachment Popup]
• Interactive 3D Map Activity: Low Text Contrast Between Foreground and Background Colors (Text using the foreground color #FFFFFF (white) on a background color of # 9E9C3E) [Games and Activities]

1.4.4 Resize text (Level AA)

Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality.

Supports

1.4.5 Images of Text (Level AA)

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:
• 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.

Support

Text is used to convey information instead of images of text, unless the visual presentation is customizable (e.g., font size or color) or essential to the content (like logos or branding).

1.4.10 Reflow (Level AA 2.1 and 2.2)

Content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions for:
• Vertical scrolling content at a width equivalent to 320 CSS pixels;
• Horizontal scrolling content at a height equivalent to 256 CSS pixels.
Except for parts of the content which require two-dimensional layout for usage or meaning.

Support

Content can reflow (adjust to different screen sizes) without losing information or functionality, and without requiring two-dimensional scrolling for:
• Vertical scrolling at widths of 320 CSS pixels (e.g., mobile screens)
• Horizontal scrolling at heights of 256 CSS pixels

1.4.11 Non-text Contrast (Level AA 2.1 and 2.2)

The visual presentation of the following have a contrast ratio of at least 3:1 against adjacent color(s):
User Interface Components: Visual information required to identify user interface components and states, except for inactive components or where the appearance of the component is determined by the user agent and not modified by the author;
Graphical Objects: Parts of graphics required to understand the content, except when a particular presentation of graphics is essential to the information being conveyed.

Supports

All user interface components maintain a minimum contrast ratio of 3:1 with their fixed or dynamic background.

1.4.12 Text Spacing (Level AA 2.1 and 2.2)

In content implemented using markup languages that support the following text style properties, no loss of content or functionality occurs by setting all of the following and by changing no other style property:
• Line height (line spacing) to at least 1.5 times the font size;
• Spacing following paragraphs to at least 2 times the font size;
• Letter spacing (tracking) to at least 0.12 times the font size;
• Word spacing to at least 0.16 times the font size.
Exception: Human languages and scripts that do not make use of one or more of these text style properties in written text can conform using only the properties that exist for that combination of language and script.

Supports

Adding the various text spacing did not result in loss of content.

1.4.13 Content on Hover or Focus (Level AA 2.1 and 2.2)

Where receiving and then removing pointer hover or keyboard focus triggers additional content to become visible and then hidden, the following are true:
• Dismissible: A mechanism is available to dismiss the additional content without moving pointer hover or keyboard focus, unless the additional content communicates an input error or does not obscure or replace other content;
• Hoverable: If pointer hover can trigger the additional content, then the pointer can be moved over the additional content without the additional content disappearing;
• Persistent: The additional content remains visible until the hover or focus trigger is removed, the user dismisses it, or its information is no longer valid.
Exception: The visual presentation of the additional content is controlled by the user agent and is not modified by the author.

Supports

2.4.5 Multiple Ways (Level AA)

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.

Supports

In addition to navigation links on the navbar and the footer.

2.4.6 Headings and Labels (Level AA)

Headings and labels describe the topic or purpose.

Partially Supports

Mentioned in 4.1.2

2.4.7 Focus Visible (Level AA)

Any keyboard-operable user interface has a mode of operation where the keyboard focus indicator is visible.

Supports

2.4.11 Focus Not Obscured (Minimum) (Level AA 2.2 only)

When a user interface component receives keyboard focus, the component is not entirely hidden due to author-created content.

Supports

When a user navigates with a keyboard, the focused element is at least partially visible and not hidden behind headers, popups, or other content — ensuring users always see where they are on the page.

2.5.7 Dragging Movements (Level AA 2.2 only)

All functionality that uses a dragging movement for operation can be achieved by a single pointer without dragging, unless dragging is essential or the functionality is determined by the user agent and not modified by the author.

Supports

No functionality requires dragging movements to complete.

2.5.8 Target Size (Minimum) (Level AA 2.2 only)

The size of the target for pointer inputs is at least 24 by 24 CSS pixels, except where:
Spacing: Undersized targets (those less than 24 by 24 CSS pixels) are positioned so that if a 24 CSS pixel diameter circle is centered on the bounding box of each, the circles do not intersect another target or the circle for another undersized target;
Equivalent: The function can be achieved through a different control on the same page that meets this criterion;
Inline: The target is in a sentence or its size is otherwise constrained by the line-height of non-target text;
User-agent control: The size of the target is determined by the user agent and is not modified by the author;
Essential: A particular presentation of the target is essential or is legally required for the information being conveyed.

Supports

The mobile version of this site features sufficient sizes for touch targets.

3.1.2 Language of Parts (Level AA)

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.

Supports

No part of the site’s content featured a language that is different from the page’s language.

3.2.3 Consistent Navigation (Level AA)

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.

Supports

Repeated navigational elements appear in the same relative order on multiple pages.

3.2.4 Consistent Identification (Level AA)

Components that have the same functionality within a set of Web pages are identified consistently.

Supports

Identification of components with the same functionality is consistent.

3.3.3 Error Suggestion (Level AA)

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.

Supports

An autocomplete or error prevention feature was found to be implemented on relevant input fields.

3.3.4 Error Prevention (Legal, Financial, Data) (Level AA)

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:
• 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.

Supports

The payment processing on this site is handled by a third-party service.

3.3.8 Accessible Authentication (Minimum) (Level AA 2.2 only)

A cognitive function test (such as remembering a password or solving a puzzle) is not required for any step in an authentication process unless that step provides at least one of the following:
Alternative: Another authentication method that does not rely on a cognitive function test.
Mechanism: A mechanism is available to assist the user in completing the cognitive function test.
Object Recognition: The cognitive function test is to recognize objects.
Personal Content: The cognitive function test is to identify non-text content the user provided to the Web site.

Supports

The site’s login or authentication process does not rely only on cognitive tests (like solving puzzles, remembering passwords, or recognizing images) — or provides an alternative method, so users with cognitive disabilities can log in without extra barriers.

4.1.3 Status Messages (Level AA 2.1 and 2.2)

In content implemented using markup languages, status messages can be programmatically determined through role or properties such that they can be presented to the user by assistive technologies without receiving focus.

Supports

The dynamic statuses of operations on this site are properly communicated to the user without a disruptive change of focus.