Compliance status100.0%
Pages scanned:5
Errors
| Check | Responsibility | Guideline | Outstanding | Pages affected |
|---|---|---|---|---|
AARIA element is missing required context | Front-end Development | 1.3.1 | 0 | 0PAGES |
AARIA refers to a non-existing ID | Front-end Development | 1.3.1 | 0 | 0PAGES |
AARIA state or property has invalid value | Front-end Development | 1.3.1 | 0 | 0PAGES |
AAuto-redirect must not be used | Front-end Development | 2.2.2 | 0 | 0PAGES |
AButton is missing an accessible name | UX DesignContent AuthoringFront-end Development | 4.1.2 | 0 | 0PAGES |
AComplex data table is missing ID and/or header attributes to associate headers with data cells | Front-end DevelopmentUX Design | 1.3.1 | 0 | 0PAGES |
AElement marked as hidden must not be included in tab navigation | Front-end Development | 4.1.2 | 0 | 0PAGES |
AElement with role attributes is missing required states or properties | Front-end Development | 4.1.2 | 0 | 0PAGES |
AElements intended as presentation-only contain focusable content | Front-end Development | 4.1.2 | 0 | 0PAGES |
AForm field is missing an accessible name | Front-end Development | 4.1.2 | 0 | 0PAGES |
AHeader attribute is referring to wrong ID or cell | Front-end Development | 1.3.1 | 0 | 0PAGES |
AHeading is missing an accessible name | Content AuthoringFront-end Development | 1.3.1 | 0 | 0PAGES |
AIframe element is missing an accessible name | Content AuthoringFront-end Development | 4.1.2 | 0 | 0PAGES |
AIframe with interactive elements is not keyboard navigable | Front-end Development | 2.1.1 | 0 | 0PAGES |
AImage button is missing an accessible name | Front-end Development | 1.1.1 | 0 | 0PAGES |
AImage is missing alternative text | Content AuthoringFront-end Development | 1.1.1 | 0 | 0PAGES |
AIncorrect use of ARIA state or property | Front-end Development | 4.1.2 | 0 | 0PAGES |
ALayout tables must not contain caption elements | Front-end DevelopmentUX Design | 1.3.1 | 0 | 0PAGES |
ALayout tables should have an empty summary attribute or none at all | Front-end DevelopmentUX Design | 1.3.1 | 0 | 0PAGES |
ALink inside text is difficult to see or identify | UX DesignVisual DesignFront-end Development | 1.4.1 | 0 | 0PAGES |
ALink is missing an accessible name | Content AuthoringFront-end Development | 4.1.2 | 0 | 0PAGES |
AMarquee element must not be used | Front-end Development | 2.2.2 | 0 | 0PAGES |
AMenu item doesn't have an accessible name | Front-end Development | 4.1.2 | 0 | 0PAGES |
AMeta refresh should not cause the page to reload or redirect automatically after a short delay | Front-end Development | 2.2.1 | 0 | 0PAGES |
ANon-text object element is missing an accessible name | Content AuthoringUX Design | 1.1.1 | 0 | 0PAGES |
APage is missing a language attribute | Front-end Development | 3.1.1 | 0 | 0PAGES |
APage is missing a title | Content AuthoringFront-end Development | 2.4.2 | 0 | 0PAGES |
APage language attribute has invalid language tag | Front-end Development | 3.1.1 | 0 | 0PAGES |
AParent element is missing required children | Front-end Development | 1.3.1 | 0 | 0PAGES |
ARole attribute is missing a valid value | Front-end Development | 4.1.2 | 0 | 0PAGES |
AScrollable content is not accessible using the keyboard | Front-end Development | 2.1.1 | 0 | 0PAGES |
ASVG element with defined role is missing an accessible name | Content AuthoringFront-end Development | 1.1.1 | 0 | 0PAGES |
ATable header is not associated to any data cells | Front-end DevelopmentUX Design | 1.3.1 | 0 | 0PAGES |
ATable summary and caption must be different | Front-end Development | 1.3.1 | 0 | 0PAGES |
AUndefined ARIA attribute must not be used | Front-end Development | 1.3.1 | 0 | 0PAGES |
AAAutocomplete attribute is missing a valid value | UX DesignFront-end Development | 1.3.5 | 0 | 0PAGES |
AAElement language attribute has invalid language tag | Front-end Development | 3.1.2 | 0 | 0PAGES |
AALink text fails minimum contrast requirements | Visual Design | 1.4.3 | 0 | 0PAGES |
AAOrientation of the page should not be restricted | Visual DesignFront-end Development | 1.3.4 | 0 | 0PAGES |
AAText fails minimum contrast requirements | Visual Design | 1.4.3 | 0 | 0PAGES |
Warnings
| Check | Responsibility | Guideline | Outstanding | Pages affected |
|---|---|---|---|---|
AAre p elements used as headers? | Content Authoring | 1.3.1 | 04 reviewed | 1PAGES |
AAre the hidden images decorative? | Front-end Development | 1.1.1 | 017 reviewed | 5PAGES |
AAre users able to shut off content with sound? | Front-end DevelopmentUX Design | 1.4.2 | 0 | 0PAGES |
AAre white space characters used for spacing? | Visual DesignContent Authoring | 1.3.2 | 0 | 0PAGES |
AAre white space characters used to format tables? | Content AuthoringVisual Design | 1.3.2 | 0 | 0PAGES |
ADo all input fields have permanently visible labels? | UX DesignContent AuthoringFront-end Development | 3.3.2 | 0 | 0PAGES |
ADo elements have the right semantic role? | Front-end Development | 1.3.1 | 0 | 0PAGES |
ADo links with the same name serve the same purpose? | Front-end Development | 2.4.4 | 0 | 0PAGES |
ADo the iframe elements with same name have same purpose? | Content AuthoringFront-end Development | 4.1.2 | 0 | 0PAGES |
ADoes audio content in a video have an accessible alternative? | Content Authoring | 1.2.2 | 0 | 0PAGES |
ADoes the layout table make sense when read line by line? | Front-end Development | 1.3.2 | 0 | 0PAGES |
AIs quote element used to mark up quotations? | Front-end DevelopmentUX Design | 1.3.1 | 0 | 0PAGES |
AIs the image alternative text descriptive enough? | Front-end Development | 1.1.1 | 017 reviewed | 2PAGES |
AIs the visible label of an interactive element part of the accessible name? | Front-end Development | 2.5.3 | 0 | 0PAGES |
AIs there non-decorative content in pseudo classes? | Front-end Development | 1.3.1 | 0 | 0PAGES |
AADo autocomplete attributes align with their purpose? | Front-end Development | 1.3.5 | 02 reviewed | 1PAGES |
AADo links on top of images have minimum contrast? | Visual DesignFront-end Development | 1.4.3 | 02 reviewed | 1PAGES |
AADo prerecorded videos have audio descriptions? | Content AuthoringFront-end Development | 1.2.5 | 0 | 0PAGES |
AADoes text on top of images have minimum contrast? | Visual DesignFront-end Development | 1.4.3 | 02 reviewed | 1PAGES |
AADoes the live video have captions? | Content Authoring | 1.2.4 | 0 | 0PAGES |
AADoes the local language attibute match the language of the content? | Front-end Development | 3.1.2 | 01 reviewed | 1PAGES |
AAIs the keyboard focus visible at all times? | Visual DesignFront-end DevelopmentUX Design | 2.4.7 | 0129 reviewed | 5PAGES |
Reviews
| Check | Responsibility | Guideline | Outstanding | Pages affected |
|---|---|---|---|---|
AAre all visual lists correctly coded as lists? | Front-end Development | 1.3.1 | 0 | 0PAGES |
AAre elements focused in a logical order when navigating with keyboard? | Visual DesignUX Design | 2.4.3 | 05 reviewed | 5PAGES |
AAre enough instructions provided for everyone to understand and operate the content? | Content AuthoringUX Design | 1.3.3 | 05 reviewed | 5PAGES |
AAre headings used for formatting? | UX DesignFront-end Development | 1.3.1 | 035 reviewed | 5PAGES |
AAre input errors described in text? | UX DesignVisual Design | 3.3.1 | 01 reviewed | 1PAGES |
AAre the table captions identifying the table? | Front-end Development | 1.3.1 | 0 | 0PAGES |
AAre there alternatives for features that require device or user motion? | Front-end Development | 2.5.4 | 05 reviewed | 5PAGES |
ACan all functionality be operated with keyboard? | Front-end Development | 2.1.1 | 05 reviewed | 5PAGES |
ADo image buttons have alt text? | Content AuthoringUX Design | 1.1.1 | 0 | 0PAGES |
ADoes audio element have text alternative? | Content Authoring | 1.2.1 | 0 | 0PAGES |
ADoes video have an accessible alternative? | Content Authoring | 1.2.3 | 0 | 0PAGES |
ADoes visual-only video content have an accessible alternative? | Content Authoring | 1.2.1 | 0 | 0PAGES |
AIs color alone used to convey meaning? | UX DesignVisual Design | 1.4.1 | 05 reviewed | 5PAGES |
AIs CSS modifying the visual layout and changing the meaning of content? | Front-end Development | 1.3.2 | 0200 reviewed | 5PAGES |
AIs keyboard focus trapped in any component? | UX DesignFront-end Development | 2.1.2 | 05 reviewed | 5PAGES |
AIs table markup used for all table information consistently? | Front-end DevelopmentUX Design | 1.3.1 | 0 | 0PAGES |
AIs the data table summary describing the navigation and structure of the table? | Content AuthoringUX Design | 1.3.1 | 0 | 0PAGES |
AIs the image a flickering GIF? | Visual Design | 2.3.1 | 0 | 0PAGES |
AIs the page title descriptive enough? | Content Authoring | 2.4.2 | 05 reviewed | 5PAGES |
AIs the pre element used to create a table? | Front-end DevelopmentUX Design | 1.3.1 | 0 | 0PAGES |
AIs there a mechanism to bypass blocks of repeated content? | Front-end Development | 2.4.1 | 05 reviewed | 5PAGES |
AAAre form submission errors helpful? | UX DesignContent Authoring | 3.3.3 | 01 reviewed | 1PAGES |
AAAre important UI and graphical components distinguishable? | Visual Design | 1.4.11 | 05 reviewed | 5PAGES |
AAAre status messages presented clearly to assistive technology users? | Front-end Development | 4.1.3 | 0 | 0PAGES |
AAAre the labels describing the input fields accurately? | Front-end DevelopmentUX Design | 2.4.6 | 05 reviewed | 1PAGES |
AAAre users able to use the fonts, spacing, and font size of their choice, without loss of content? | Front-end DevelopmentVisual Design | 1.4.12 | 05 reviewed | 5PAGES |
AAAre users forced to scroll in two dimensions when zoomed in? | Front-end DevelopmentUX Design | 1.4.10 | 05 reviewed | 5PAGES |
AADo the images contain text? | UX DesignVisual Design | 1.4.5 | 01 reviewed | 1PAGES |
AADoes content that appears on hover or focus block important information or disappear before users can interact with it? | Front-end Development | 1.4.13 | 05 reviewed | 5PAGES |
AADoes text over background image meet minimum contrast requirements? | Visual DesignUX Design | 1.4.3 | 0 | 0PAGES |
AAIf legal financial data is processed, are there safeguards for form submission? | UX Design | 3.3.4 | 01 reviewed | 1PAGES |
AAIs link text distinguishable in all interactive states? (Minimum) | Visual DesignUX Design | 1.4.3 | 048 reviewed | 4PAGES |
AAIs the heading descriptive enough? | Content Authoring | 2.4.6 | 035 reviewed | 5PAGES |