Report Title: pvsunglasses4sale
May 23, 2022 20:06
  • 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.

Landmarks must identify content regions

Violations Warnings Manual
Checks
Passed
Number of Pages - - 25 -
25 pages with manual checks;

Details

Rule ID Landmark 18
Definition Landmarks must identify regions of content on the page according to the ARIA Landmark Roles specification.
Purpose
  • When ARIA landmarks are used to identify regions of content on the page, users of assistive technologies gain programmatic access to those regions through built-in navigation commands.
  • Proper use of landmarks provides a navigable structure where common sections or features of pages can be easily accessed or, conversely, skipped over if they represent repeated blocks of content.
  • If the appropriate landmark roles are NOT used, the type or purpose of each content region will be less obvious to users of assistive technologies.
  • In the worst-case scenario, when NO landmark roles are present, the content on the page will be presented to users of assistive technologies as a single undifferentiated block.
  • Visual styling of blocks of content are often good indicators of potential landmarks (e.g. banner, main, navigation, contentinfo).
WCAG Success Criteria

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

Rule Category Landmarks
Scope Element
Target Resources Elements with ARIA Landmark roles
  • aside
  • footer
  • header
  • main
  • nav
  • section
Techniques
  • Use the appropriate landmarks to identify the different regions of content on a web page.
  • The most important landmark roles are main and navigation, as nearly every page will include at least those regions.
  • Other commonly used landmark roles include banner, contentinfo, complementary and search.
  • Use HTML5 sectioning elements that have a default ARIA landmark role: main (main), nav (navigation), aside (complementary) and in some situations header (banner) and footer (contentinfo). When using these elements, the role attribute should NOT be defined.
  • In HTML4 and XHTML 1.0 documents, a landmark can be created using a div element with a role attribute and the appropriate ARIA landmark role value (e.g., role="main").
  • The search role is typically placed on a form element or a div that surrounds the search form.
  • When there are multiple instances of a particular landmark role on a page, provide a unique accessible name for each landmark with the same role to enable users to differentiate among them.
  • An alternative landmark can be created in HTML5 by using the section element, which has a default landmark role of region, with an author-defined accessible name (e.g., using aria-labelledby to reference a heading element).
  • Do not nest landmarks with the same role (e.g., do not place navigation landmarks within a navigation landmark). Instead, use the section element technique described above to provide additional subsections within a standard landmark.
  • If a region on a page does not correspond to one of the defined ARIA landmark roles, the section element technique described above can be used to create a landmark container for the content.
Manual Checks
  • View the accessible names of the landmarks on the page and verify that each uniquely describes the type of content the landmark contains.
Informational Links

Page Results

Element Results Implementation Level
Page Page Title Result V W MC P Score Status
All Pages Manual Check - - - - 0 R

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