YuJa EqualGround scans for a variety of common issues in your web pages and documents. This guide provides an overview of all issues that are detected using the platform, including the issue name, description, and additional details where applicable.
Accessibility issues
Note: All issues listed in the WCAG, ARIA, and Best practices tables can be resolved by YuJa AutoPilot and In-line Remediation.
WCAG
| Issue name | Issue description | Remediation summary |
| Missing Alt Attributes on Non-Text Content | The img element is missing alternative text. | Adds accessible name. |
| Missing Alt Text for Image Buttons | This image is used as a button, but it has no alternative text, so screen reader users cannot tell what the button does. | Adds accessible name. |
| Missing Alternative Text on Elements with Img Role | This element is marked up as an image (role="img") but has no description. | Adds accessible name. |
| Presentational Roles and Hidden States on Decorative Content | This decorative element is announced by screen readers even though it carries no information. | Adds aria-hidden="true" to <svg>; sets role="presentation" on <img>/<area>. |
| Redundant Title Attributes on Images with Empty Alternative Text | This image is marked as decorative (empty alt text) but still has a tooltip title, so screen readers announce it anyway. | N/A |
| Missing Audio Transcript Issues | This audio player has no transcript, so people who are deaf or hard of hearing cannot access its content. | Adds <track> as a children. |
| Missing Captions in Embedded Vimeo Videos | This embedded Vimeo video has no captions. | Unable to modify video captions from other platforms. |
| Missing Captions in Embedded YouTube Videos | This embedded YouTube video has no captions. | Unable to modify video captions from other platforms. |
| Missing Captions in Video Content | This video has no captions, so people who are deaf or hard of hearing cannot follow it. | Adds <track> as a children. |
| Improper Definition List Structure | This description list contains content that is neither a term nor a description, so the pairing breaks down. | Enforces valid structure within Description Lists (<dl>) by wrapping invalid direct children in <dd> tags. |
| Improper List Structure | This list contains content that is not a list item, so screen readers announce the wrong number of items. | Inserts list items to proper places to fix a list structure within tables. |
| Incorrect Use of headers Attribute by Using scope in Tables | This table uses plain data cells as headers, so screen readers cannot link each value to the right heading. | Adds missing <th> elements to the <thead> and setting columnheader roles on existing headers. |
| Incorrect Use of Scope Attribute in Tables | The scope attribute is used on a cell that is not a header, so screen readers cannot work out the table's structure. | Sets the attribute of a table role to 'col' or 'row' depending on it's location. |
| Missing Aria-Level on Heading Roles | This element acts as a heading but does not say what level it is, so screen reader users cannot tell where it sits in the page outline. | Adds aria-level of 1, 2, 3, 4, 5, or 6. |
| Missing Fieldset or Group for Same-Name Inputs | These radio buttons or checkboxes are grouped together, but lack a label telling screen reader users what the group represents. | N/A |
| Missing Legend in Fieldset | The <fieldset> element is missing a <legend>, so screen readers cannot identify the context or group label for these form fields. | Adds a legend element as the first child of a fieldset. |
| Missing Parent for Definition Elements | This term or description is not inside a description list, so screen readers cannot pair the two together. | Wraps orphaned <dt> or <dd> elements in a <dl> container. |
| Missing Parent for List Items | This list item is not inside a list, so screen readers do not announce it as part of a list. | Wraps orphaned <li> elements in a <ul> or <ol> container. |
| Table Headers Do Not Contain Table Data | This table's header cells have no data cells associated with them, so the headers describe nothing. | Inserts a new, populated data cell into the correct position to ensure every header is associated with meaningful content. |
| Apple Mobile Web App Orientation Issues | This page locks itself to one screen orientation, so people who mount their device in a fixed position cannot use it. | Changes the apple orientation to 'any'. |
| Meta Viewport Orientation Issues | This page's viewport settings lock the orientation or block zooming, so people who need to rotate or magnify the page cannot. | Sets the correct attribute and it's value for meta viewports. |
| Invalid Autocomplete Values in Form Fields | This form field does not tell the browser what kind of information it collects, so it cannot be filled in automatically. | Validates the autocomplete attribute on form elements and resets it to 'off' if the value is invalid. |
| Missing Autocomplete Attribute in Form Fields | This form field does not tell the browser what kind of information it collects, so it cannot be filled in automatically. | N/A |
| Missing Link Styling for Links | This link is only distinguished from the text around it by its colour, so people who cannot see colour differences will miss it. | Forces standard link styling by adding an underline and a pointer cursor to anchor tags that lack them. |
| Missing Audio Controls in Audio Players | This audio plays without giving the user any way to pause or stop it. | Adds controls attribute. |
| Low Contrast Issues in Text | This text does not stand out enough from its background, so people with low vision may not be able to read it. | Updates the text color to the inverse of the background color. |
| Enhanced Contrast Issues in Text | This text does not meet the enhanced contrast level required at WCAG AAA. | Updates the text color to the inverse of the background color. |
| Absolute Font Sizes in Paragraphs | This paragraph's text size is fixed in pixels, so it does not respond when a reader increases their browser text size. | Sets the fontsize to 1em. |
| Absolute Line Heights in Paragraphs | This paragraph's line spacing is fixed in pixels, so it does not grow when a reader increases their text size. | Sets the line height to 1.5em. |
| Insufficient Line Spacing in Paragraphs | The lines in this paragraph sit too close together, which makes the text hard to read for people with dyslexia or low vision. | Sets the line height to 1.5em. |
| Justified Text Alignment in Paragraphs | This paragraph is justified, which creates uneven gaps between words and makes the text harder to read. | Sets the text alignment to be left. |
| Viewport Restriction Issues | This page does not adapt to the width of the screen, so people on small screens or at high zoom have to scroll sideways to read it. | Sets the content attribute to the correct values. |
| Controls with Low Contrast Issues | The border, background or text of this form control does not stand out enough, so people with low vision may not see it. | Updates the text color to the inverse of the background color. |
| Inaccessible Letter Spacing | This text stops readers widening the space between letters, which some people need in order to read comfortably. | Sets the letter spacing to 0.12em using an important inline style declaration. |
| Inaccessible Line Height | This text stops readers increasing the space between lines, which some people need in order to read comfortably. | Sets the line-height to 1.5em. |
| Inaccessible Word Spacing | This text stops readers widening the space between words, which some people need in order to read comfortably. | Sets the word-spacing to 0.16em. |
| Inaccessible Scrollable Regions | This area scrolls, but keyboard users cannot reach it because it cannot receive focus. | Sets the node's tab index to 0. |
| User-Controlled Timed Content Changes | This page refreshes itself on a timer, which can interrupt people who read slowly or use a screen reader. | Sets the meta refresh's content attribute to 72000. |
| Deprecated Tags in Content | This content uses a blinking or scrolling tag that browsers no longer support, and that can cause problems for people with attention or vestibular conditions. | Removes the deprecated element. |
| Missing Bypass Mechanism | Keyboard and screen reader users have to tab through the whole header on every page before they reach the content. | Adds a visible "skip to main content" link at the start of the body and ensures a valid target element exists. |
| Missing Page Titles | This page has no title, so it shows as "Untitled" in browser tabs, bookmarks and search results, and screen readers announce nothing when it loads. | Adds a placeholder title to the html. |
| Incorrect Focus Order | Keyboard focus jumps around this page instead of following the order things appear on screen. | Sets the node's tab index to 0. |
| Link Purpose Issues | Several links on this page share the same text but go to different places, so screen reader users cannot tell them apart. | Updates the href attribute by copying the destination from another element with the same accessible name or uses a placeholder if no match is found. |
| Missing Page Headings | This page lacks a main heading, making it difficult for screen reader users to quickly understand the main topic or navigate the structure. | Adds a h1 element to the body. |
| Missing Section Headings | This section has no heading, so screen reader users cannot tell what it contains or skip past it. | Inserts an h2 heading containing default text as the first child of the element. |
| Insufficient Interactive Element Size | This control is too small to click or tap reliably, which is difficult for people with limited dexterity. | Sets the node's minimum width to 44px and minimum height to 44px. |
| Small Touch Target Size | This control is too small to tap accurately on a touchscreen, or it sits too close to the one next to it. | N/A |
| Small Touch Target Size | This control is too small to tap accurately on a touchscreen, or it sits too close to the one next to it. | N/A |
| Mismatched Declared Language | This page declares two different languages, so screen readers cannot tell which pronunciation to use. | Unable to obtain the HTML reference node. |
| Missing Language Declaration | This page does not say what language it is written in, so screen readers may read it with the wrong pronunciation. | Unable to obtain the HTML reference node. |
| Invalid Value for Lang Attribute | The page uses an invalid language code, causing screen readers to fall back to default settings and mispronounce content. | N/A |
| Unexpected Context Changes on Focus | This form submits as soon as a field is focused or hovered, which takes control away from the user. | N/A |
| Users About New Tabs | This link opens in a new tab without warning, which can disorient screen reader users and people using magnification. | Adds "(opens in a new tab)" in addition to the orginal node attribute. |
| Error Descriptions for Input Fields as Atomic | When this error message updates, screen readers read out only the part that changed, so the message stops making sense. | Sets the aria-atomic value to 'true'. |
| Missing Accessible Name on Buttons | This button has no text or label, so screen reader users hear only element's generic name. | Adds aria-label of 'Button'. |
| Missing Accessible Name on Input/Select/Textarea | This form field has no label, so screen reader users do not know what to enter. | Adds accessible name. |
| Missing Accessible Names for <iframe> | This embedded frame has no title, so screen reader users cannot tell what it contains before they enter it. | N/A |
| Missing Link Descriptions | The link does not have descriptive link text or an accessible label, causing screen reader users to hear only "link" without any indication of its destination. | Adds accessible name. |
| Nested Interactive Controls | One clickable control is placed inside another, so screen readers and keyboards cannot tell them apart or reach both. | Converts links/buttons to static spans, deletes form inputs, and strips interactive attributes. |
ARIA
| Issue name | Issue description | Remediation summary |
| Invalid ARIA Attributes | This element has an ARIA attribute that is not allowed on it, so assistive technology may describe it incorrectly. | Removes any ARIA attributes from an element that are invalid or unsupported for its assigned role to ensure the element's accessibility semantics remain valid. |
| Invalid ARIA Attributes | This element has an ARIA attribute that is not allowed on it, so assistive technology may describe it incorrectly. | N/A |
| Invalid ARIA Roles | The element does not have a valid role value. | Removes invalid role attributes from visible elements, attempting to replace them with the element's correct implicit role or removing the attribute entirely to restore valid semantics. |
| Missing Accessible Name for Braille Properties | This element has a braille label but no corresponding text label, leaving no text alternative for users who rely on assistive technologies. | Ensures valid Braille ARIA usage by removing Braille-specific attributes if their required standard counterparts are missing. |
| Missing Accessible Name for Braille Properties | This element has a braille label but no corresponding text label, leaving no text alternative for users who rely on assistive technologies. | Ensures valid Braille ARIA usage by removing Braille-specific attributes if their required standard counterparts are missing. |
| Conditionally Incorrect ARIA Attributes | The conditions for the use of the ARIA label are not appropriate. Certain ARIA labels can only be used on elements if certain conditions are met. | Removes redundant aria-checked attributes from native checkboxes and upgrades a table's role to treegrid. |
| Use of Deprecated ARIA Roles | The value assigned to the role attribute is deprecated and no longer valid. | Detects deprecated ARIA roles and either replaces them with a modern equivalent (specifically mapping directory to section) or strips the attribute to ensure standards compliance. |
| Invalid ARIA Dialogs | The dialog lacks an accessible name, making it difficult for screen reader users to identify its purpose or determine what has opened. | Ensures the dialog has a valid accessible name by adding an aria-label derived from its text content or a default fallback if no explicit labeling attributes exist. |
| Hidden Body Element | The entire page is hidden from assistive technology, preventing users from accessing any of its content or functionality. | Removes aria-hidden attrbute. |
| Missing Accessible Names for Input Fields | This input does not have an accessible label, so screen reader users cannot determine what information they are expected to enter. | Applies a default "Toggle Option" label if one is missing, or explicitly setting the aria-label to match the existing text. |
| Use of Prohibited ARIA Attributes | The ARIA attribute is prohibited from being used for the element’s role. | Removes ARIA attributes that are strictly forbidden for an element's role. |
| Redundant ARIA Roles | This element already has the semantics provided by the role, so the role is redundant. | N/A |
| Missing Required ARIA Attributes | This element's role requires an attribute that is missing, so assistive technology cannot report its state. | Adds default attribute values for the invalid attributes. |
| Missing Required ARIA Children | The element has a missing child role value. | Adds missing required child elements and removing invalid children. |
| Missing Required ARIA Parent | The element has a missing parent role value. | Removes incorrect ARIA Roles. |
| Use of Invalid ARIA Role Description | The element with the aria-roledescription attribute requires an explicit or implicit supported role. | Removes aria-roledescription from decorative or role-less elements (where it is forbidden) and converts it into an aria-label. |
| Use of Abstract ARIA Roles | The assigned ARIA role value is not valid. Role values should be checked for spelling errors and correspond to existing ARIA role values. | Removes any role attributes that are typos, unsupported, or "abstract" roles. |
| Invalid ARIA Role Usage | The assigned ARIA role value is not valid. Role values should be checked for spelling errors and correspond to existing ARIA role values. | Removes any role attributes that are typos, unsupported, or "abstract" roles. |
| Use of Unsupported ARIA Roles | The assigned ARIA role value is not valid. Role values should be checked for spelling errors and correspond to existing ARIA role values. | Removes any role attributes that are typos, unsupported, or "abstract" roles. |
| Missing Accessible Names for Input Fields | The element with a semantic role does not have an accessible name. | Applies a default "Toggle Option" label if one is missing, or explicitly setting the aria-label to match the existing text. |
| Invalid ARIA Attributes | This attribute is not a real ARIA attribute - it is misspelled or does not exist, so assistive technology ignores it. | Removes all invalid ARIA attributes. |
| Invalid ARIA Attribute Values | This ARIA attribute of the element contains an invalid value. | Corrects invalid values assigned to ARIA attributes by resetting them to safe defaults. |
| Global ARIA Attributes on Presentation Role Elements | This element is marked as decorative but remains keyboard accessible, causing screen reader users to encounter an element that is not announced. | Removes explicit role attributes that exactly match the element's built-in implicit role. |
| Focusable Elements Using the Presentation Role | This element is marked as decorative but remains keyboard accessible, causing screen reader users to encounter an element that is not announced. | Removes the role if the element is focusable to restore its semantic value, or by stripping conflicting global ARIA attributes to maintain its decorative status. |
Best Practices
| Issue name | Issue description |
| Mismatched Accessible Name and Visible Label | The text displayed as the label for the interactive element does not appear in the programmed accessible name specified in the HTML, such as those provided by <label> and <aria-label> tags. |
| Empty Headings | Headings do not contain any meaningful description, which can be confusing when navigating. |
| Skipped Heading Levels | Certain heading levels have been skipped in the page, which breaks the logical structure of the content. |
| Repeated Alt Text on Images | This image's alt text repeats wording that already appears right next to it. |
Landmark Roles on Nested Elements | The role of the landmark is not applied to the correct page hierarchy. |
| Incorrect <noscript> Elements | The page includes <noscript> elements that provide content only when JavaScript is disabled. |
| Missing Heading One (H1) | The page does not include a level one heading, which is meant to identify the main topic or purpose of the page. |
| Use of Visual Tags Without Semantic Meaning | The page uses visual-only tags to style text instead of semantic tags. These tags only change how the text looks but do not provide meaning to assistive technologies. |
| Missing or Improperly Defined Surrounding Regions | This content is not contained within a landmark, making it harder for screen reader users to find when navigating by region. |
Duplicate Captions on Tables | Two or more tables on this page share the same caption. |
| Duplicate Landmark Regions | This page has more than one landmark of the same kind, so screen reader users cannot tell them apart. |
SEO issues
| Issue name | Issue description |
| Canonical Tag | Canonical tags prevent duplicate-content issues by telling search engines which version of a page is preferred. |
| Crawlable Links | Links with a missing, empty or broken destination stop search engines from finding linked pages. |
| Language & Region Tags (hreflang) | Hreflang tags tell search engines the language and region a page is meant for, so the right version shows up in search results. |
| Page Status Code | Pages that return an error status code may not be indexed by search engines. |
| Page Indexability | Pages blocked from indexing (for example by a "noindex" tag or header) can't appear in search results. |
| Descriptive Link Text | Descriptive link text helps search engines understand what the linked page is about. |
| Meta Description | Meta descriptions summarize a page and improve click-through rates from search results. |
| Meta Description Length | Meta descriptions that are empty or longer than 160 characters may be cut off or ignored in search results. |
| Page Title | Every page needs a title. It's the main headline shown in search results and browser tabs. |
| Page Title Length | Titles longer than 65 characters may be cut off in search results. |
| Robots.txt File | An invalid robots.txt file can stop search engines from crawling the site properly. |
| Social Sharing Tags (Open Graph) | Open Graph tags control how content looks when it's shared on social media. |
| Structured Data | Structured data (JSON-LD) helps search engines categorize content and can improve how the page appears in results. |
| XML Sitemap | A sitemap that includes the page helps search engines crawl the site effectively. |
| Internal Link Count | More than 100 internal links on a page can dilute link value and hurt ranking. |
| Page Redirects | Pages that redirect to another URL slow loading and can weaken search ranking. |
| Mobile Viewport Tag | Viewport meta tags make pages display properly across devices, and mobile-friendliness is a ranking factor. |
| Main Heading (H1) | Each page should have exactly one H1 heading so search engines understand its main topic. |
| Image Alt Text | Alt text helps search engines index images and improves accessibility. |
Usability issues
| Issue name | Issue description |
| Readability | Content is too complex or hard for the intended audience to understand. |
| Spelling Errors | Spelling mistakes undermine a website's credibility and professionalism. |
| Broken Links | Broken links hurt the user experience and SEO performance. |
| Unsafe Domains | Links to domains flagged as unsafe or malicious put visitors at risk. |
| Personal Information Exposure | The page may be exposing sensitive personal information by mistake: |
| Social Insurance Numbers | The page contains what look like Social Insurance Numbers (SINs). |
| Phone Numbers | The page contains phone numbers. |
| Email Addresses | The page contains email addresses. |
Performance issues
| Issue name | Issue description |
| First Contentful Paint (FCP) | The time from navigation until the browser renders the first piece of content. |
| Largest Contentful Paint (LCP) | The time from navigation until the largest visible content element is rendered. |
| Total Blocking Time (TBT) | The total time between First Contentful Paint and Time to Interactive when the page can't respond to user input. |
| Cumulative Layout Shift (CLS) | How much visible content moves around unexpectedly while the page loads. Lower is better. |
| Time to First Byte (TTFB) | The time from navigation until the browser receives the first byte of data from the server. |
| Speed Index (SI) | How quickly the page's content visibly fills in, measured as the average time visible parts of the page take to appear. |
Issues requiring manual review
Note: Issues that are indicated to require manual review require manual verification from an accessibility reviewer.
| Issue name | Issue description | Manual verification statement |
| Manual Review Required: WCAG 1.1.1 | Provide text alternatives for non-text content. | Text alternatives accurately describe non-text content. |
| Manual Review Required: WCAG 1.2.1 | 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 (1) a prerecorded audio-only, and (2) has an alternative for time-based media that presents equivalent information for prerecorded audio-only content. | Text alternatives correctly match the content of the audio or video. |
| Manual Review Required: WCAG 1.2.2 | Captions are provided for all prerecorded audio content in synchronized media, except when the media serves as an alternative to text and is clearly labeled as such. | Captions correctly match the content of the video. |
| Manual Review Required: WCAG 1.2.3 | An alternative to time-based media or audio description of prerecorded video content is provided for synchronized media, except when the media serves as an alternative to text and is clearly labeled as such. | Videos include a text alternative, and confirm that it accurately reflects the content. |
| Manual Review Required: WCAG 1.2.5 | Audio description is provided for all prerecorded video content in synchronized media. | Videos include an audio description, and that it accurately reflects the content. |
| Manual Review Required: WCAG 1.2.6 | Sign language interpretation is provided for all prerecorded audio content in synchronized media. | Audios include a sign language alternative, and confirm that it accurately reflects the content. |
| Manual Review Required: WCAG 1.2.7 | Where pauses in foreground audio are insufficient to allow audio descriptions to convey the sense of the video, extended audio description is provided for all prerecorded video content in synchronized media. | Videos include extended audio descriptions and accurately reflect their content. |
| Manual Review Required: WCAG 1.2.8 | A full-text alternative (such as a transcript) must be provided for all prerecorded synchronized media and all prerecorded video-only media. This alternative should include all visual and audio content in a single, readable format for users who cannot access video or audio. | Prerecorded media includes a full-text alternative that conveys both visual and audio content. |
| Manual Review Required: WCAG 1.3.1 | Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. | There is the appropriate use of semantics, labels, and layout tables. |
| Manual Review Required: WCAG 1.3.4 | 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. | Any enforced orientation is essential to the content or functionality. |
| Manual Review Required: WCAG 1.3.5 | In content implemented using markup languages, the purpose of user interface components and navigation mechanisms can be programmatically determined. | Autocomplete attributes correctly identify the purpose of input fields. |
| Manual Review Required: WCAG 1.4.1 | Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. | N/A |
| Manual Review Required: WCAG 1.4.2 | 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. | Automatically playing audio can be paused, stopped, or muted. |
| Manual Review Required: WCAG 1.4.3 | The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, except for large text, which must have a contrast ratio of at least 3:1. | Text meets enhanced contrast requirements based on its size. |
| Manual Review Required: WCAG 1.4.4 | Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality. | Content remains readable and functional at 200% zoom. |
| Manual Review Required: WCAG 1.4.5 | If the technologies being used can achieve the visual presentation, text is used to convey information rather than images of text, except when the image of text can be customized. | Text is not presented using images unless essential. |
| Manual Review Required: WCAG 1.4.6 | The visual presentation of text and images of text has a contrast ratio of at least 7:1, except for large text, which must have a contrast ratio of at least 4.5:1. | Text meets enhanced contrast requirements based on its size. |
| Manual Review Required: WCAG 1.4.7 | For prerecorded audio-only content with foreground speech, the background audio is either not present or is low enough not to interfere with understanding the speech. | Background audio does not interfere with speech unless it's intentional. |
| Manual Review Required: WCAG 1.4.8 | A mechanism is available to customize the visual presentation of blocks of text, such as changing foreground and background colors. | Text styling can be changed. |
| Manual Review Required: WCAG 1.4.9 | Images of text are only used for pure decoration or where a particular presentation of text is essential to the information being conveyed. | Images of text are used only for decoration or when a specific visual presentation is essential. |
| Manual Review Required: WCAG 1.4.10 | Content can be presented without loss of information or functionality, and without requiring horizontal scrolling, at a width equivalent to 320 CSS pixels. | Content remains readable and functional at 400% zoom. |
| Manual Review Required: WCAG 1.4.11 | The visual presentation of user interface components and graphical objects required to identify UI states must have a contrast ratio of at least 3:1, unless exempt. | Inactive components or graphical presentations are exempt from color contrast ratios. |
| Manual Review Required: WCAG 1.4.12 | When users override text spacing properties (such as line height, letter spacing, word spacing, or paragraph spacing) to specified minimum values, the content must remain readable and functional without loss of information or functionality. | Content remains readable and functional when text spacing is adjusted to minimum values. |
| Manual Review Required: WCAG 2.1.1 | All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, unless movement input is essential. | Interactive elements are accessible through a keyboard interface. |
| Manual Review Required: WCAG 2.1.2 | If focus can be moved to a component using a keyboard, it must also be able to move away using only a keyboard. If a non-standard exit method is required, the user must be informed. | Interactive elements are accessible through a keyboard interface. |
| Manual Review Required: WCAG 2.1.3 | If a keyboard shortcut is implemented using printable characters, users must be able to turn it off, remap it, or restrict it to components with focus. | Interactive elements are accessible through a keyboard interface. |
| Manual Review Required: WCAG 2.2.1 | For each time limit set by the content, users must be able to turn off, adjust, or extend the limit, unless it is essential or part of a real-time event. | Time limits can be turned off, adjusted, or extended. |
| Manual Review Required: WCAG 2.2.2 | For content that moves, blinks, scrolls, or updates automatically and lasts more than five seconds, users must be able to pause, stop, or hide it, unless doing so is essential. | Controls for any moving content (carousels, banners, slideshows) are keyboard-focusible and can stop the movement. |
| Manual Review Required: WCAG 2.2.3` | N/A | N/A |
| Manual Review Required: WCAG 2.2.6` | N/A | N/A |
| Manual Review Required: WCAG 2.3.1 | Content must not flash more than three times per second unless the flash is below the threshold known to cause seizures. | Animations do not flash more than three times per second or exceed thresholds for flash intensity and area. |
| Manual Review Required: WCAG 2.3.2 | Content must not flash more than three times per second. | Animations do not flash more than three times per second. |
| Manual Review Required: WCAG 2.3.3 | Motion animation triggered by user interaction must be able to be disabled, unless the animation is essential to the functionality. | Animations triggered by user interaction can be disabled. |
| Manual Review Required: WCAG 2.4.1 | Provide a way for users to bypass blocks of repeated content. | Skip links are present and work as expected. |
| Manual Review Required: WCAG 2.4.2 | Web pages must have descriptive titles that indicate the topic or purpose. | Titles accurately summarize the page content. |
| Manual Review Required: WCAG 2.4.3 | Focusable components must receive focus in an order that preserves meaning and operability. | Focus orders move in a logical order that preserves meaning and functionality. |
| Manual Review Required: WCAG 2.4.4 | The description of the link is unclear without further context, and adjacent links should not point to the same URL. | Links clearly indicate their purpose. |
| Manual Review Required: WCAG 2.4.5 | Provide at least two ways to locate each web page, unless it is part of a process. | There are at least two methods to locate each web page. |
| Manual Review Required: WCAG 2.4.6 | Headings and labels must describe the topic or purpose of their associated content. | Headings and labels clearly describe the purpose of their content. |
| Manual Review Required: WCAG 2.4.7 | A visible focus indicator must be present for any keyboard-operable user interface component. | Interactive components have a visible keyboard focus. |
| Manual Review Required: WCAG 2.4.8 | Information about the user's location within a set of web pages must be available to support orientation and navigation. | Page locations are clearly indicated within the website. |
| Manual Review Required: WCAG 2.4.9 | The purpose of each link must be identifiable from the link text alone, except where the link's purpose would be ambiguous to most users. | Links contain sufficient context or description to satisfy their purpose. |
| Manual Review Required: WCAG 2.4.10 | Use section headings to organize content and aid in navigation, even if headings are not required for the structure. | Section headings are logical and distinct. |
| Manual Review Required: WCAG 2.5.2 | Functionality that can be operated using a single pointer must not trigger on the down-event unless it is essential, or must allow the action to be aborted or reversed. | Actions are not triggered on pointer down unless essential. |
| Manual Review Required: WCAG 2.5.3 | The visible text label for a user interface component must be included in its accessible name to support assistive technologies. | Visible labels match the accessible names of UI components. |
| Manual Review Required: WCAG 2.5.5 | Clickable elements must be at least 44 by 44 CSS pixels, unless they meet exceptions such as being inline or having sufficient spacing. | Smaller interactive targets are exempt from the size requirement. |
| Manual Review Required: WCAG 2.5.7 | All functionality that uses a dragging movement must be operable without dragging, unless it is essential or controlled by the user agent. | Drag-and-drop actions have alternatives unless essential. |
| Manual Review Required: WCAG 2.5.8 | Clickable targets must meet minimum size requirements to support users with limited dexterity. | Smaller interactive targets are exempt from the size requirement. |
| Manual Review Required: WCAG 3.1.1 | The default human language of each web page must be programmatically identifiable to support screen readers and other assistive technologies. | Specified language attributes are accurate. |
| Manual Review Required: WCAG 3.1.2 | When parts of a page use a language different from the default, the change must be programmatically identified to support accurate pronunciation and translation. | Language changes within content are correctly identified with language attributes. |
| Manual Review Required: WCAG 3.2.1 | When an element receives focus, it must not cause a major change of context unless expected by the user. | Focusing elements does not cause unexpected changes of context unless expected. |
| Manual Review Required: WCAG 3.2.2 | Changing the setting of a form control must not automatically cause a change of context unless the user is advised before interacting with the control. | Changing form values does not cause unexpected changes of context. |
| Manual Review Required: WCAG 3.2.4 | Components with the same functionality within a set of Web pages are identified consistently. | N/A |
| Manual Review Required: WCAG 3.3.1 | If an input error is detected, the error must be identified and described to the user in text. | Input errors are automatically identified and described. |
| Manual Review Required: WCAG 3.3.2 | Labels or instructions must be provided when user input is required, so users know what is expected. | Form input or controls have accurate instructions or placeholder text. |
| Manual Review Required: WCAG 4.1.2 | User interface components must expose name, role, state, and value programmatically so assistive technologies can interpret and interact with them. | User interface components have accurate and accessible names, roles, and states. |
| Manual Review Required: WCAG 4.1.3 | Status messages must be programmatically conveyed to assistive technologies without requiring user focus. | Status messages are announced to assistive technologies without moving focus. |