Accessibility checks

Scanned at: Jan 15, 2024, 8:45 PM

Report created: Jan 19, 2024, 1:39 PM

100%

Errors

		Guideline
AAll `img` elements have an `alt` attribute	Front-end Development UX Design	1.1.1
AAlt text for all `img` elements used as source anchors is not empty when there is no other text in the anchor.	Front-end Development Content Authoring	1.1.1
A"All `input` elements with a `type` attribute value of "image" have an `alt` attribute."	Content Authoring Visual Design	1.1.1
AAll `area` elements have an `alt` attribute.	UX Design Front-end Development	1.1.1
AAll `embed` elements have an associated `noembed` element that contains a text equivalent to the `embed` element.	Front-end Development	1.1.1
AAll `input` elements, except those with with a `type` attribute value of "image", do not have an `alt` attribute.	Front-end Development	1.1.1
AAlt text should not be part of the filename.	Content Authoring UX Design	1.1.1
AAll `input` elements, `type` of "text", have an explicitly associated label.	Front-end Development	1.3.1
AAll `select` elements have a label that contains text.	Front-end Development	1.3.1
AAll `textarea` elements have an explicitly associated `label`.	UX Design Visual Design	1.3.1
AAll data `table` summaries contain text.	Content Authoring UX Design	1.3.1
AAll layout `tables` have an empty `summary` attribute or no `summary` attribute.	Front-end Development UX Design	1.3.1
AAll layout tables do not contain `caption` elements	Front-end Development UX Design	1.3.1
AAll `input` elements, `type` of "password", have an explicitly associated `label`	Front-end Development	1.3.1
AAll `input` elements, `type` of "checkbox", have an explicitly associated `label`.	Front-end Development	1.3.1
AAll `input` elements, `type` of "file", have an explicitly associated `label`.	Front-end Development	1.3.1
AAll `input` elements, `type` of "radio", have an explicitly associated `label`.	UX Design Front-end Development	1.3.1
AAll radio button groups are marked using `fieldset` and legend elements	Front-end Development	1.3.1
AAll `input` elements, `type` of \"radio\", have a `label` containing text.	Front-end Development	1.3.1
AAll `input` elements, `type` of \"checkbox\", have a `label` containing text.	Front-end Development	1.3.1
AAll `input` elements, `type` of \"password\", have a `label` containing text.	Front-end Development	1.3.1
AAll `select` elements have a label that contains text.	Front-end Development	1.3.1
AAll `textarea` elements have a `label` containing text.	Front-end Development	1.3.1
AAll `input` elements, `type` of "text", have a `label` containing text.	Front-end Development	1.3.1
AAll `input` elements, `type` of "file", have a `label` containing text.	Front-end Development	1.3.1
ATable summaries do not duplicate the table captions.	Front-end Development	1.3.1
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
AAll checkbox groups are marked using `fieldset` and `legend` elements.	Front-end Development	1.3.1
AData tables that contain both row and column headers use the `scope` attribute, or id and headers, to identify cells.	Front-end Development UX Design	1.3.1
AAll text colors or no text colors are set.	UX Design Visual Design	1.4.1
ALinks inside text are distinguishable.	UX Design Visual Design Front-end Development	1.4.1
AAll `onmousedown` event handlers have have an associated `onkeydown` event handler	Front-end Development UX Design	2.1.1
AAll `onmouseout` event handlers have an associated `onblur` event handler	Front-end Development UX Design	2.1.1
AAll `onmouseover` event handlers have an associated `onfocus` event handler.	Front-end Development UX Design	2.1.1
AAll `onmouseup` event handlers have an associated `onkeyup` event handler	Front-end Development UX Design	2.1.1
A`Meta` refresh is not used with a time-out.	Front-end Development	2.2.1
A`blink` element is not used.	Front-end Development	2.2.2
A`marquee` element is not used.	Front-end Development	2.2.2
AAuto-redirect must not be used.	Front-end Development	2.2.2
AError All `frames` have a title attribute.	Content Authoring UX Design	2.4.1
ADocument contains a `title` element	Content Authoring	2.4.2
A`title` contains text	Content Authoring	2.4.2
AEach source anchor contains text	UX Design Content Authoring	2.4.4
ADocument has required `lang` attribute(s)	Front-end Development	3.1.1
ADocument has a valid `language` code	Front-end Development	3.1.1
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
AEach `input` element has only one associated `label`.	Front-end Development	3.3.2
AEach label associated with an `input` element contains text.	Front-end Development	3.3.2
A`id` attributes must be unique.	Front-end Development	4.1.1
AAProvide sufficient contrast between text and background colours.	Visual Design	1.4.3
AA`b` (bold) element is not used.	Front-end Development	1.4.4
AA`i` (italic) element is not used	Front-end Development	1.4.4
AA`basefont` must not be used	Front-end Development	1.4.4
AA`font` must not be used.	Front-end Development	1.4.4
AAThe header following an `h1` is `h1 or h2`	Content Authoring	2.4.6
AAThe header following an `h2` is `h1`, `h2` or `h3`	Content Authoring	2.4.6
AAThe header following an `h3` is `h1`, `h2`, `h3` or `h4`	Content Authoring	2.4.6
AAThe header following an `h4` is `h1`, `h2`, `h3`, `h4` or `h5`	Content Authoring	2.4.6
AAThe header following an `h5` is `h6` or any header less than `h6`	Content Authoring	2.4.6

