These checks highlight opportunities to improve the accessibility of your web app. Only a subset of accessibility issues can be automatically detected so manual testing is also encouraged.
ARIA
ARIA input fields do not have accessible names
When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more.
Failing Elements |
|---|
There's a lot that we can say about our bread but frankly we think you need to … <div aria-describedby="placeholder-uv1q" aria-multiline="true" class="notranslate public-DraftEditor-content" contenteditable="true" role="textbox" spellcheck="true" style="outline: none; user-select: text; white-space: pre-wrap;"> |
Bread is a staple food prepared from a dough of flour and water, usually by bak… <div aria-describedby="placeholder-41m7i" aria-multiline="true" class="notranslate public-DraftEditor-content" contenteditable="true" role="textbox" spellcheck="true" style="outline: none; user-select: text; white-space: pre-wrap;"> |
Navigation
Heading elements are not in a sequentially-descending order
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more.
Failing Elements |
|---|
div.c-sf-container__block-container > div.c-sf-block > div.c-sf-block__header > h3.c-sf-block__header__title <h3 data-block-title="" class="c-sf-block__header__title"> |
Additional items to manually check (10) Show Hide
Additional items to manually check (10)
Show Hide
The page has a logical tab order
Tabbing through the page follows the visual layout. Users cannot focus elements that are offscreen. Learn more.
Interactive controls are keyboard focusable
Custom interactive controls are keyboard focusable and display a focus indicator. Learn more.
Interactive elements indicate their purpose and state
Interactive elements, such as links and buttons, should indicate their state and be distinguishable from non-interactive elements. Learn more.
The user's focus is directed to new content added to the page
If new content, such as a dialog, is added to the page, the user's focus is directed to it. Learn more.
User focus is not accidentally trapped in a region
A user can tab into and out of any control or region without accidentally trapping their focus. Learn more.
Custom controls have associated labels
Custom interactive controls have associated labels, provided by aria-label or aria-labelledby. Learn more.
Custom controls have ARIA roles
Custom interactive controls have appropriate ARIA roles. Learn more.
Visual order on the page follows DOM order
DOM order matches the visual order, improving navigation for assistive technology. Learn more.
Offscreen content is hidden from assistive technology
Offscreen content is hidden with display: none or aria-hidden=true. Learn more.
HTML5 landmark elements are used to improve navigation
Landmark elements (<main>, <nav>, etc.) are used to improve the keyboard navigation of the page for assistive technology. Learn more.
Passed audits (23) Show Hide
Passed audits (23)
Show Hide
[aria-*] attributes match their roles
[aria-*] attributes match their roles Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn more.
[aria-hidden="true"] is not present on the document <body>
[aria-hidden="true"] is not present on the document <body> Assistive technologies, like screen readers, work inconsistently when `aria-hidden="true"` is set on the document `<body>`. Learn more.
[role]s have all required [aria-*] attributes
[role]s have all required [aria-*] attributes Some ARIA roles have required attributes that describe the state of the element to screen readers. Learn more.
Elements with an ARIA [role] that require children to contain a specific [role] have all required children.
[role] that require children to contain a specific [role] have all required children. Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more.
[role]s are contained by their required parent element
[role]s are contained by their required parent element Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more.
[role] values are valid
[role] values are valid ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more.
[aria-*] attributes have valid values
[aria-*] attributes have valid values Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more.
[aria-*] attributes are valid and not misspelled
[aria-*] attributes are valid and not misspelled Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. Learn more.
Buttons have an accessible name
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn more.
ARIA IDs are unique
The value of an ARIA ID must be unique to prevent other instances from being overlooked by assistive technologies. Learn more.
Image elements have [alt] attributes
[alt] attributes Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more.
Form elements have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more.
[user-scalable="no"] is not used in the <meta name="viewport"> element and the [maximum-scale] attribute is not less than 5.
[user-scalable="no"] is not used in the <meta name="viewport"> element and the [maximum-scale] attribute is not less than 5. Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more.
[aria-hidden="true"] elements do not contain focusable descendents
[aria-hidden="true"] elements do not contain focusable descendents Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn more.
The page contains a heading, skip link, or landmark region
Adding ways to bypass repetitive content lets keyboard users navigate the page more efficiently. Learn more.
Background and foreground colors have a sufficient contrast ratio
Low-contrast text is difficult or impossible for many users to read. Learn more.
Document has a <title> element
<title> element The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more.
<html> element has a [lang] attribute
<html> element has a [lang] attribute If a page doesn't specify a lang attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more.
<html> element has a valid value for its [lang] attribute
<html> element has a valid value for its [lang] attribute Specifying a valid BCP 47 language helps screen readers announce text properly. Learn more.
Links have a discernible name
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn more.
Lists contain only <li> elements and script supporting elements (<script> and <template>).
<li> elements and script supporting elements (<script> and <template>). Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more.
List items (<li>) are contained within <ul> or <ol> parent elements
<li>) are contained within <ul> or <ol> parent elements Screen readers require list items (`<li>`) to be contained within a parent `<ul>` or `<ol>` to be announced properly. Learn more.
No element has a [tabindex] value greater than 0
[tabindex] value greater than 0 A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more.
Not applicable (19) Show Hide
Not applicable (19)
Show Hide
[accesskey] values are unique
[accesskey] values are unique Access keys let users quickly focus a part of the page. For proper navigation, each access key must be unique. Learn more.
button, link, and menuitem elements have accessible names
button, link, and menuitem elements have accessible names When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more.
ARIA meter elements have accessible names
meter elements have accessible names When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more.
ARIA progressbar elements have accessible names
progressbar elements have accessible names When a `progressbar` element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more.
ARIA toggle fields have accessible names
When a toggle field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more.
ARIA tooltip elements have accessible names
tooltip elements have accessible names When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more.
ARIA treeitem elements have accessible names
treeitem elements have accessible names When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more.
<dl>'s contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
<dl>'s contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements. When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn more.
Definition list items are wrapped in <dl> elements
<dl> elements Definition list items (`<dt>` and `<dd>`) must be wrapped in a parent `<dl>` element to ensure that screen readers can properly announce them. Learn more.
[id] attributes on active, focusable elements are unique
[id] attributes on active, focusable elements are unique All focusable elements must have a unique `id` to ensure that they're visible to assistive technologies. Learn more.
No form fields have multiple labels
Form fields with multiple labels can be confusingly announced by assistive technologies like screen readers which use either the first, the last, or all of the labels. Learn more.
<frame> or <iframe> elements have a title
<frame> or <iframe> elements have a title Screen reader users rely on frame titles to describe the contents of frames. Learn more.
<input type="image"> elements have [alt] text
<input type="image"> elements have [alt] text When an image is being used as an `<input>` button, providing alternative text can help screen reader users understand the purpose of the button. Learn more.
The document does not use <meta http-equiv="refresh">
<meta http-equiv="refresh"> Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may create a frustrating or confusing experience. Learn more.
<object> elements have alternate text
<object> elements have alternate text Screen readers cannot translate non-text content. Adding alternate text to `<object>` elements helps screen readers convey meaning to users. Learn more.
Cells in a <table> element that use the [headers] attribute refer to table cells within the same table.
<table> element that use the [headers] attribute refer to table cells within the same table. Screen readers have features to make navigating tables easier. Ensuring `<td>` cells using the `[headers]` attribute only refer to other cells in the same table may improve the experience for screen reader users. Learn more.
<th> elements and elements with [role="columnheader"/"rowheader"] have data cells they describe.
<th> elements and elements with [role="columnheader"/"rowheader"] have data cells they describe. Screen readers have features to make navigating tables easier. Ensuring table headers always refer to some set of cells may improve the experience for screen reader users. Learn more.
[lang] attributes have a valid value
[lang] attributes have a valid value Specifying a valid BCP 47 language on elements helps ensure that text is pronounced correctly by a screen reader. Learn more.
<video> elements contain a <track> element with [kind="captions"]
<video> elements contain a <track> element with [kind="captions"] When a video provides a caption it is easier for deaf and hearing impaired users to access its information. Learn more.
Trust and Safety
Does not use HTTPS 1 insecure request found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more.
Insecure URL | Request Resolution |
|---|---|
/avatar/e64c7d8…?s=100&d=mm (www.gravatar.com) | Allowed |
Includes front-end JavaScript libraries with known security vulnerabilities 3 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers. Learn more.
Library Version | Vulnerability Count | Highest Severity |
|---|---|---|
| jQuery UI@1.12.1 | 3 | High |
Ensure CSP is effective against XSS attacks
A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn more
Description | Directive | Severity |
|---|---|---|
No CSP found in enforcement mode | High |
User Experience
Serves images with low resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn more.
URL | Displayed size | Actual size | Expected size | |
|---|---|---|---|---|
Breads 1 <img alt="Breads 1" class="show-transparency" height="126" src="/media/images/breads1.max-165x165_1yHhjrV.jpg" width="165"> | …images/breads1.max-165x1….jpg (localhost) | 130 x 99 | 165 x 126 | 260 x 198 |
General
Browser errors were logged to the console
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more
Source | Description |
|---|---|
…cjs/react-dom.development.js:1297:13 | Error: <path> attribute d: Expected moveto path command ('M' or 'm'), "cut". |
…cjs/react-dom.development.js:1297:13 | Error: <path> attribute d: Expected moveto path command ('M' or 'm'), "cut". |
…dist/index.js:133:12 | Fix any of the following: aria-label attribute does not exist or is empty aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty Element has no title attribute or the title attribute is empty |
…dist/index.js:133:12 | Fix any of the following: aria-label attribute does not exist or is empty aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty Element has no title attribute or the title attribute is empty |
…dist/index.js:133:12 | Fix any of the following: Element does not have text that is visible to screen readers |
…dist/index.js:133:12 | Fix any of the following: Element does not have text that is visible to screen readers |
…dist/index.js:133:12 | Fix any of the following: Element does not have text that is visible to screen readers |
…dist/index.js:133:12 | Fix any of the following: Heading order invalid |
…dist/index.js:133:12 | Fix any of the following: The complementary landmark is contained in another landmark. |
…cjs/react-dom.development.js:88:29 | Warning: A component is changing an uncontrolled input of type %s to be controlled. Input elements should not switch from uncontrolled to controlled (or vice versa). Decide between using a controlled or uncontrolled input element for the lifetime of the component. More info: https://fb.me/react-controlled-components%s text
in input (created by ComboBox)
in div (created by ComboBox)
in div (created by ComboBox)
in ComboBox (created by BlockToolbar)
in Tippy (created by ForwardRef(TippyWrapper))
in ForwardRef(TippyWrapper) (created by BlockToolbar)
in div (created by BlockToolbar)
in BlockToolbar (created by topToolbar)
in topToolbar (created by DraftailEditor)
in div (created by DraftailEditor)
in DraftailEditor (created by CommentableEditor)
in CommentableEditor (created by DynamicOptionsEditorWrapper)
in Provider (created by DynamicOptionsEditorWrapper)
in DynamicOptionsEditorWrapper
in EditorFallback |
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more.
Name | Version |
|---|---|
Bootstrap | >= 3.0.0 & <= 3.1.1 |
jQuery | 3.6.0 |
jQuery UI | 1.12.1 |
React | 16.14.0 |
Missing source maps for large first-party JavaScript
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more.
URL | Map URL |
|---|---|
…js/wagtailadmin.js?v=2f6c1edb (localhost) | |
Large JavaScript file is missing a source map | |
…js/vendor.js?v=2f6c1edb (localhost) | |
Large JavaScript file is missing a source map | |
…js/draftail.js?v=2f6c1edb (localhost) | |
Large JavaScript file is missing a source map |
Passed audits (8) Show Hide
Passed audits (8)
Show Hide
Avoids requesting the geolocation permission on page load
Users are mistrustful of or confused by sites that request their location without context. Consider tying the request to a user action instead. Learn more.
Avoids requesting the notification permission on page load
Users are mistrustful of or confused by sites that request to send notifications without context. Consider tying the request to user gestures instead. Learn more.
Allows users to paste into password fields
Preventing password pasting undermines good security policy. Learn more.
Displays images with correct aspect ratio
Image display dimensions should match natural aspect ratio. Learn more.
Page has the HTML doctype
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more.
Properly defines charset
A character encoding declaration is required. It can be done with a `<meta>` tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header. Learn more.
Avoids deprecated APIs
Deprecated APIs will eventually be removed from the browser. Learn more.
No issues in the Issues panel in Chrome Devtools
Issues panel in Chrome Devtools Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Not applicable (1) Show Hide
Not applicable (1)
Show Hide
Fonts with font-display: optional are preloaded
font-display: optional are preloaded Preload `optional` fonts so first-time visitors may use them. Learn more
These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more.
Content Best Practices
Document does not have a meta descriptionDescription text is empty.
Description text is empty.
Meta descriptions may be included in search results to concisely summarize page content. Learn more.
Crawling and Indexing
Page is blocked from indexing
Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more.
Blocking Directive Source |
|---|
head > meta <meta name="robots" content="noindex" /> |
Additional items to manually check (1) Show Hide
Additional items to manually check (1)
Show Hide
Structured data is valid
Run the Structured Data Testing Tool and the Structured Data Linter to validate structured data. Learn more.
Passed audits (10) Show Hide
Passed audits (10)
Show Hide
Has a <meta name="viewport"> tag with width or initial-scale
<meta name="viewport"> tag with width or initial-scale A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more.
Document has a <title> element
<title> element The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more.
Page has successful HTTP status code
Pages with unsuccessful HTTP status codes may not be indexed properly. Learn more.
Links have descriptive text
Descriptive link text helps search engines understand your content. Learn more.
Links are crawlable
Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn More
Image elements have [alt] attributes
[alt] attributes Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more.
Document has a valid hreflang
hreflang hreflang links tell search engines what version of a page they should list in search results for a given language or region. Learn more.
Document uses legible font sizes 95.94% legible text
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. Learn more.
Source | Selector | % of Page Text | Font Size |
|---|---|---|---|
…css/core.css?v=2f6c1edb:11:73747 (localhost) | .error-message, .help | 4.03% | 11.56px |
…css/core.css?v=2f6c1edb:11:155525 (localhost) | .w-text-\[0\.6875rem\] | 0.02% | 11px |
…css/core.css?v=2f6c1edb:11:155567 (localhost) | .w-text-\[0\.5625rem\] | 0.00% | 9px |
Legible text | 95.94% | ≥ 12px |
Document avoids plugins
Search engines can't index plugin content, and many devices restrict plugins or don't support them. Learn more.
Tap targets are sized appropriately 100% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements. Learn more.
Not applicable (2) Show Hide
Not applicable (2)
Show Hide
robots.txt is valid
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more.
Document has a valid rel=canonical
rel=canonical Canonical links suggest which URL to show in search results. Learn more.