Report Title: clogsflips
May 14, 2022 03:19
  • Followed links in specfied domain only
Maximum page limit was reached
You need to increase the page limit to evaluate more pages in the website, which may require purchasing or increasing your subscription level.

Verify appropriate use of live region

Violations Warnings Manual
Checks		 Passed
Number of Pages - - - -

Details

Rule ID Widget 14
Definition Verify the live region has the appropriate ARIA markup to indicate whether or how the screen reader will interrupt the user with a change notification.
Purpose
  • ARIA live regions provide a mechanism for displaying dynamic text content on a page such that changes in the content will be automatically announced to screen reader users while they are focusing on other parts of the page.
  • The manner in which informational changes in live regions are announced to screen reader users is controlled by three separate ARIA roles that may be assigned to the region: alert, log and status.
  • In general, live regions should be used sparingly, since live regions that are constantly announcing changes become distracting, and may prevent the user from completing the task they are working on.
  • A common misuse of live regions is to announce the opening of pull down menus or dialog boxes: These types of announcements are better handled through the appropriate use of other ARIA markup such as the menu and dialog roles.
WCAG Success Criteria

4.1.2 Name, Role, Value (Level A, Primary Success Criterion)

Other Related Success Criterion:

Rule Category Widgets/Scripting
Scope Element
Target Resources Elements with alert, log or status roles or the aria-live attribute
  • [aria-live]
Techniques
  • The alert role identifies a live region with very important, and usually time-sensitive, information. When the information changes in this type of live region, a message is typically sent that interrupts the current speech being spoken by a screen reader. Examples includes transaction errors that are cancelling or impeding the progress of completing a financial transaction.
  • The log role identifies a type of live region where new information is added in a meaningful order and old information may disappear. Examples include chat logs, messaging history, game log, or an error log.
  • The status role identifies a live region that contains an advisory message, but one that is not important enough to justify an alert role. This type of region is often, but not necessarily, presented as a status bar, and announcements of informational changes are typically delayed until a break occurs in the current speech being read by the screen reader software.
  • When the aria-atomic attribute is specified for a live region, it indicates to assistive technologies that when a change occurs, it should re-render all of the content or just the changes.
  • The optional aria-relevant attribute on a live region indicates what types of informational changes should be communicated to the user (e.g. additions, deletions, text and all).
  • The aria-live attribute can be used to create custom live regions, with possible values of polite, assertive and off. When used in conjunction with the ARIA alert, log or status roles, care must be taken in order to avoid conflicts with the default properties of those roles.
Informational Links

Page Results

Element Results Implementation Level
Page Page Title Result V W MC P Score Status
All Pages Not Applicable - - - - - na

Implementation Score Definitions

  • The implementation score is based on the rule results across all pages and ranges from 0 to 100.
  • '-' means there were no rule results for that group (e.g. rules were not applicable).
  • The following messages give a general idea of the overall implementation of the rules for a website.
Abbrev Score Status Description
C 100 Complete Complete means all rules have passed. There were either no manual checks or all manual checks have been resolved.
R 0 Required Manual Checks
  • Manual checks are required to verify accessibility. Markup has been identified that needs to be reviewed to determine if accessibility requirements have been met.
  • Start with the website and page level manual checks since they affect website and page navigation and identification of content and then start on the element level manual checks.
AC
AC-R 		95-99 Almost Complete
  • Almost Complete means that you seem to understand the accessibility requirements of the rules, and are close to fully implementing their requirements on all pages within the website.
  • "-R" means there are required Manual Checks. Markup has been identified that needs to be reviewed to determine if accessibility requirements have been met.
PI
PI-R 		50-94 Partial Implementation
  • Partial Implementation means that you may understand at least some of the accessibility requirements.
  • "-R" means there are required Manual Checks. Markup has been identified that needs to be reviewed to determine if accessibility requirements have been met.
  • Please re-read the accessibility requirement and review the techniques before trying to improve the accessibility.
NI
NI-R 		0-50 Not Implemented
  • Incomplete means that you do not understand the accessibility requirements of the rules or did not consider accessibility in the design of the website.
  • "-R" means there are required Manual Checks. Markup has been identified that needs to be reviewed to determine if accessibility requirements have been met.
  • Please read the accessibility requirements and review the techniques before trying to improve the accessibility.
na - Not Applicable No markup was found that identifed a known or possible accessibility issue.

Note: Future versions of FAE will allow you to mark manual checks as, pass, fail or not applicable.

Implementation Score Computation

Implementation Score = P / (P + F + MC)

Each variable represents the number of element level results for a particular rule, where:

  • P = elements that passed
  • F = elements that failed
  • MC = elements that require a manual check

The score ranges in value from 0 to 100, that is from no implementation to all accessibility requirements met. In the future, FAE will allow you to change manual checks to pass, fail or not applicable, and will recompute the Implementation Score based on the updated manual checking results.

Note: When a manual check is changed to not applicable that element result is removed from the implementation score computation.

Implementation Score Combinations

Implementation scores are rule-based and are computed for the following combinations:

Pages Rules Calculation
1 1 Element level results determine the implementation score for a rule on a specific page.
1 All The implementation score for a page is the average of all implementation scores for all rules on the page, with all rules being equally weighted.
All 1 The implementation score for a rule across all the pages in a website is based on the aggregation of all element results for the rule across all pages.
All All The implementation score for a website is the average of the website rule implementation scores.

Example Rule Implementation Scores on Individual Page

Description Pass Fail Manual Check Implementation Score
A rule with scope of element, like "Image must have alt text". 8 2 0 80
A rule with scope of page like "Page must have main landmark". 0 1 0 0
A rule with scope of element with elment results of pass, fail and manual checks that may occur for the color contrast rule. 134 29 37 67

Example Rule Implementation Score for All Pages in a Website

This is a hypothetical example for a website

Page results for Rule X Pass Fail Manual Check Implementation Score
Page 1 element results for rule X. 23 12 4 59
Page 2 element results for rule X. 12 4 0 75
Page 3 element results for rule X. 45 0 0 100
Website element results for Rule X 80 16 4 80