Export as PDF
The exported PDF may not fully meet accessibility standards, which could limit usability for some users.
Scan results for perryparkmd.colorado.gov/accessibility
Accessible
Congratulations! Our scan indicates that your webpage is accessible. We’re thrilled you chose to be inclusive and comply with legislation.
#
Element
Relevant
Successes
Failures
Score
1
Elements that act as buttons but use non-button tags (e.g., span, div, a) should include a role="button" attribute.
Yes
5
0
100
Code snapshots of successful elements
-
1<button type="submit" value="Search" class="button js-form-submit form-submit btn" role="button">Search</button> -
2<button aria-controls="menu-item-c24e510db5edf88be37b785d936a8d9b" aria-expanded="off" class="tbm-submenu-toggle always-show color__brand-dark-blue"> <span class="visually-hidden">Toggle About submenu</span></button> -
3<button aria-controls="menu-item-5330d0d15726bed0c75677a043aebd84" aria-expanded="off" class="tbm-submenu-toggle always-show color__brand-dark-blue"> <span class="visually-hidden">Toggle Metro District submenu</span></button> -
4<button aria-controls="menu-item-b263ec0ff517a8f93ae4e67c03fc9dd3" aria-expanded="off" class="tbm-submenu-toggle always-show color__brand-dark-blue"> <span class="visually-hidden">Toggle Important Info submenu</span></button> -
5<button aria-controls="menu-item-fdd402c1d40355e6abf9bd9762d09a3b" aria-expanded="off" class="tbm-submenu-toggle always-show color__brand-dark-blue"> <span class="visually-hidden">Toggle Contact Us submenu</span></button>
#
Element
Relevant
Successes
Failures
Score
2
Buttons should include text explaining their functionality, and if icons are used as buttons, a screen-reader only text or an "aria-label" attribute should be used for that description.
Yes
5
0
100
Code snapshots of successful elements
-
1<button type="submit" value="Search" class="button js-form-submit form-submit btn" role="button">Search</button> -
2<button aria-controls="menu-item-c24e510db5edf88be37b785d936a8d9b" aria-expanded="off" class="tbm-submenu-toggle always-show color__brand-dark-blue"> <span class="visually-hidden">Toggle About submenu</span></button> -
3<button aria-controls="menu-item-5330d0d15726bed0c75677a043aebd84" aria-expanded="off" class="tbm-submenu-toggle always-show color__brand-dark-blue"> <span class="visually-hidden">Toggle Metro District submenu</span></button> -
4<button aria-controls="menu-item-b263ec0ff517a8f93ae4e67c03fc9dd3" aria-expanded="off" class="tbm-submenu-toggle always-show color__brand-dark-blue"> <span class="visually-hidden">Toggle Important Info submenu</span></button> -
5<button aria-controls="menu-item-fdd402c1d40355e6abf9bd9762d09a3b" aria-expanded="off" class="tbm-submenu-toggle always-show color__brand-dark-blue"> <span class="visually-hidden">Toggle Contact Us submenu</span></button>
#
Element
Relevant
Successes
Failures
Score
3
Links should include text that sets expectations about the page they lead to. If empty links are used as layout wrapping elements, provide a description using screen-reader only text or an "aria-label" attribute.
Yes
22
0
100
Code snapshots of successful elements
-
1<a class="header__logo navbar-btn" href="/" aria-label="Perry Park Metropolitan District" title="Perry Park Metropolitan District" rel="home"> <img class="header__logo--image" src="/sites/perryparkmd/files/Perry%20Park%20Metropolitan%20District%20%28... -
2<a href="/home" class="tbm-link level-1"> Home </a> -
3<a href="/perry-park-0" class="tbm-link level-1"> About </a> -
4<a href="/metro-district" class="tbm-link level-1"> Metro District </a> -
5<a href="/emergency-preparedness" class="tbm-link level-1"> Emergency Preparedness </a> -
6<a href="https://perryparkmd.colorado.gov/sites/perryparkmd/files/documents/HB23-1105%20-%20Metro%20District%20Task%20Force%20Notice.pdf" class="tbm-link level-1"> Important Info </a> -
7<a href="/contact-us-0" class="tbm-link level-1"> Contact Us </a> -
8<a href="/accessibility" class="tbm-link level-1 active-trail"> Accessibility </a> -
9<a href="/">Home</a> -
10<a class="ck-anchor" id="mailto:melonie.c@wsdistricts.co" href="mailto:melonie.c@wsdistricts.co">melonie.c@wsdistricts.co</a>
#
Element
Relevant
Successes
Failures
Score
4
Links that open in a new tab or a new window should either have an "aria-label" attribute or a screen-reader only element explaining to screen-readers that this opens in a new tab.
No
0
0
#
Element
Relevant
Successes
Failures
Score
5
An H1 heading provides information to screen-reader users about the main topic of the page. Each page should have exactly one H1 heading.
Yes
Pass
-
100
Code snapshots of successful elements
-
1<h1> Accessibility </h1>
#
Element
Relevant
Successes
Failures
Score
6
HTML heading elements (h1-h6) should contain text content. If they include images or links, those elements must provide alternative text or screen-reader-only text.
Yes
11
0
100
#
Element
Relevant
Successes
Failures
Score
7
Elements that visually function as headings but are not coded with a heading tag should include a role="heading" attribute or be updated to use the correct heading tag
No
0
0
#
Element
Relevant
Successes
Failures
Score
8
Heading levels should not be skipped and must follow a consistent hierarchy. For example, you should not use h2 and h4 headings without including an h3 in between.
Yes
Pass
-
100
#
Element
Relevant
Successes
Failures
Score
9
Interactive elements such as links, buttons and form fields should all be navigable using the keyboard by either using a focusable element (a, button, input, etc.) or including the "tabindex" attribute that equals to "0".
Yes
Pass
-
100
#
Element
Relevant
Successes
Failures
Score
10
Interactive elements that can be navigated using the keyboard should be surrounded by a visual outline whenever they are focused.
Yes
Pass
-
100
#
Element
Relevant
Successes
Failures
Score
11
Active popups should include aria-modal="true" and role="dialog" attributes to help screen-reader users navigate them effectively.
No
0
0
#
Element
Relevant
Successes
Failures
Score
12
Each page should include hidden skip links that allow users (via keyboard or screen reader) to bypass certain blocks and navigate directly to main landmarks like the main content, menu, or footer.
Yes
Pass
-
100
Code snapshots of successful elements
-
1<a href="#main-content" class="visually-hidden focusable skip-link"> Skip to main content </a>
#
Element
Relevant
Successes
Failures
Score
13
Elements hidden using CSS (e.g., opacity, height, text-indent, off-canvas) should include an "aria-hidden" attribute set to "true" when hidden and dynamically updated to "false" when they become visible.
Yes
Pass
-
100
#
Element
Relevant
Successes
Failures
Score
14
Elements hidden using CSS (e.g., opacity, height, text-indent, off-canvas) should have a tabindex attribute set to less than 0 and be dynamically updated to 0 when they become visible.
No
0
0
#
Element
Relevant
Successes
Failures
Score
15
Menus should be built using the HTML5 "nav" element or include a "role" attribute set to "menu" or "navigation" to indicate a navigation landmark for screen readers.
No
0
0
#
Element
Relevant
Successes
Failures
Score
16
Menu items that have a dropdown should include an aria-haspopup="true" attribute.
No
0
0
#
Element
Relevant
Successes
Failures
Score
17
Menu items that have a dropdown should include an "aria-expanded" attribute set to "false" by default, which changes to "true" when the dropdown is opened, and back to "false" when closed.
No
0
0
#
Element
Relevant
Successes
Failures
Score
18
Images should have an alternative text description that describes both the objects and the embedded text that the image contains, using the "alt" attribute.
Yes
2
0
100
Code snapshots of successful elements
-
1<img class="header__logo--image" src="/sites/perryparkmd/files/Perry%20Park%20Metropolitan%20District%20%281%29.png" alt="Perry Park Metropolitan District"> -
2<img src="/sites/perryparkmd/files/inline-images/WSDM_Managers%20Logo-Stacked%20Color.jpg" data-entity-uuid="f3fbb108-809a-4eab-8526-de8511cf0ffc" data-entity-type="file" alt="WSDM Managers Logo" width="178" height="94" class="align-center">
#
Element
Relevant
Successes
Failures
Score
19
Background images that are not just for decoration purposes should have the same treatment as standard images. They should include a role="img" attribute and an alternative text description using an "aria-label" attribute.
No
0
0
#
Element
Relevant
Successes
Failures
Score
20
Font icons, SVGs, or images used as spacers, decorations, or when their purpose is already described by other content, should include a role="presentation" or role="none" attribute.
No
0
0
#
Element
Relevant
Successes
Failures
Score
21
Figure elements used to display images should have a role="none" attribute, and the image itself should provide a description using the "alt" attribute.
No
0
0
#
Element
Relevant
Successes
Failures
Score
22
Each "area" element within a map tag should have an "alt" attribute that provides an alternative text description, similar to standard images.
No
0
0
#
Element
Relevant
Successes
Failures
Score
23
Small or hidden tracking pixel images (used for analytics or marketing) should include a role="none" or role="presentation" attribute to exclude them from screen-readers.
No
0
0
#
Element
Relevant
Successes
Failures
Score
24
Form fields should include either an "aria-label" attribute or an associated "label" element to describe the field's purpose (e.g., email, phone, name).
Yes
Pass
-
100
Code snapshots of successful elements
-
1<input title="Site Search" data-drupal-selector="edit-keys" class="form-search form-control" placeholder="Search" type="search" id="edit-keys" name="keys" value="" size="40" maxlength="128" data-toggle="tooltip" style="background: rgb(255, 255, 255);...
#
Element
Relevant
Successes
Failures
Score
25
Form elements must have unique IDs to ensure that their corresponding labels provide accurate information.
No
0
0
#
Element
Relevant
Successes
Failures
Score
26
Required form fields should include aria-required="true" to inform screen-reader users of the field's validation.
No
0
0
#
Element
Relevant
Successes
Failures
Score
27
aria-describedby and aria-labelledby attributes should reference the ID of an element that either has a text description or an "aria-label" attribute.
No
0
0
#
Element
Relevant
Successes
Failures
Score
28
Search forms should include a role="search" attribute or be wrapped in an element with this role to indicate a search landmark for screen-readers.
Yes
Pass
-
100
Code snapshots of successful elements
-
1<form action="/search/search" method="get" id="search-block-form" accept-charset="UTF-8"> <div class="form-item js-form-item form-type-search js-form-type-search form-item-keys js-form-item-keys form-no-label form-group"> <label for="edit-keys" class...
#
Element
Relevant
Successes
Failures
Score
29
All forms should include a submission button built as an input type="submit" or a "button" element, or have a role="button" attribute. The button can be hidden if the form supports submission via the Enter key.
Yes
Pass
-
100
Code snapshots of successful elements
-
1<form action="/search/search" method="get" id="search-block-form" accept-charset="UTF-8"> <div class="form-item js-form-item form-type-search js-form-type-search form-item-keys js-form-item-keys form-no-label form-group"> <label for="edit-keys" class...
#
Element
Relevant
Successes
Failures
Score
30
The validity status of each form element must be represented using the "aria-invalid" attribute with "true" or "false" values, and should update dynamically as the status changes.
No
0
0
#
Element
Relevant
Successes
Failures
Score
31
The title tag in the head section should be present and describe the current webpage accurately. This title appears in the browser tab, search engine results, and helps screen-reader users understand the page's content.
Yes
Pass
-
100
#
Element
Relevant
Successes
Failures
Score
32
The HTML tag should include a "lang" attribute representing the main language of the webpage to help screen-readers provide accurate pronunciation.
Yes
Pass
-
100
#
Element
Relevant
Successes
Failures
Score
33
The viewport meta tag should enable vision-impaired users to pinch-zoom to at least twice the standard size by including user-scalable="yes" and maximum-scale=2 (or higher) in the content attribute.
Yes
Pass
-
100
Code snapshots of successful elements
-
1<meta name="viewport" content="width=device-width, initial-scale=1.0">
#
Element
Relevant
Successes
Failures
Score
34
Landmarks like main content and footer should use their corresponding HTML5 elements (<main>, <footer>) or include an "aria-label" and "role" attribute (e.g., role="main" or role="contentinfo"). Landmarks like search and navigation are covered elsewhere.
Yes
2
2
50
Code snapshots of successful elements
-
1<footer> <div class="footer__content-footer color__grey-sand"> <div class="container"> <div class="region region-footer"> <section id="block-blockmainfooter" class="block block-block-content block-block-content8e0f4fc5-1848-4e37-892d-08efb5472307 cle...
Code snapshots of failed elements
-
1<div class="site-wrapper"> <a href="#main-content" class="visually-hidden focusable skip-link"> Skip to main content </a> <div class="dialog-off-canvas-main-canvas" data-off-canvas-main-canvas=""> <header> <div class="region region-co-branding"> <sec... -
2<main tabindex="-1" class="main-container container js-quickedit-main-content"> <div class="row"> <nav aria-label="Breadcrumb"> <ol class="breadcrumb"> <li> <a href="/">Home</a> </li> <li class="active"> <span aria-current="page">Accessibility</span>...
#
Element
Relevant
Successes
Failures
Score
35
Font sizes should be at least 11px to ensure readability across most font families. This requirement should also be verified when using dynamic units like REM or percentages.
Yes
54
1
98
Code snapshots of failed elements
-
1<button type="submit" value="Search" class="button js-form-submit form-submit btn" role="button">Search</button>
#
Element
Relevant
Successes
Failures
Score
36
Letter spacing should not be set below -1px to maintain readability across most font families. This should also be verified when using dynamic units like REM or percentages.
Yes
55
0
100
#
Element
Relevant
Successes
Failures
Score
37
Text elements should meet a minimum contrast ratio of 4.5:1 between the foreground (text color) and the background.
Yes
49
5
91
Code snapshots of successful elements
-
1<p>WSDM Managers moved from 614 N. Tejon St. to 3204 N. Academy Blvd. Suite 100, Colorado Springs, CO 80917</p> -
2<a href="/home" class="tbm-link level-1"> Home </a> -
3<a href="/perry-park-0" class="tbm-link level-1"> About </a> -
4<a href="/metro-district" class="tbm-link level-1"> Metro District </a> -
5<a href="/emergency-preparedness" class="tbm-link level-1"> Emergency Preparedness </a> -
6<a href="https://perryparkmd.colorado.gov/sites/perryparkmd/files/documents/HB23-1105%20-%20Metro%20District%20Task%20Force%20Notice.pdf" class="tbm-link level-1"> Important Info </a> -
7<a href="/contact-us-0" class="tbm-link level-1"> Contact Us </a> -
8<a href="/accessibility" class="tbm-link level-1 active-trail"> Accessibility </a> -
9<a href="/">Home</a> -
10<span aria-current="page">Accessibility</span>
Code snapshots of failed elements
-
1<span style="font-family:'Trebuchet MS';">Beth Diana, WSDM Managers</span> -
2<span style="font-family:'Trebuchet MS';">3204 N. Academy Blvd. Suite 100, Colorado Springs, CO 80917</span> -
3<span style="font-family:'Trebuchet MS';">Phone: 719-447-1777 x110</span> -
4<span style="font-family:'Trebuchet MS';">Email: </span> -
5<span style="font-family:'Trebuchet MS';">beth.d@wsdistricts.co</span>
#
Element
Relevant
Successes
Failures
Score
38
Carousels should include an "aria-label" attribute (e.g., carousel or slider) to indicate their functionality. They should also be marked as a landmark for screen-readers with a role="contentinfo" attribute.
No
0
0
#
Element
Relevant
Successes
Failures
Score
39
Control elements such as next and previous icons should include an "aria-label" attribute or a screen-reader only text that explains the functionality to screen-readers.
No
0
0
#
Element
Relevant
Successes
Failures
Score
40
A common accessibility mistake is treating carousels as live regions using the "aria-live attribute" with "polite" or "assertive" values. This can cause screen readers to cut off or skip important announcements.
No
0
0
#
Element
Relevant
Successes
Failures
Score
41
Carousel pagination items (usually used as small dots at the bottom of the carousel) should indicate their functionality and slide number they control using an "aria-label" and a screen-reader only text.
No
0
0
#
Element
Relevant
Successes
Failures
Score
42
Tables used for layout purposes should include a role="presentation" attribute to indicate to screen-readers that it is not a data table.
No
0
0
#
Element
Relevant
Successes
Failures
Score
43
If nested tables are used (a table element within a table cell), set the nested tables "role" attribute to "presentation".
No
0
0
#
Element
Relevant
Successes
Failures
Score
44
Tables without a thead row containing th elements should use the role="rowheader" attribute on td elements in the tr that visually represent the table headings.
No
0
0
#
Element
Relevant
Successes
Failures
Score
45
Visually deleted texts (e.g., a previous price on sale items) should include an "aria-label" attribute or a screen-reader only text to indicate that it is deleted.
No
0
0
#
Element
Relevant
Successes
Failures
Score
46
The main element of breadcrumbs should include a role="navigation" attribute and an "aria-label" to describe its functionality.
Yes
Pass
-
100
Code snapshots of successful elements
-
1<ol class="breadcrumb"> <li> <a href="/">Home</a> </li> <li class="active"> <span aria-current="page">Accessibility</span> </li> </ol>
#
Element
Relevant
Successes
Failures
Score
47
Ratings/scores that are represented visually using stars, meters or other indicators should either have an "aria-label" attribute or a screen-reader only texts conveying the score/rate.
No
0
0
#
Element
Relevant
Successes
Failures
Score
48
An accessibility interface allows visually-impaired users to adjust UI elements like font size, colors, and spacing to suit their needs. While not a compliance requirement, it can help improve accessibility compliance.
No
0
0
#
Element
Relevant
Successes
Failures
Score
49
Iframe elements should include a "title" or "aria-label" attribute that explains their purpose, functionality, or destination. If irrelevant, they should be hidden from screen readers.
No
0
0