Warnings

		Guideline
AAlt text for all `img` elements is not placeholder text unless author has confirmed it is correct.	UX Design Front-end Development	1.1.1
AAlt text for all `input` elements with a `type` attribute value of "image" is less than 100 characters (English) or the user has confirmed that the Alt text is as short as possible.	Content Authoring UX Design	1.1.1
AImage used in `input` element - Alt text should not be placeholder text.	Content Authoring UX Design	1.1.1
A`area` link to sound file must have text transcript.	Content Authoring UX Design	1.1.1
ALinks to multimedia require a text transcript.	Content Authoring UX Design	1.2.1
ALinks to multimedia have a link to text alternative.	UX Design Content Authoring	1.2.1
AAll `p` elements are not used as headers.	Content Authoring	1.3.1
AAutoplaying audible Multimedia can be shut down.	Front-end Development UX Design	1.4.2
AASCII art should have a skipover link.	Front-end Development UX Design	2.4.1
A`title` is short.	Content Authoring	2.4.2
A`title` is not placeholder text	Content Authoring	2.4.2
ASuspicious `link` text.	Content Authoring UX Design	2.4.4
A`area` should not open new window without warning.	UX Design Visual Design	3.2.2
AAll `select` elements do not cause an extreme change in context.	UX Design Visual Design	3.2.2
AA`List` items must not be used to format text.	Visual Design UX Design	3.2.4

Reviews

		Guideline
