Accessibility checks

Scanned at: Dec 30, 2024, 5:47 PM

Report for: Agency Dominion Inc.
Scanned at: Dec 30, 2024, 5:47 PM
Report created: Jan 6, 2025, 8:53 AM

Compliance status

100%

100%

Pages scanned:

5

Errors

Guideline
AAll input elements with a type attribute value of "image" have an alt attribute.
Content Authoring
Visual Design		 1.1.1 0
0
pages
AAll area elements have an alt attribute.
UX Design
Front-end Development		 1.1.1 0
0
pages
ASVG element with explicit role has non-empty accessible name
Content Authoring
Front-end Development		 1.1.1 0
0
pages
AImage has non-empty accessible name
Content Authoring
Front-end Development		 1.1.1 0
0
pages
Aobject element rendering non-text content has non-empty accessible name
Content Authoring
UX Design		 1.1.1 0
0
pages
AImage button has non-empty accessible name
Front-end Development 1.1.1 0
0
pages
AAll data table summaries contain text.
Content Authoring
UX Design		 1.3.1 0
0
pages
AAll layout tables have an empty summary attribute or no summary attribute.
Front-end Development
UX Design		 1.3.1 0
0
pages
AAll layout tables do not contain caption elements.
Front-end Development
UX Design		 1.3.1 0
0
pages
ATable summaries do not duplicate the table captions.
Front-end Development 1.3.1 0
0
pages
AData tables that contain more than one row/column of headers use the id and headers attributes to identify cells.
Front-end Development
UX Design		 1.3.1 0
0
pages
AARIA attribute is defined in WAI-ARIA
Front-end Development 1.3.1 0
0
pages
AARIA state or property has valid value
Front-end Development 1.3.1 0
0
pages
AARIA required context role
Front-end Development 1.3.1 0
0
pages
AARIA required ID references exist
Front-end Development 1.3.1 0
0
pages
AHeaders attribute specified on a cell refers to cells in the same table element
Front-end Development 1.3.1 0
0
pages
AARIA required owned elements
Front-end Development 1.3.1 0
0
pages
ATable header cell has assigned cells
Front-end Development
UX Design		 1.3.1 0
0
pages
AHeading has non-empty accessible name
Content Authoring
Front-end Development		 1.3.1 0
0
pages
ALinks inside text are sufficiently distinguishable
UX Design
Visual Design
Front-end Development		 1.4.1 0
0
pages
AScrollable content can be reached with sequential focus navigation
Front-end Development 2.1.1 0
0
pages
AIframe with interactive elements is not excluded from tab-order
Front-end Development 2.1.1 0
0
pages
AMeta element has no refresh delay
Front-end Development 2.2.1 0
0
pages
Ablink element is not used.
Front-end Development 2.2.2 0
0
pages
Amarquee element is not used.
Front-end Development 2.2.2 0
0
pages
AAuto-redirect must not be used.
Front-end Development 2.2.2 0
0
pages
AAll frames have a title attribute.
Content Authoring
UX Design		 2.4.1 0
0
pages
AHTML page has non-empty title
Content Authoring
Front-end Development		 2.4.2 0
0
pages
AEach source anchor contains text.
UX Design
Content Authoring		 2.4.4 0
0
pages
ADocument has required lang attribute(s)
Front-end Development 3.1.1 0
0
pages
ADocument has a valid language code
Front-end Development 3.1.1 0
0
pages
AReading order direction is marked using the html element's dir attribute if the document's primary language is read right to left.
Front-end Development 3.1.1 0
0
pages
AEach input element has only one associated label.
Front-end Development 3.3.2 0
0
pages
AEach label associated with an input element contains text.
Front-end Development 3.3.2 0
0
pages
Aid attributes must be unique.
Front-end Development 4.1.1 0
0
pages
AElement with role attribute has required states and properties
Front-end Development 4.1.2 0
0
pages
AForm field has non-empty accessible name
Front-end Development 4.1.2 0
0
pages
AMenuitem has non-empty accessible name
Front-end Development 4.1.2 0
0
pages
AElement with aria-hidden has no content in sequential focus navigation
Front-end Development 4.1.2 0
0
pages
ALink has non-empty accessible name
Content Authoring
Front-end Development		 4.1.2 0
0
pages
AIframe element has non-empty accessible name
Content Authoring
Front-end Development		 4.1.2 0
0
pages
AElement with presentational children has no focusable content
Front-end Development 4.1.2 0
0
pages
AButton has non-empty accessible name
UX Design
Content Authoring
Front-end Development		 4.1.2 0
0
pages
AARIA state or property is permitted
Front-end Development 4.1.2 0
0
pages
ARole attribute has valid value
Front-end Development 4.1.2 0
0
pages
AALink text colour must contrast sufficiently with its background colour.
Visual Design 1.4.3 0
0
pages
AAText has minimum contrast
Visual Design 1.4.3 0
0
pages
AAb (bold) element is not used.
Front-end Development 1.4.4 0
0
pages
AAi (italic) element is not used.
Front-end Development 1.4.4 0
0
pages
AAbasefont must not be used.
Front-end Development 1.4.4 0
0
pages
AAfont must not be used.
Front-end Development 1.4.4 0
0
pages

