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-*] attributes do not match their roles
[aria-*] attributes do not match their roles Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn more.
Failing Elements |
|---|
Search <div role="tab" dojoattachpoint="focusNode" id="mainTab_tablist_browseTab" tabindex="0" aria-selected="true" aria-pressed="true"> |
form#searchForm > div#searchRadioButtons > div.dijit > input#radioData <input name="searchType" type="radio" checked="" class="dijitReset dijitCheckBoxInput" dojoattachpoint="focusNode" dojoattachevent="onclick:_onClick" value="data" id="radioData" tabindex="0" aria-pressed="true"> |
div#dataSearch > div > div.dijit > input#limit <input type="checkbox" checked="" class="dijitReset dijitCheckBoxInput" dojoattachpoint="focusNode" dojoattachevent="onclick:_onClick" value="on" id="limit" tabindex="0" aria-pressed="true"> |
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[role] that require children to contain a specific [role] are missing some or all of those required children. Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more.
Failing Elements |
|---|
Search
Map (0)
Download
Login
? <div class="dijitTabListContainer-top tabStrip-disabled dijitAlignTop dijitLayoutConta…" style="visibility: visible; left: 15px; top: 0px; position: absolute; width: 461p…" role="tablist" id="mainTab_tablist" dir="" lang="" widgetid="mainTab_tablist"> |
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 |
|---|
center.dijitReset > div.dijitSliderBar > div.dijitSliderMoveable > div.dijitSliderImageHandle <div dojoattachpoint="sliderHandle,focusNode" class="dijitSliderImageHandle dijitSliderImageHandleV" dojoattachevent="onmousedown:_onHandleClick" role="slider" valuemin="0" valuemax="23" aria-valuemin="0" aria-valuemax="23" aria-valuenow="3" tabindex="0" style="outline: none;"> |
Names and labels
Image elements do not 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.
Failing Elements |
|---|
div#header > div#logo > a > img <img src="images/logo.png"> |
div.facetTitle > span.browseSubjectTitle > h3 > img.hide <img height="8px" class="hide inline" src="images/down_grey.png" style="display:inline;"> |
div.facetTitle > span.browseSubjectTitle > h3 > img.hide <img height="8px" class="hide inline" src="images/down_grey.png" style="display:inline;"> |
div.facetTitle > span.browseSubjectTitle > h3 > img.hide <img height="8px" class="hide inline" src="images/down_grey.png" style="display:inline;"> |
div.facetTitle > span.facetHelp > a > img.helpIcon <img src="images/feedIcon.png" class="helpIcon"> |
div#map_layers > div#map_layer0 > div > img#map_layer0_tile_3_0_0 <img id="map_layer0_tile_3_0_0" class="layerTile" src="proxy.html?http://server.arcgisonline.com/ArcGIS/rest/services/World_Topo_…" style="width: 256px; height: 256px; visibility: visible; transform: translate3d(-…"> |
div#map_layers > div#map_layer0 > div > img#map_layer0_tile_3_1_0 <img id="map_layer0_tile_3_1_0" class="layerTile" src="proxy.html?http://server.arcgisonline.com/ArcGIS/rest/services/World_Topo_…" style="width: 256px; height: 256px; visibility: visible; transform: translate3d(-…"> |
div#map_layers > div#map_layer0 > div > img#map_layer0_tile_3_2_0 <img id="map_layer0_tile_3_2_0" class="layerTile" src="proxy.html?http://server.arcgisonline.com/ArcGIS/rest/services/World_Topo_…" style="width: 256px; height: 256px; visibility: visible; transform: translate3d(-…"> |
div#map_layers > div#map_layer0 > div > img#map_layer0_tile_3_3_0 <img id="map_layer0_tile_3_3_0" class="layerTile" src="proxy.html?http://server.arcgisonline.com/ArcGIS/rest/services/World_Topo_…" style="width: 256px; height: 256px; visibility: visible; transform: translate3d(-…"> |
div#map_layers > div#map_layer0 > div > img#map_layer0_tile_3_4_0 <img id="map_layer0_tile_3_4_0" class="layerTile" src="proxy.html?http://server.arcgisonline.com/ArcGIS/rest/services/World_Topo_…" style="width: 256px; height: 256px; visibility: visible; transform: translate3d(-…"> |
div#map_layers > div#map_layer0 > div > img#map_layer0_tile_3_0_1 <img id="map_layer0_tile_3_0_1" class="layerTile" src="proxy.html?http://server.arcgisonline.com/ArcGIS/rest/services/World_Topo_…" style="width: 256px; height: 256px; visibility: visible; transform: translate3d(1…"> |
div#map_layers > div#map_layer0 > div > img#map_layer0_tile_3_1_1 <img id="map_layer0_tile_3_1_1" class="layerTile" src="proxy.html?http://server.arcgisonline.com/ArcGIS/rest/services/World_Topo_…" style="width: 256px; height: 256px; visibility: visible; transform: translate3d(1…"> |
div#map_layers > div#map_layer0 > div > img#map_layer0_tile_3_2_1 <img id="map_layer0_tile_3_2_1" class="layerTile" src="proxy.html?http://server.arcgisonline.com/ArcGIS/rest/services/World_Topo_…" style="width: 256px; height: 256px; visibility: visible; transform: translate3d(1…"> |
div#map_layers > div#map_layer0 > div > img#map_layer0_tile_3_3_1 <img id="map_layer0_tile_3_3_1" class="layerTile" src="proxy.html?http://server.arcgisonline.com/ArcGIS/rest/services/World_Topo_…" style="width: 256px; height: 256px; visibility: visible; transform: translate3d(1…"> |
div#map_layers > div#map_layer0 > div > img#map_layer0_tile_3_4_1 <img id="map_layer0_tile_3_4_1" class="layerTile" src="proxy.html?http://server.arcgisonline.com/ArcGIS/rest/services/World_Topo_…" style="width: 256px; height: 256px; visibility: visible; transform: translate3d(1…"> |
div#map_layers > div#map_layer0 > div > img#map_layer0_tile_3_0_2 <img id="map_layer0_tile_3_0_2" class="layerTile" src="proxy.html?http://server.arcgisonline.com/ArcGIS/rest/services/World_Topo_…" style="width: 256px; height: 256px; visibility: visible; transform: translate3d(4…"> |
div#map_layers > div#map_layer0 > div > img#map_layer0_tile_3_1_2 <img id="map_layer0_tile_3_1_2" class="layerTile" src="proxy.html?http://server.arcgisonline.com/ArcGIS/rest/services/World_Topo_…" style="width: 256px; height: 256px; visibility: visible; transform: translate3d(4…"> |
div#map_layers > div#map_layer0 > div > img#map_layer0_tile_3_2_2 <img id="map_layer0_tile_3_2_2" class="layerTile" src="proxy.html?http://server.arcgisonline.com/ArcGIS/rest/services/World_Topo_…" style="width: 256px; height: 256px; visibility: visible; transform: translate3d(4…"> |
div#map_layers > div#map_layer0 > div > img#map_layer0_tile_3_3_2 <img id="map_layer0_tile_3_3_2" class="layerTile" src="proxy.html?http://server.arcgisonline.com/ArcGIS/rest/services/World_Topo_…" style="width: 256px; height: 256px; visibility: visible; transform: translate3d(4…"> |
div#map_layers > div#map_layer0 > div > img#map_layer0_tile_3_4_2 <img id="map_layer0_tile_3_4_2" class="layerTile" src="proxy.html?http://server.arcgisonline.com/ArcGIS/rest/services/World_Topo_…" style="width: 256px; height: 256px; visibility: visible; transform: translate3d(4…"> |
div#map_layers > div#map_layer0 > div > img#map_layer0_tile_3_0_3 <img id="map_layer0_tile_3_0_3" class="layerTile" src="proxy.html?http://server.arcgisonline.com/ArcGIS/rest/services/World_Topo_…" style="width: 256px; height: 256px; visibility: visible; transform: translate3d(6…"> |
div#map_layers > div#map_layer0 > div > img#map_layer0_tile_3_1_3 <img id="map_layer0_tile_3_1_3" class="layerTile" src="proxy.html?http://server.arcgisonline.com/ArcGIS/rest/services/World_Topo_…" style="width: 256px; height: 256px; visibility: visible; transform: translate3d(6…"> |
div#map_layers > div#map_layer0 > div > img#map_layer0_tile_3_2_3 <img id="map_layer0_tile_3_2_3" class="layerTile" src="proxy.html?http://server.arcgisonline.com/ArcGIS/rest/services/World_Topo_…" style="width: 256px; height: 256px; visibility: visible; transform: translate3d(6…"> |
div#map_layers > div#map_layer0 > div > img#map_layer0_tile_3_3_3 <img id="map_layer0_tile_3_3_3" class="layerTile" src="proxy.html?http://server.arcgisonline.com/ArcGIS/rest/services/World_Topo_…" style="width: 256px; height: 256px; visibility: visible; transform: translate3d(6…"> |
div#map_layers > div#map_layer0 > div > img#map_layer0_tile_3_4_3 <img id="map_layer0_tile_3_4_3" class="layerTile" src="proxy.html?http://server.arcgisonline.com/ArcGIS/rest/services/World_Topo_…" style="width: 256px; height: 256px; visibility: visible; transform: translate3d(6…"> |
div#overviewMapDijit-map_layers > div#overviewMapDijit-map_layer8 > div > img#overviewMapDijit-map_layer8_tile_0_0_0 <img id="overviewMapDijit-map_layer8_tile_0_0_0" class="layerTile" src="proxy.html?http://server.arcgisonline.com/ArcGIS/rest/services/World_Topo_…" style="width: 256px; height: 256px; visibility: visible; transform: translate3d(-…"> |
div#overviewMapDijit-map_layers > div#overviewMapDijit-map_layer8 > div > img#overviewMapDijit-map_layer8_tile_0_0_-1 <img id="overviewMapDijit-map_layer8_tile_0_0_-1" class="layerTile" src="proxy.html?http://server.arcgisonline.com/ArcGIS/rest/services/World_Topo_…" style="width: 256px; height: 256px; visibility: visible; transform: translate3d(-…"> |
Form elements do not have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more.
Failing Elements |
|---|
td.q > div.dijitReset > div.dijitReset > input#__q <input dojoattachpoint="query" class="dijitReset dijitInputInner" autocomplete="off" id="__q" name="query" type="text" tabindex="0" value="" autofocus=""> |
div#dataSearch > div > div.dijit > input#limit <input type="checkbox" checked="" class="dijitReset dijitCheckBoxInput" dojoattachpoint="focusNode" dojoattachevent="onclick:_onClick" value="on" id="limit" tabindex="0" aria-pressed="true"> |
Links do not 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.
Failing Elements |
|---|
body.claro > div#header > div#logo > a <a href="#" onclick="geoportal.UI.goHome();return false;"> |
div#rssWrapper > div.facetTitle > span.facetHelp > a <a href="proxy.html?http:__giseditor.scholarsportal.info/search/new.html" target="_blank"> |
Best practices
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is 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.
Failing Elements |
|---|
head > meta <meta name="viewport" content="initial-scale=1,user-scalable=no,maximum-scale=1,width=device-width"> |
Contrast
Background and foreground colors do not have a sufficient contrast ratio.
Low-contrast text is difficult or impossible for many users to read. Learn more.
Failing Elements |
|---|
Search <span dojoattachpoint="containerNode" class="tabLabel"> |
Map (0) <span dojoattachpoint="containerNode" class="tabLabel"> |
Download <span dojoattachpoint="containerNode" class="tabLabel"> |
Login <span dojoattachpoint="containerNode" class="tabLabel"> |
Search <span id="submitBtnLabel" textclass="search" textcontent="submitBtnLabel" class="translatable innerHTML"> |
Back To Results <span id="backResults" textclass="nav" textcontent="backResults" class="translatable innerHTML"> |
Browse by... <div class="translatable innerHTML bigBrowseBy" textclass="facet" textcontent="browseBy"> |
2011-2022 Ontario Council of University Libraries. All rights reserved. <span id="copyrightText" textclass="copyright" textcontent="text" class="translatable innerHTML"> |
Internationalization and localization
<html> element does not have a [lang] attribute
<html> element does not have 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.
Failing Elements |
|---|
html.dj_webkit <html dir="ltr" class="dj_webkit dj_chrome dj_contentbox"> |
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 (18) Show Hide
Passed audits (18)
Show Hide
[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.
[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.
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.
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.
[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.
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.
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.
Heading elements appear 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.
Not applicable (17) Show Hide
Not applicable (17)
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-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.
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.
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.
<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.
<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 [alt] text
<object> elements have [alt] text Screen readers cannot translate non-text content. Adding alt text to `<object>` elements helps screen readers convey meaning to users. 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.