AImage `Alt` text is short.	Content Authoring UX Design Visual Design	1.1.1
AA long description is used for each `img` element that does not have Alt text conveying the same information as the image.	Front-end Development	1.1.1
AAlt text for all `img` elements is the empty string ("") if the image is decorative.	Front-end Development	1.1.1
A`applet` contains a text equivalent in the `alt` attribute of the `applet`.	Content Authoring UX Design	1.1.1
AText equivalents for `applet` must be updated if `applet` changes.	Content Authoring UX Design	1.1.1
A`applet` contains a text equivalent in the body of the `applet`.	Content Authoring UX Design	1.1.1
A"Alt 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
AAlt text for all `area` elements identifies the link destination.	Content Authoring UX Design Visual Design	1.1.1
AEach object must have a text equivalent that will be displayed if the object is not.	Content Authoring UX Design	1.1.1
AAlt text for all `img` elements that are not used as source anchors conveys the same information as the image.	Content Authoring UX Design	1.1.1
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
AAlt text for all `area` elements contains all non-decorative text in the image area.	Front-end Development	1.1.1
A`title` attribute for all `img` elements is absent or the empty string ("") if the image is decorative.	Front-end Development	1.1.1
A`Sound file` must have a text transcript.	Content Authoring UX Design	1.2.1
A`object` link to multimedia file require equivalent alternatives (e.g., captions or auditory descriptions of the visual track).	Content Authoring UX Design	1.2.3
A`object` may require a long description.	UX Design Content Authoring	1.2.3
AAll `textarea` elements have a label that is positioned close to control.	UX Design Visual Design	1.3.1
AAll complex data tables have a summary	UX Design Content Authoring	1.3.1
AAll `input` elements, `type` of "password", have a label that is positioned close to the control.	UX Design Visual Design	1.3.1
AAll `input` elements, `type` of "checkbox", have a label that is positioned close to the control.	UX Design Visual Design	1.3.1
AAll `input` elements, `type` of "file", have a label that is positioned close to the control.	UX Design Visual Design	1.3.1
AAll `input` elements, `type` of "radio", have a label that is positioned close to the control.	UX Design Visual Design	1.3.1
AAll data tables contain `th` elements	Front-end Development UX Design	1.3.1
AAll layout tables do not contain `th` elements.	Front-end Development UX Design	1.3.1
AAll data tables contain a `caption` unless the table is identified within the document.	Front-end Development	1.3.1
A`pre` element should not be used to create tabular layout.	Front-end Development UX Design	1.3.1
AAll data table summaries describe navigation and structure of the table.	Content Authoring UX Design	1.3.1
AAll `select` elements have a label that is positioned close to the control.	Front-end Development	1.3.1
A"All `input` elements, `type` of "text", have a label that is positioned close to the control."	Front-end Development	1.3.1
AUse `thead` to group repeated table headers, `tfoot` for repeated table footers, and `tbody` for other groups of rows.	Front-end Development	1.3.1
AUse `colgroup` and `col` elements to group columns.	Front-end Development UX Design	1.3.1
ATable markup is used for all tabular information.	Front-end Development UX Design	1.3.1
ATable captions identify the table.	Front-end Development	1.3.1
AAll visual lists are marked.	Front-end Development	1.3.1
AUnicode right-to-left marks or left-to-right marks are used whenever the HTML bidirectional algorithm produces undesirable results.	Front-end Development UX Design	1.3.1
AAll changes in text direction are marked using the dir attribute.	Front-end Development UX Design	1.3.1
AAll layout `tables` make sense when linearized	Front-end Development UX Design	1.3.3
AAll text references do not use shape, size, or relative position alone.	Content Authoring UX Design	1.3.3
AFor all `img` elements, text does not refer to the image by color alone.	Visual Design UX Design	1.4.1
A`applet` should not use color alone.	Visual Design UX Design	1.4.1
A`input` should not use color alone	Visual Design UX Design	1.4.1
A`object` must not use color alone.	UX Design Visual Design	1.4.1
AColor alone should not be used in the script.	Visual Design UX Design	1.4.1
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.4.5
A`applet` user interface must be accessible.	Front-end Development Visual Design UX Design Content Authoring	2.1.1
A`object` user interface must be accessible - (codebase).	Front-end Development Visual Design UX Design Content Authoring	2.1.1
AUser interface for `script` must be accessible.	Front-end Development	2.1.1
AAll `ondblclick` event handlers have corresponding keyboard-specific functions	Front-end Development UX Design	2.1.1
AAll `onmousemove` event handlers have corresponding keyboard-specific functions.	Front-end Development UX Design	2.1.1
A`applet` provides a keyboard mechanism to return focus to the parent window.	Front-end Development	2.1.2
A`object` provides a keyboard mechanism to return focus to the parent window.	Front-end Development	2.1.2
A`embed` provides a keyboard mechanism to return focus to the parent window.	Front-end Development	2.1.2
AKeyboard shortcuts are implemented in a changeable and safe manner	Front-end Development	2.1.4
AAll `img` elements have associated images that do not flicker.	Visual Design	2.3.1
A`applets` cause screen flicker.	Visual Design UX Design	2.3.1
AAll `objects` do not flicker.	UX Design Visual Design	2.3.1
A`script` should not cause screen flicker.	Front-end Development	2.3.1
A"A "`skip to content`" link appears on all pages with blocks of material prior to the main document."	UX Design	2.4.1
AAll `frame` titles identify the purpose or function of the frame.	Content Authoring UX Design	2.4.1
AAll groups of links with a related purpose are marked.	Front-end Development UX Design	2.4.1
A`title` describes the document	Content Authoring	2.4.2
A`Link` text is meaningful when read out of context.	Content Authoring	2.4.4
AContent can be operated using simple inputs on a wide range of pointing devices.	Front-end Development UX Design	2.5.1
AFunctionality that can be operated using a single pointer, is implemented in a safe manner.	Front-end Development	2.5.2
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
AFunctionality that can be operated by device motion or user motion can also be operated by user interface.	Front-end Development	2.5.4
AFunctionality that can be operated by device motion or user motion can be disabled to prevent accidental actuation.	Front-end Development	2.5.4
ALoading the web page does not cause a new window to open.	UX Design Front-end Development	3.2.1
AChange of context occurs only by user activation unless a warning is provided.	Front-end Development	3.2.2
AAll form submission error messages identify any empty required fields.	UX Design Visual Design	3.3.1
AEach label describes its associated `input` element.	Front-end Development UX Design	3.3.2
AAll `input` elements, `type` of "file", have a `label` that describes the purpose or function of the control.	Front-end Development	3.3.2
AAll `select` elements have a label that describes the purpose or function of the control.	Front-end Development	3.3.2
AAll `input` elements, type of "`password`", have a `label` that describes the purpose or function of the control.	Front-end Development	3.3.2
AAll `input` elements, `type` of "text", have a `label` that describes the purpose or function of the control.	Front-end Development	3.3.2
AAll `input` elements, `type` of "checkbox", have a `label` that describes the purpose or function of the control.	Front-end Development	3.3.2
AAll `input` elements, `type` of "radio", have a `label` that describes the purpose or function of the control.	Front-end Development	3.3.2
AAll `form` fields that are required are indicated to the user as required.	UX Design Visual Design	3.3.2
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
AAThe purpose of each input field collecting information about the user can be programmatically determined.	Front-end Development	1.3.5
AAScrolling in more than one direction is not necessary for small displays and zoomed content.	Front-end Development UX Design	1.4.10
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
AANo loss of content or functionality occurs when changing certain text style properties.	Front-end Development Visual Design	1.4.12
AAAdditional content that appears and disappears in coordination with keyboard focus or pointer hover does not obstruct operation.	Front-end Development	1.4.13
AAThe luminosity contrast ratio between text and background color in all images is at least 5:1.	Visual Design UX Design	1.4.3
AAVisited link text colour must contrast sufficiently with its background colour.	Visual Design	1.4.3
AAActive link text color must contrast sufficiently with its background color.	Visual Design	1.4.3
AASelected link text color must contrast sufficiently with its background color.	Visual Design	1.4.3
AALink text colour must contrast sufficiently with its background colour.	Visual Design	1.4.3
AASites must have a site map.	Front-end Development UX Design	2.4.5
AAAll `h1` elements are not used for formatting	Visual Design	2.4.6
AAAll `h2` elements are not used for formatting.	Visual Design	2.4.6
AAAll `h3` elements are not used for formatting	Visual Design	2.4.6
AAAll `h4` elements are not used for formatting	Visual Design	2.4.6
AAAll `h5` elements are not used for formatting	Visual Design	2.4.6
AAAll `h6` elements are not used for formatting	Visual Design	2.4.6
AAWords and phrases not in the document"s primary language are marked.	Front-end Development	3.1.2
AARepeated blocks of content appear in the same `frame` within the `frameset`.	UX Design Visual Design	3.2.3
AAThe tab order specified by `tabindex` attributes follows a logical order.	Visual Design UX Design	3.2.3
AARepeated components appear in the same relative order each time they appear.	UX Design Visual Design	3.2.3
AA`blockquote` must not be used for indentation.	Front-end Development	3.2.4
AAUse the `blockquote` element to mark up block quotations	Front-end Development UX Design	3.2.4
AAAll form submission error messages provide assistance in correcting the error.	UX Design Content Authoring	3.3.3
AAForm submission data is presented to the user before final acceptance for all irreversable transactions.	UX Design	3.3.4
AAInformation deleted using a web page can be recovered.	UX Design	3.3.4
AAStatus messages can be programmatically determined through role or properties.	Front-end Development	4.1.3