Warnings

Guideline
AImage not in the accessibility tree is decorative
Front-end Development 1.1.1 0
0
pages
AImage accessible name is descriptive
Front-end Development 1.1.1 0
0
pages
ALinks to multimedia require a text transcript.
Content Authoring
UX Design		 1.2.1 0
0
pages
Aarea link to sound file must have text transcript.
Content Authoring
UX Design		 1.2.1 0
0
pages
AVideo element visual-only content has accessible alternative.
Content Authoring 1.2.1 0
0
pages
AAudio element content has text alternative
Content Authoring 1.2.1 0
0
pages
AVideo element auditory content has accessible alternative
Content Authoring 1.2.2 0
0
pages
AVideo element visual content has accessible alternative
Content Authoring 1.2.3 0
0
pages
AAll p elements are not used as headers.
Content Authoring 1.3.1 0
0
pages
AUse a quote element to mark up quotations.
Front-end Development
UX Design		 1.3.1 0
0
pages
ANon-decorative content in pseudo classes
Front-end Development 1.3.1 0
0
pages
AElement needs to have the right semantic role
Front-end Development 1.3.1 0
0
pages
AHTML layout tables should make sense when linearized
Front-end Development 1.3.2 0
0
pages
AUsing white space characters to control spacing within a word
Visual Design
Content Authoring		 1.3.2 0
0
pages
AUsing white space characters to create multiple columns or to format tables in plain text content
Content Authoring
Visual Design		 1.3.2 0
0
pages
AAudio Control.
Front-end Development
UX Design		 1.4.2 0
0
pages
AASCII art should have a skipover link.
Front-end Development
UX Design		 2.4.1 0
0
pages
ASuspicious link text.
Content Authoring
UX Design		 2.4.4 0
0
pages
Aarea should not open new window without warning.
UX Design
Visual Design		 3.2.2 0
0
pages
AAll select elements do not cause an extreme change in context.
UX Design
Visual Design		 3.2.2 0
0
pages
Aiframe elements with identical accessible names have equivalent purpose
Content Authoring
Front-end Development		 4.1.2 0
0
pages
AACaptions (Live)
Content Authoring 1.2.4 0
0
pages
AAElement in sequential focus order has visible focus
Visual Design
Front-end Development
UX Design		 2.4.7 0
0
pages
AAList items must not be used to format text.
Visual Design
UX Design		 3.2.4 0
0
pages

Reviews

