Report
About the Evaluation
- Report Creator
- Not provided
- Evaluation Commissioner
- Not provided
- Evaluation date
- 25-10-2023
Executive Summary
Scope of the Evaluation
- Website name
- Bleizo.nl
- Scope of the website
- All content of the Bleizo website located at: https://bleizo.nl/
- WCAG Version
- 2.1
- Conformance target
- AA
- Accessibility support baseline
- Not provided
- Additional evaluation requirements
- Not provided
Detailed Audit Results
Summary
Reported on 50 of 50 WCAG 2.1 AA Success Criteria.
- 29 Passed
- 0 Failed
- 0 Cannot tell
- 21 Not present
- 0 Not checked
All Results
1 Perceivable
1.1 Text Alternatives
Success Criterion | Result | Observations |
---|---|---|
1.1.1: Non-text Content |
Entire sampleResult: Passed |
Entire sampleObservations: The website provides text alternatives for all non-text content, such as images, videos, and audio files, ensuring that this content is accessible to users who rely on screen readers or cannot perceive visual or auditory content. |
1.2 Time-based Media
Success Criterion | Result | Observations |
---|---|---|
1.2.1: Audio-only and Video-only (Prerecorded) |
Entire sampleResult: Not present |
|
1.2.2: Captions (Prerecorded) |
Entire sampleResult: Not present |
|
1.2.3: Audio Description or Media Alternative (Prerecorded) |
Entire sampleResult: Not present |
|
1.2.4: Captions (Live) |
Entire sampleResult: Not present |
|
1.2.5: Audio Description (Prerecorded) |
Entire sampleResult: Not present |
1.3 Adaptable
Success Criterion | Result | Observations |
---|---|---|
1.3.1: Info and Relationships |
Entire sampleResult: Passed |
Entire sampleObservations: Interactive elements indicate their purpose and state |
1.3.2: Meaningful Sequence |
Entire sampleResult: Passed |
Entire sampleObservations: The page has a logical tab order. List items (<li>) are contained within <ul>, <ol> or <menu> parent elements. Heading elements appear in a sequentially-descending order |
1.3.3: Sensory Characteristics |
Entire sampleResult: Passed |
Entire sampleObservations: Interactive elements indicate their purpose and state |
1.3.4: Orientation |
Entire sampleResult: Passed |
Entire sampleObservations: Upon evaluation, the website content was observed to be fully responsive and adaptable to both portrait and landscape orientations on various devices. |
1.3.5: Identify Input Purpose |
Entire sampleResult: Not present |
1.4 Distinguishable
Success Criterion | Result | Observations |
---|---|---|
1.4.1: Use of Color |
Entire sampleResult: Passed |
Entire sampleObservations: Interactive elements indicate their purpose and state |
1.4.2: Audio Control |
Entire sampleResult: Not present |
|
1.4.3: Contrast (Minimum) |
Entire sampleResult: Passed |
Entire sampleObservations: Background and foreground colors have a sufficient contrast ratio |
1.4.4: Resize text |
Entire sampleResult: Passed |
Entire sampleObservations: The website's text elements are responsive and can be resized up to 200 percent without the use of assistive technology. |
1.4.5: Images of Text |
Entire sampleResult: Passed |
Entire sampleObservations: The website consistently uses text for conveying information and does not utilize images of text in any part of its content. |
1.4.10: Reflow |
Entire sampleResult: Passed |
Entire sampleObservations: The website's design ensures that content can be presented without loss of information or functionality, and does not require two-dimensional scrolling on a variety of devices, including those with small screens. This was verified across different devices and screen sizes. |
1.4.11: Non-text Contrast |
Entire sampleResult: Passed |
Entire sampleObservations: The visual elements of the website, including buttons, graphical controls, and user interface components, demonstrate a contrast ratio of at least 3:1 against adjacent colors. This was verified using contrast analysis tools to ensure compliance. |
1.4.12: Text Spacing |
Entire sampleResult: Passed |
Entire sampleObservations: Testing confirmed that when adjusting text style properties (such as line height, spacing, and letter spacing) in the website's content, there was no loss of content or functionality |
1.4.13: Content on Hover or Focus |
Entire sampleResult: Not present |
Entire sampleObservations: The website does not employ any mechanisms where additional content becomes visible upon receiving and then removing pointer hover or keyboard focus. |
2 Operable
2.1 Keyboard Accessible
Success Criterion | Result | Observations |
---|---|---|
2.1.1: Keyboard |
Entire sampleResult: Passed |
Entire sampleObservations: All functionalities of the website are operable through a keyboard interface, with no dependency on specific timings for keystrokes. This includes navigating through menus, selecting items, and triggering actions. The site is designed to be fully accessible via keyboard, catering to users who cannot use a mouse or prefer keyboard navigation. |
2.1.2: No Keyboard Trap |
Entire sampleResult: Passed |
Entire sampleObservations: Keyboard focus can be moved to and away from all components on the website using standard keyboard interfaces, such as the Tab key and arrow keys. There are no components that trap keyboard focus. |
2.1.4: Character Key Shortcuts |
Entire sampleResult: Not present |
Entire sampleObservations: No keyboard shortcuts are implemented on the website |
2.2 Enough Time
Success Criterion | Result | Observations |
---|---|---|
2.2.1: Timing Adjustable |
Entire sampleResult: Not present |
Entire sampleObservations: No time limits are set by the content of the website |
2.2.2: Pause, Stop, Hide |
Entire sampleResult: Not present |
Entire sampleObservations: No moving, blinking, scrolling, or auto-updating information is present on the website |
2.3 Seizures and Physical Reactions
Success Criterion | Result | Observations |
---|---|---|
2.3.1: Three Flashes or Below Threshold |
Entire sampleResult: Not present |
Entire sampleObservations: No flashing items are present on the website |
2.4 Navigable
Success Criterion | Result | Observations |
---|---|---|
2.4.1: Bypass Blocks |
Entire sampleResult: Not present |
|
2.4.2: Page Titled |
Entire sampleResult: Passed |
Entire sampleObservations: Each web page on the site has a distinct and descriptive title that accurately reflects its content and purpose. |
2.4.3: Focus Order |
Entire sampleResult: Passed |
Entire sampleObservations: The website is designed to ensure that all focusable components receive focus in a logical sequence that preserves the meaning and operability of the content. This was verified through keyboard navigation tests, where the focus order followed the visual and logical structure of each page. |
2.4.4: Link Purpose (In Context) |
Entire sampleResult: Passed |
Entire sampleObservations: The website's links are designed so that the purpose of each can be understood either from the link text itself or from the link text combined with its programmatically determined context. This was ensured by carefully crafting link text to be descriptive and by providing additional context where necessary. |
2.4.5: Multiple Ways |
Entire sampleResult: Passed |
Entire sampleObservations: The website offers multiple methods for users to locate specific pages within its structure, such as navigation menus, and a site map. |
2.4.6: Headings and Labels |
Entire sampleResult: Passed |
Entire sampleObservations: he website uses clear and descriptive headings and labels throughout, effectively communicating the topic or purpose of the content they precede. |
2.4.7: Focus Visible |
Entire sampleResult: Passed |
Entire sampleObservations: The website is designed to ensure that any keyboard-operable user interface includes a visible keyboard focus indicator. This was verified through keyboard navigation testing, confirming that when elements are navigated using the keyboard, a clear focus indicator is visible |
2.5 Input Modalities
Success Criterion | Result | Observations |
---|---|---|
2.5.1: Pointer Gestures |
Entire sampleResult: Not present |
Entire sampleObservations: The website does not implement any functionality that requires multipoint or path-based gestures for operation. |
2.5.2: Pointer Cancellation |
Entire sampleResult: Not present |
Entire sampleObservations: No pointer based fucntions are present on the website |
2.5.3: Label in Name |
Entire sampleResult: Passed |
Entire sampleObservations: The website ensures that for all user interface components with labels, whether they include text or images of text, the accessible name (programmatically determined) matches the text that is presented visually. |
2.5.4: Motion Actuation |
Entire sampleResult: Not present |
3 Understandable
3.1 Readable
Success Criterion | Result | Observations |
---|---|---|
3.1.1: Language of Page |
Entire sampleResult: Passed |
Entire sampleObservations: <html> element has a [lang] attribute |
3.1.2: Language of Parts |
Entire sampleResult: Not present |
3.2 Predictable
Success Criterion | Result | Observations |
---|---|---|
3.2.1: On Focus |
Entire sampleResult: Passed |
Entire sampleObservations: Upon testing, it was observed that focusing on any user interface component (like links, buttons, form fields) on the website does not automatically trigger a change in the context, such as redirecting to a new page or refreshing the current page. The website maintains the current context unless an explicit action (like clicking or pressing Enter) is taken by the user. |
3.2.2: On Input |
Entire sampleResult: Passed |
Entire sampleObservations: During evaluation, it was noted that changing the settings of any user interface components, does not automatically cause a change of context like page refresh or navigation. Users are not unexpectedly redirected or faced with a context change without prior notification. |
3.2.3: Consistent Navigation |
Entire sampleResult: Passed |
Entire sampleObservations: The navigational elements of the website, such as menus and links, maintain a consistent relative order across all web pages. |
3.2.4: Consistent Identification |
Entire sampleResult: Passed |
Entire sampleObservations: Throughout the website, components with identical functionalities are consistently identified using the same labels, icons, and design elements across all web pages. |
3.3 Input Assistance
Success Criterion | Result | Observations |
---|---|---|
3.3.1: Error Identification |
Entire sampleResult: Not present |
Entire sampleObservations: The website does not contain interactive user components such as input fields or forms |
3.3.2: Labels or Instructions |
Entire sampleResult: Not present |
Entire sampleObservations: The website does not contain interactive user components such as input fields or forms |
3.3.3: Error Suggestion |
Entire sampleResult: Not present |
Entire sampleObservations: The website does not contain interactive user components such as input fields or forms |
3.3.4: Error Prevention (Legal, Financial, Data) |
Entire sampleResult: Not present |
Entire sampleObservations: The website does not contain interactive user components such as input fields or forms |
4 Robust
4.1 Compatible
Success Criterion | Result | Observations |
---|---|---|
4.1.1: Parsing |
Entire sampleResult: Passed |
Entire sampleObservations: Upon reviewing the website's HTML structure, it was found that all elements have complete start and end tags, are nested correctly as per their specifications, and do not contain duplicate attributes. Additionally, all IDs used in the markup are unique. |
4.1.2: Name, Role, Value |
Entire sampleResult: Passed |
Entire sampleObservations: The website's user interface components, such as links, are designed in a way that their names and roles can be programmatically determined via labels or aria-roles. |
4.1.3: Status Messages |
Entire sampleResult: Passed |
Entire sampleObservations: [role]s have all required [aria-*] attributes |
Sample of Audited Web Pages
- Homepage - bleizo.nl
- Organisatie - https://bleizo.nl/organisatie
- Organisatie - https://bleizo.nl/organisatie
Web Technology
HTML,CSS,WAI-ARIA,JavaScript,SVG,PDF
Recording of Evaluation Specifics
Not provided