Embedded Files
SEDONA COMPUTER REPAIR NEAR ME
BEST OUT 100% is the Goal
Accessibility:
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
ARIA
[aria-*] attributes do not match their roles
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
These items address areas which an automated testing tool cannot cover.:
Buttons have an accessible name
ARIA IDs are unique
Image elements have [alt] attributes
[user-scalable="no"] is not used in the <meta name="viewport"> element and the [maximum-scale] attribute is not less than 5.
button, link, and menuitem elements have accessible names
[aria-hidden="true"] elements do not contain focusable descendents
[role] values are valid
Background and foreground colors have a sufficient contrast ratio
Document has a <title> element
[id] attributes on active, focusable elements are unique
<html> element has a [lang] attribute
<html> element has a valid value for its [lang] attribute
Links are distinguishable without relying on color.
Links have a discernible name
Lists contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are contained within <ul>, <ol> or <menu> parent elements
No element has a [tabindex] value greater than 0
Heading elements appear in a sequentially-descending order
Values assigned to role="" are valid ARIA roles.
Image elements do not have [alt] attributes that are redundant text.
[accesskey] values are unique
Elements with role="dialog" or role="alertdialog" have accessible names.
ARIA input fields have accessible names
ARIA meter elements have accessible names
ARIA progressbar elements have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] have all required children.
[role]s are contained by their required parent element
Elements with the role=text attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA tooltip elements have accessible names
ARIA treeitem elements have accessible names
The page contains a heading, skip link, or landmark region
<dl>'s contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
Definition list items are wrapped in <dl> elements
No form fields have multiple labels
<frame> or <iframe> elements have a title
<html> element has an [xml:lang] attribute with the same base language as the [lang] attribute.
Input buttons have discernible text.
<input type="image"> elements have [alt] text
Elements with visible text labels have matching accessible names.
Form elements have associated labels
The document does not use <meta http-equiv="refresh">
<object> elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
Tables have different content in the summary attribute and <caption>.
Tables use <caption> instead of cells with the [colspan] attribute to indicate a caption.
<td> elements in a large <table> have one or more table headers.
Cells in a <table> element that use the [headers] attribute refer to table cells within the same table.
<th> elements and elements with [role="columnheader"/"rowheader"] have data cells they describe.
[lang] attributes have a valid value
<video> elements contain a <track> element with [kind="captions"]
All heading elements contain content.
Identical links have the same purpose.
Document has a main landmark.
Touch targets have sufficient size and spacing.
Page updated
Google Sites
Report abuse