Report Title: Einstein Toolkit
November 17, 2021 16:20
  • Followed links in specfied domain only

section element role semantics. (Deprecated)

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

Details

Rule ID Role 5
Definition section element must only have role semantics of alert, alertdialog, application, contentinfo, dialog, document, log, main, marquee, presentation, region, search or status. NOTE: Deprecated in favor of HTML 3 a more general rule on role restrictions based on ARIA in HTML specification.
Purpose
  • The section element has role restrictions as part of its definition in the W3C HTML5 Specification.
  • The section element can be used to for identifying many types of of sections and sub sections within a web page and a limited number of widget roles, review the techniques for the possible uses of the section element with ARIA role semantics.
  • The section element should not be used when there is a more semantically meaningful elements available (e.g. main, header, footer,..)
  • The default (e.g. no role attribute) is role="region", if the section element has an accessible name it will be considered a landmark in the document.
WCAG Success Criteria

1.3.1 Info and Relationships (Level A, Primary Success Criterion)

Other Related Success Criterion:

Rule Category Styling/Content
Scope Element
Target Resources section element
  • section
Techniques
  • If the content of the section element is used as a sub-section of another landmark use role="region" with an accessible name to identify the sub-section.
  • If the content of the section element is used to provide a time sensitive text message to the user that is very important for the user to know use the live region role="alert" on the section element.
  • If the content of the section element is used to create a error dialog box with a message that is very important for the user to know use the role="alertdialog" on the section element.
  • If the content of the section element is primarily form controls and/or widgets use role="application" on the section element.
  • If the content of the section element is used as the container for footer information that is repeated on most pages of the website use role="contentinfo" on the section element.
  • If the content of the section element is used to create a non-error message related dialog box use the role="dialog" on the section element.
  • If the content of the section element is primarily composed of non interactive text and images and the section element is embedded inside an container element with role="application"" use the role="document" attribute on the section element.
  • If the content of the section element is used as the container a list of messages use role="log" on the section element.
  • If the content of the section element is used as the container for the main content of the page use role="main" on the section element.
  • If the content of the section element is used as for periodically changing text on the page that is considered more informational (e.g. news tag line) use role="marquee" on the section element.
  • If the content of the section element is NOT being used as the container for a region landmark use role="presentation" on the section element to remove it from landmark navigation.
  • If the content of the section element is used as the container for sub section within a landmark use role="region" on the section element.
  • If the content of the section element is used as the container for a search the website form use role="search" on the section element.
  • If the content of the section element is used as the container for a status message that will be automatically be updated on some pending transaction use role="status" on the section element.
  • If the content of the section element does not meet any of the other techniques do not use the role attribute.
Informational Links

Page Results

Element Results Implementation Level
Page Page Title Result V W MC P Score Status
15 Tutorial for New Users Not Applicable - - - - - na
14 Citation Not Applicable - - - - - na
13 Credits Not Applicable - - - - - na
12 Poisson equation Not Applicable - - - - - na
11 Multipatch wave equation Not Applicable - - - - - na
10 Binary Neutron Star Not Applicable - - - - - na
9 Binary Black Hole Not Applicable - - - - - na
8 Gallery Not Applicable - - - - - na
7 Contribute Not Applicable - - - - - na
6 Einstein Toolkit - Support Not Applicable - - - - - na
5 Documentation Not Applicable - - - - - na
4 Download Not Applicable - - - - - na
3 About Not Applicable - - - - - na
2 The Einstein Toolkit Not Applicable - - - - - na
1 The Einstein Toolkit Not Applicable - - - - - na
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