Backend
Overview of all sections and features
easyVision
easyMonitoring
easyMonitorung manual checks
- A: ARIA attributes must conform to valid values (WCAG 4.1.2)
- A: Links must have discernible text (WCAG 2.4.4 + 4.1.2)
- A: The visual order on the page follows the DOM order (WCAG 1.3.2)
- A: The page has a logical tab order (WCAG 2.4.3)
- A: Links must be distinguishable from the surrounding text (WCAG 1.4.1)
- A: Form fields should only have one label element (WCAG 3.3.2)
- A: Custom controls have appropriate ARIA roles (WCAG 4.1.2)
- A: Interactive controls can be focused using the keyboard (WCAG 2.1.1 + 2.4.7)
- A: The user focus is not accidentally trapped in one region (WCAG 2.1.2)
- A: Custom controls have associated labels (WCAG 4.1.2)
- A: Custom controls have appropriate ARIA roles (WCAG 4.1.2)
- AA: Elements must have sufficient color contrast (WCAG 1.4.3)
- AA: Interactive elements indicate their purpose and status (WCAG 1.3.1 + 4.1.2)
- Best practice: HTML5 landmark elements are used to improve navigation (WCAG 1.3.1 + 2.4.1)
- Best practice: Hidden content on the page could not be analyzed (WCAG 4.1.2 + 2.4.3)
- Best practice: The focus will be on newly added content (WCAG 1.3.1 + 4.1.2)
- Best practice: Content outside the screen is hidden from assistive technologies (WCAG 1.3.1 + 4.1.2)
easyMonitorung automatic checks
- A: ARIA toggle fiields must have an accessible name (WCAG 4.1.2)
- A: ARIA meter nodes must have an accessible name (WCAG 1.1.1)
- A: ARIA attributes must be used as specified for the element's role (WCAG 4.1.2)
- A: ARIA roles used must conform to valid values (WCAG 4.1.2)
- A: < li> elements must be contained in a < ul> or < ol> (WCAG 1.3.1)
- A: < ul> and < ol> must only directly contain < li>, < script> or < template> elements (WCAG 1.3.1)
- A: Input buttons must have discernible text (WCAG 4.1.2)
- A: Elements must have their visible text as part of their accessible name (WCAG 2.5.3)
- A: Image buttons must have alternative text (WCAG 1.1.1 + 4.1.2)
- A: Form elements must have labels (WCAG 4.1.2)
- A: Images must have alternative text (WCAG 1.1.1)
- A: HTML elements with lang and xml -> lang must have the same base language (WCAG 3.1.1)
- A: < html> element must have a valid value for the lang attribute (WCAG 3.1.1)
- A: Frames must have a unique title attribute (WCAG 4.1.2)
- A: Frames must have an accessible name (WCAG 4.1.2)
- A: Documents must have < title> element to aid in navigation (WCAG 2.4.2)
- A: < dt> and < dd> elements must be contained by a < dl> (WCAG 1.3.1)
- A: Page must not have means to bypass repeated blocks (WCAG 2.4.1)
- A: Buttons must have discernible text (WCAG 4.1.2)
- A: < blink> elements are deprecated and must not be used (WCAG 2.2.2)
- A: < audio> elements must have a captions track (WCAG 1.2.1)
- A: ARIA attributes must conform to valid names (WCAG 4.1.2)
- A: ARIA tooltip nodes must have an accessible name (WCAG 4.1.2)
- A: aria-roledescription must be on elements with a semantic role (WCAG 4.1.2)
- A: Required ARIA attributes must be provided (WCAG 4.1.2)
- A: ARIA progressbar nodes must have an accessible name (WCAG 1.1.1)
- A: ARIA input fields must have an accessible name (WCAG 4.1.2)
- A: ARIA hidden element must not be focusable or contain focusable elements (WCAG 4.1.2)
- A: aria-hidden='true' must not be present on the document body (WCAG 1.3.1 + 4.1.2)
- A: Deprecated ARIA roles must not be used (WCAG 4.1.2)
- A: ARIA commands must have an accessible name (WCAG 4.1.2)
- A: aria-braille attributes must have a non-braille equivalent (WCAG 4.1.2)
- A: Elements must only use ARIA supported attributes (WCAG 4.1.2)
- A: Active < area> elements must have alternative text (WCAG 2.4.4 + 4.1.2)
- Best practice: ARIA role should be appropriate for the element
- A: < html> must have a lang attribute (WCAG 3.1.1)
- A: Certain ARIA roles must be contained by particular parents (WCAG 1.3.1)
- A: < dl> elements must only directly contain properly-ordered < dt> and < dd> groups, < script>, < template> or < div> elements (WCAG 1.3.1)