glendaleca.gov digital experience monitor
- Managed by: City of Glendale, CA
- Updated: 5/2/2026 · Request update
- Scan: Homepage only · Get full site scan
| Standard | Status |
|---|---|
|
[aria-*] attributes match their roles Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. [Learn how to match ARIA attributes to their roles](https://dequeuniversity.c |
Active |
|
ARIA attributes are used as specified for the element's role Some ARIA attributes are only allowed on an element under certain conditions. |
Active |
|
Deprecated ARIA roles were not used Deprecated ARIA roles may not be processed correctly by assistive technology. |
Active |
|
[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 how `aria-hidden` affects the document body](https://dequeuniversity. |
Active |
|
[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 how `aria-hidden` |
Missing |
|
Elements use only permitted ARIA attributes Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. |
Active |
|
[role]s have all required [aria-*] attributes Some ARIA roles have required attributes that describe the state of the element to screen readers. |
Active |
|
[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. |
Missing |
|
[role] values are valid ARIA roles must have valid values in order to perform their intended accessibility functions. |
Active |
|
[aria-*] attributes have valid values Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. |
Active |
|
[aria-*] attributes are valid and not misspelled Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid names. |
Active |
|
Background and foreground colors have a sufficient contrast ratio Low-contrast text is difficult or impossible for many users to read. [Learn how to provide sufficient color contrast](https://dequeuniversity.com/rules/axe/4.10/color-contrast). |
Missing |
|
Document has a <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. |
Active |
|
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. |
Active |
|
<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 |
Active |
|
<html> element has a valid value for its [lang] attribute Specifying a valid [BCP 47 language](https://www.w3.org/International/questions/qa-choosing-language-tags#question) helps screen readers announce text properly. [Learn how to use the `lang` attribute] |
Active |
|
Image elements have [alt] attributes Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. |
Active |
|
Form elements have associated labels Labels ensure that form controls are announced properly by assistive technologies, like screen readers. |
Active |
|
Links are distinguishable without relying on color Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. [Learn how to make links distinguishable](https:// |
Active |
|
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 how to make links accessible |
Active |
|
Lists contain only <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. |
Missing |
|
List items (<li>) are contained within <ul>, <ol> or <menu> parent elements Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. |
Active |
|
[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. |
Active |
|
Select elements have associated label elements Form elements without effective labels can create frustrating experiences for screen reader users. |
Missing |
|
Skip links are focusable Including a skip link can help users skip to the main content to save time. |
Missing |
|
Touch targets have sufficient size and spacing Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. |
Missing |
|
Cells in a <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 r |
Active |
|
Document has a main landmark One main landmark helps screen reader users navigate a web page. |
Missing |
|
Elements with visible text labels have matching accessible names Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. |
Active |
|
Tables use <caption> instead of cells with the [colspan] attribute to indicate a caption Screen readers have features to make navigating tables easier. Ensuring that tables use the actual caption element instead of cells with the `[colspan]` attribute may improve the experience for screen |
Active |
|
<td> elements in a large <table> have one or more table headers Screen readers have features to make navigating tables easier. Ensuring that `<td>` elements in a large table (3 or more cells in width and height) have an associated table header may improve the expe |
Active |
|
Image aspect ratio Ratio of image width to height. |
Active |
|
Valid doctype Tells browser how to read code. |
Active |
|
Character encoding Character set for text encoding. |
Active |
| Standard | Status |
|---|---|
|
Canonical Use preferred page URLs to avoid duplication. |
Active |
|
Link text Links have descriptive text. |
Missing |
|
hreflang Specifies language and region for webpages. |
Active |
|
Crawlable Site is available for indexing by well-behaved agents. |
Active |
|
Content available in document Page main content is available in initial document. |
Active |
| Standard | Status |
|---|---|
|
Content security policy (CSP) The site restricts what can be loaded. |
Active |
|
HTTP Strict Transport Security (HSTS) Site upgrades to a secure connection. |
Active |
|
Errors in the console Tracks mistakes in code for debugging. |
Active |
|
Clickjacking mitigation Stops fake clicks on hidden content. |
Active |
|
Paste preventing inputs Page doesn't allow copy-paste into inputs. |
Active |
|
Hypertext Transfer Protocol Secure (HTTPS) Privacy and integrity protection. |
Active |
|
X-Content-Type-Options The site prevents mime type sniffing. |
Active |
|
Sponsored top-level domain (sTLD) Sponsored top-level domain (.gov / .edu / .mil). |
Active |
| Standard | Status |
|---|---|
|
Page title Describes webpage content in a few words. |
Active |
|
Page description Describes webpage content in a few words. |
Active |
|
Viewport meta tag Makes websites fit all screen sizes. |
Active |
|
Open Graph site name Website title for social sharing. |
Missing |
|
Open Graph type Content category for social media. |
Missing |
|
Open Graph title Page title for social sharing. |
Active |
|
Open Graph description Short description of your webpage content. |
Active |
|
Open Graph URL Canonical link for social sharing. |
Missing |
|
Open Graph image Preview image for social sharing. |
Missing |
|
Open Graph image alt Image description for accessibility |
Missing |
|
Readability How easy text is to read. |
Active |
|
First Contentful Paint (FCP) The page begins to display within 1.8 seconds. |
Active |
|
Largest Contentful Paint (LCP) Major content loads in 2.5 seconds. |
Active |
|
Time to First Byte (TTFB) Code received in 0.8 seconds. |
Active |
|
Cumulative Layout Shift (CLS) Measures unexpected webpage content shifts. |
Active |
|
Interaction to Next Paint (INP) Page responds in under 0.2 seconds. |
Active |
|
www resolution One domain works with www and non-www. |
Active |