- URL: https://www.muslimuzbekistan.com/
- Ruleset: HTML5 and ARIA Techniques
Adaptable
Violations | Warnings | Manual Checks |
Passed | |
---|---|---|---|---|
Number of Rules | 1 | - | 5 | 10 |
Adaptable Rule Results
Number of Elements | Implementation Level | ||||||||
---|---|---|---|---|---|---|---|---|---|
ID | Rule Summary | Result | V | W | MC | P | H | Score | Status |
Landmark 2 | All content must be contained in landmarks | Violation | 1 | - | - | 57 | 10 | 98 | AC |
Order 1 | Reading order: CSS positioning | Manual Check | - | - | 42 | - | 11 | 0 | R |
List 1 | Use semantic markup for lists | Manual Check | - | - | 32 | - | 6 | 0 | R |
Landmark 16 |
region landmark must have accessible name
|
Manual Check | - | - | 5 | - | - | 0 | R |
Landmark 18 | Landmarks must identify content regions | Manual Check | - | - | 4 | - | 2 | 0 | R |
Sensory 1 | Not only shape, size and location | Manual Check | - | - | 1 | - | - | 0 | R |
Landmark 17 | Landmarks must be uniquely identifiable | Passed | - | - | - | 4 | 2 | 100 | C |
Heading 5 | Headings must be properly nested | Passed | - | - | - | 4 | - | 100 | C |
Heading 8 | Headings nested in landmarks | Passed | - | - | - | 4 | - | 100 | C |
Heading 6 | Headings must have text content | Passed | - | - | - | 4 | - | 100 | C |
Landmark 10 |
navigation landmark: restrictions
|
Passed | - | - | - | 1 | 2 | 100 | C |
Landmark 9 |
banner landmark: restrictions
|
Passed | - | - | - | 1 | 1 | 100 | C |
Landmark 8 |
banner landmark: must be top-level
|
Passed | - | - | - | 1 | - | 100 | C |
Landmark 12 |
contentinfo landmark: must be top-level
|
Passed | - | - | - | 1 | - | 100 | C |
Landmark 13 |
contentinfo landmark: restrictions
|
Passed | - | - | - | 1 | - | 100 | C |
Landmark 11 |
main landmark: must be top-level
|
Passed | - | - | - | 1 | - | 100 | C |
Role 6 |
Do not override nav element semantics. (Deprecated)
|
Not Applicable | - | - | - | - | 1 | - | na |
Layout 1 | Layout tables must have meaningful sequence | Not Applicable | - | - | - | - | - | - | na |
Landmark 19 |
complementary landmark: must be top level
|
Not Applicable | - | - | - | - | - | - | na |
Landmark 15 |
form landmark: restrictions
|
Not Applicable | - | - | - | - | - | - | na |
Landmark 14 |
search landmark: restrictions
|
Not Applicable | - | - | - | - | - | - | na |
Heading 7 |
First landmark heading h2
|
Not Applicable | - | - | - | - | - | - | na |
Layout 3 |
Verify aria-flowto supports reading order
|
Not Applicable | - | - | - | - | - | - | na |
Table 7 |
Data cells must use headers attribute
|
Not Applicable | - | - | - | - | - | - | na |
Table 6 |
Header cells must be th elements
|
Not Applicable | - | - | - | - | - | - | na |
Table 5 | Identify table markup as data or layout | Not Applicable | - | - | - | - | - | - | na |
Table 4 | Data tables must have unique names | Not Applicable | - | - | - | - | - | - | na |
Table 3 | Data tables must have description | Not Applicable | - | - | - | - | - | - | na |
Table 1 | Data cells must have row/column headers | Not Applicable | - | - | - | - | - | - | na |
Role 10 |
Overriding h1-h6 role semantics. (Deprecated)
|
Not Applicable | - | - | - | - | - | - | na |
Role 9 |
Do not override footer element role . (Deprecated)
|
Not Applicable | - | - | - | - | - | - | na |
Role 8 |
Do not override header element role . (Deprecated)
|
Not Applicable | - | - | - | - | - | - | na |
Role 7 |
aside element role semantics. (Deprecated)
|
Not Applicable | - | - | - | - | - | - | na |
Role 5 |
section element role semantics. (Deprecated)
|
Not Applicable | - | - | - | - | - | - | na |
Role 4 |
article element role semantics. (Deprecated)
|
Not Applicable | - | - | - | - | - | - | na |
Role 2 |
body element role semantics. (Deprecated)
|
Not Applicable | - | - | - | - | - | - | na |
Role 1 |
main element role semantics. (Deprecated)
|
Not Applicable | - | - | - | - | - | - | na |
Table 8 | Name must be different than description | Not Applicable | - | - | - | - | - | - | na |
Layout 2 | Do not nest layout tables | 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 |
|
AC AC-R |
95-99 | Almost Complete |
|
PI PI-R |
50-94 | Partial Implementation |
|
NI NI-R |
0-50 | Not Implemented |
|
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 |