Guideline
AAlt text for all img elements contains all text in the image unless the image text is decorative or appears elsewhere in the document.
Content Authoring
Visual Design
UX Design		 1.1.1 0
0
pages
AAlt text for all input elements with a type attribute value of "image" identifies the purpose or function of the image.
Content Authoring
UX Design		 1.1.1 0
0
pages
AAlt text for all area elements identifies the link destination.
Content Authoring
UX Design
Visual Design		 1.1.1 0
0
pages
AAlt text for all input elements with a type attribute value of "image" contains all non-decorative text in the image.
Front-end Development 1.1.1 0
0
pages
AAlt text for all area elements contains all non-decorative text in the image area.
Front-end Development 1.1.1 0
0
pages
ASound file must have a text transcript.
Content Authoring
UX Design		 1.2.1 0
0
pages
Aobject link to multimedia file require equivalent alternatives (e.g., captions or auditory descriptions of the visual track).
Content Authoring 1.2.3 0
0
pages
AAll h1 elements are not used for formatting
Visual Design 1.3.1 0
0
pages
AAll h2 elements are not used for formatting.
Visual Design 1.3.1 0
0
pages
AAll h3 elements are not used for formatting
Visual Design 1.3.1 0
0
pages
AAll h4 elements are not used for formatting
Visual Design 1.3.1 0
0
pages
AAll h5 elements are not used for formatting
Visual Design 1.3.1 0
0
pages
AAll h6 elements are not used for formatting
Visual Design 1.3.1 0
0
pages
Apre element should not be used to create tabular layout.
Front-end Development
UX Design		 1.3.1 0
0
pages
AAll data table summaries describe navigation and structure of the table.
Content Authoring
UX Design		 1.3.1 0
0
pages
ATable markup is used for all tabular information.
Front-end Development
UX Design		 1.3.1 0
0
pages
ATable captions identify the table.
Front-end Development 1.3.1 0
0
pages
AAll visual lists are marked.
Front-end Development 1.3.1 0
0
pages
AAll layout tables make sense when linearized.
Front-end Development
UX Design		 1.3.2 0
0
pages
AChanging the meaning of content by positioning information with CSS.
Front-end Development 1.3.2 0
0
pages
AAll text references do not use shape, size, or relative position alone.
Content Authoring
UX Design		 1.3.3 0
0
pages
AColor is not used as the only visual means of conveying meaning
UX Design
Visual Design		 1.4.1 0
0
pages
AAll functionality of the content is operable through a keyboard interface
Front-end Development 2.1.1 0
0
pages
AKeyboard Trap
UX Design
Front-end Development		 2.1.2 0
0
pages
AKeyboard shortcuts are implemented in a changeable and safe manner
Front-end Development 2.1.4 0
0
pages
AImage is not a flickering GIF.
Visual Design 2.3.1 0
0
pages
AA "skip to content" link appears on all pages with blocks of material prior to the main document.
UX Design 2.4.1 0
0
pages
AAll frame titles identify the purpose or function of the frame.
Content Authoring
UX Design		 2.4.1 0
0
pages
AAll groups of links with a related purpose are marked.
Front-end Development
UX Design		 2.4.1 0
0
pages
AHTML page title is descriptive
Content Authoring 2.4.2 0
0
pages
AThe tab order specified by tabindex attributes follows a logical order.
Visual Design
UX Design		 2.4.3 0
0
pages
ALink text is meaningful when read out of context.
Content Authoring 2.4.4 0
0
pages
AContent can be operated using simple inputs on a wide range of pointing devices.
Front-end Development
UX Design		 2.5.1 0
0
pages
AFunctionality that can be operated using a single pointer, is implemented in a safe manner.
Front-end Development 2.5.2 0
0
pages
AUser interface components with labels that include text or images of text has the text that is presented visually contained in the name.
Front-end Development 2.5.3 0
0
pages
AFunctionality that can be operated by device motion or user motion can also be operated by user interface.
Front-end Development 2.5.4 0
0
pages
AFunctionality that can be operated by device motion or user motion can be disabled to prevent accidental actuation.
Front-end Development 2.5.4 0
0
pages
ALoading the web page does not cause a new window to open.
UX Design
Front-end Development		 3.2.1 0
0
pages
AChange of context occurs only by user activation unless a warning is provided.
Front-end Development 3.2.2 0
0
pages
AAll form submission error messages identify any empty required fields.
UX Design
Visual Design		 3.3.1 0
0
pages
AAll textarea elements have a label that is positioned close to control.
UX Design
Visual Design		 3.3.2 0
0
pages
AAll input elements, type of "password", have a label that is positioned close to the control.
UX Design
Visual Design		 3.3.2 0
0
pages
AAll input elements, type of "checkbox", have a label that is positioned close to the control.
UX Design
Visual Design		 3.3.2 0
0
pages
AAll input elements, type of "file", have a label that is positioned close to the control.
UX Design
Visual Design		 3.3.2 0
0
pages
AAll input elements, type of "radio", have a label that is positioned close to the control.
UX Design
Visual Design		 3.3.2 0
0
pages
AAll input elements, type of "file", have a label that describes the purpose or function of the control.
Front-end Development 3.3.2 0
0
pages
AAll select elements have a label that is positioned close to the control.
Front-end Development 3.3.2 0
0
pages
AAll select elements have a label that describes the purpose or function of the control.
Front-end Development 3.3.2 0
0
pages
AAll input elements, type of "text", have a label that is positioned close to the control.
Front-end Development 3.3.2 0
0
pages
AAll input elements, type of "password", have a label that describes the purpose or function of the control.
Front-end Development 3.3.2 0
0
pages
AAll input elements, type of "text", have a label that describes the purpose or function of the control.
Front-end Development 3.3.2 0
0
pages
AAll input elements, type of "checkbox", have a label that describes the purpose or function of the control.
Front-end Development 3.3.2 0
0
pages
AAll input elements, type of "radio", have a label that describes the purpose or function of the control.
Front-end Development 3.3.2 0
0
pages
AAll form fields that are required are indicated to the user as required.
UX Design
Visual Design		 3.3.2 0
0
pages
AAContent does not restrict its view and operation to a single display orientation, such as portrait or landscape, unless a specific display orientation is essential.
Front-end Development
UX Design		 1.3.4 0
0
pages
AAThe purpose of each input field collecting information about the user can be programmatically determined.
Front-end Development 1.3.5 0
0
pages
AAScrolling in more than one direction is not necessary for small displays and zoomed content.
Front-end Development
UX Design		 1.4.10 0
0
pages
AAThe visual presentation of UI and graphics components have a contrast ratio of at least 3:1 against adjacent color(s).
Visual Design 1.4.11 0
0
pages
AANo loss of content or functionality occurs when changing certain text style properties.
Front-end Development
Visual Design		 1.4.12 0
0
pages
AAAdditional content that appears and disappears in coordination with keyboard focus or pointer hover does not obstruct operation.
Front-end Development 1.4.13 0
0
pages
AAThe luminosity contrast ratio between text and background color in all images is at least 4.5:1.
Visual Design
UX Design		 1.4.3 0
0
pages
AAVisited link text colour must contrast sufficiently with its background colour.
Visual Design 1.4.3 0
0
pages
AAActive link text colour must contrast sufficiently with its background colour.
Visual Design 1.4.3 0
0
pages
AASelected link text colour must contrast sufficiently with its background colour.
Visual Design 1.4.3 0
0
pages
AASites must have a site map.
Front-end Development
UX Design		 2.4.5 0
0
pages
AAHeading is descriptive
Content Authoring 2.4.6 0
0
pages
AAEach label describes its associated input element.
Front-end Development
UX Design		 2.4.6 0
0
pages
AAWords and phrases not in the document"s primary language are marked.
Front-end Development 3.1.2 0
0
pages
AARepeated blocks of content appear in the same frame within the frameset.
UX Design
Visual Design		 3.2.3 0
0
pages
AARepeated components appear in the same relative order each time they appear.
UX Design
Visual Design		 3.2.3 0
0
pages
AAblockquote must not be used for indentation.
Front-end Development 3.2.4 0
0
pages
AAAll form submission error messages provide assistance in correcting the error.
UX Design
Content Authoring		 3.3.3 0
0
pages
AAForm submission data is presented to the user before final acceptance for all irreversible transactions.
UX Design 3.3.4 0
0
pages
AAInformation deleted using a web page can be recovered.
UX Design 3.3.4 0
0
pages
AAStatus messages can be programmatically determined through role or properties.
Front-end Development 4.1.3 0
0
pages
table has 75 search results