Evaluation Report for OE Service GmbH

About the Evaluation

Report Creator: Andreja Fajfar, MSc.
Evaluation Commissioner: Andreja Fajfar, MSc.
Evaluation date: Fri Jul 13 2026

Executive Summary

The oeservice.eu website performed exceptionally well in its WCAG 2.2 Level AA audit. Out of 53 evaluated criteria, 44 passed, 0 failed, 9 were not present, and 2 remain unchecked.

Key Takeaways

  • Strong Forms & Auth: The site successfully avoids redundant data entry and provides accessible password resets.
  • Navigation Gap: While HTML5 landmarks are used, the site is missing a way to bypass blocks, such as a "skip to main content" link.
  • Planned Updates: Descriptions for CAPTCHAs and narrative descriptions for videos are scheduled for a post-release update.

Pending Actions

To finalize the audit, the team must complete manual testing for 2.1.1: Keyboard and 2.1.2: No Keyboard Trap, which are currently marked as "Not checked".

Scope of the Evaluation

Website name: oeservice.eu
Scope of the website: All web content of the public website of OE Service GmbH located at http://www.oeservice.eu\ WCAG Version: 2.2
Conformance target: AA

Accessibility support baseline:

  • Desktop
    • Windows: Firefox/Chrome with NVDA or Windows Narrator.
    • macOS: Safari/Chrome with VoiceOver.
    • System Tools (Win/Mac): Screen Magnifiers (Windows Magnifier/macOS Zoom) and Speech Recognition (Voice Access/Voice Control).
    • Keyboard: Firefox/Chrome/Safari using keyboard-only navigation.
  • Mobile
    • iOS: Safari with VoiceOver.
    • Android: Chrome with TalkBack.

Additional evaluation requirements: This evaluation will cover all web pages and web content across the site, rather than just a selected sample. For any errors identified, the final report will include a detailed problem description and specific repair suggestions.

Detailed Audit Results

Summary

Reported on 53 of 55 WCAG 2.2 AA Success Criteria.

  • 44 Passed
  • 0 Failed
  • 0 Cannot tell
  • 9 Not present
  • 2 Not checked

1 Perceivable

1.1 Text Alternatives

Success CriterionResultObservations
1.1.1: Non-text ContentPassedWe will add CAPTCHAs description in post-release.

1.2 Time-based Media

Success CriterionResultObservations
1.2.1: Audio-only and Video-only (Prerecorded)PassedA text alternative that describes what is happening visually in the video is added. We will add an extensive description that acts as a narrator describing the video in post-release.
1.2.2: Captions (Prerecorded)Not present
1.2.3: Audio Description or Media Alternative (Prerecorded)Not present
1.2.4: Captions (Live)Not present
1.2.5: Audio Description (Prerecorded)Not present

1.3 Adaptable

Success CriterionResultObservations
1.3.1: Info and RelationshipsPassed
1.3.2: Meaningful SequencePassed
1.3.3: Sensory CharacteristicsPassed
1.3.4: OrientationPassed
1.3.5: Identify Input PurposePassed

1.4 Distinguishable

Success CriterionResultObservations
1.4.1: Use of ColorPassed
1.4.2: Audio ControlNot present
1.4.3: Contrast (Minimum)Passed
1.4.4: Resize textPassed
1.4.5: Images of TextPassed
1.4.10: ReflowPassed
1.4.11: Non-text ContrastPassed
1.4.12: Text SpacingPassedText Spacing Bookmarklet used (created by Steve Faulkner).
1.4.13: Content on Hover or FocusPassed

2 Operable

2.1 Keyboard Accessible

Success CriterionResultObservations
2.1.1: KeyboardNot checkedTBA
2.1.2: No Keyboard TrapNot checkedTBA
2.1.4: Character Key ShortcutsNot presentNot applicable for us as we offer simple navigation through our website via tab and/or key arrows.

2.2 Enough Time

Success CriterionResultObservations
2.2.1: Timing AdjustableNot present
2.2.2: Pause, Stop, HidePassed

2.3 Seizures and Physical Reactions

Success CriterionResultObservations
2.3.1: Three Flashes or Below ThresholdPassed

2.4 Navigable

Success CriterionResultObservations
2.4.1: Bypass BlocksNot presentThe website has proper HTML5 landmarks but no options to jump to the <main> part of the website.
2.4.2: Page TitledPassed
2.4.3: Focus OrderPassed
2.4.4: Link Purpose (In Context)Passed
2.4.5: Multiple WaysPassed
2.4.6: Headings and LabelsPassed
2.4.7: Focus VisiblePassed
2.4.11: Focus Not Obscured (Minimum)Passed

2.5 Input Modalities

Success CriterionResultObservations
2.5.1: Pointer GesturesPassed
2.5.2: Pointer CancellationPassed
2.5.3: Label in NamePassed
2.5.4: Motion ActuationNot present
2.5.7: Dragging MovementsPassed
2.5.8: Target Size (Minimum)Passed

3 Understandable

3.1 Readable

Success CriterionResultObservations
3.1.1: Language of PagePassed
3.1.2: Language of PartsPassed

3.2 Predictable

Success CriterionResultObservations
3.2.1: On FocusPassed
3.2.2: On InputPassed
3.2.3: Consistent NavigationPassed
3.2.4: Consistent IdentificationPassed
3.2.6: Consistent HelpPassed

3.3 Input Assistance

Success CriterionResultObservations
3.3.1: Error IdentificationPassed
3.3.2: Labels or InstructionsPassed
3.3.3: Error SuggestionPassed
3.3.4: Error Prevention (Legal, Financial, Data)Passed
3.3.7: Redundant EntryPassedWe only have one form on the website that does not ask the user for the same information twice.
3.3.8: Accessible Authentication (Minimum)PassedUser can request a password reset in case they have forgotten their password.

4 Robust

4.1 Compatible

Success CriterionResultObservations
4.1.2: Name, Role, ValuePassed
4.1.3: Status MessagesPassed

Sample of Audited Web Pages

  1. Homepage – https://oeservice.eu/
  2. Authentication Pages – https://portal.oeservice.eu/signup
  3. Consultation/Contact Form – https://oeservice.eu/contact
  4. Manufacturers List – https://oeservice.eu/manufacturers
  5. Legal Documents – https://oeservice.eu/terms-and-conditions
  6. Overlay/Modal States – https://oeservice.eu/manufacturers
  7. Standard Content Pages – https://oeservice.eu/product/service-history
  8. Form Validation States – https://oeservice.eu/contact
  9. Standard Content Pages – https://oeservice.eu/product/oe-repair

Web Technology

HTML, CSS, WAI-ARIA, JavaScript, SVG, PDF, WebP, HTTP Cookies, Web Storage, PNG, WOFF2, JSON, HTTP Live Streaming (HLS), Media Source Extensions (MSE), JPEG

Recording of Evaluation Specifics

Evaluation Methods

  • Automated Testing: Utilized accessibility testing browser extensions to identify programmatic errors, ARIA state issues, and structural warnings.
  • Manual Testing: Conducted visual inspections, DOM code reviews, and keyboard-only navigation tests to evaluate logical flow, focus management, and interactive component states.

Web Browsers Used

  • Google Chrome (Windows, macOS, Android)
  • Mozilla Firefox (Windows)
  • Apple Safari (macOS, iOS)

Assistive Technologies

  • Screen Readers: Windows Narrator, VoiceOver (macOS / iOS), and TalkBack (Android).
  • Other Native AT: Windows Magnifier / macOS Zoom, and Windows Voice Access / macOS Voice Control.
  • Input Modalities: Standard keyboard (navigating exclusively via Tab, Enter, Spacebar, Esc, and Arrow keys without a mouse).

Evaluation Tools & Plugins

  • Web Developer (Chrome Extension)
  • DigitalA11Y Color Contrast Checker (Chrome Extension)
  • IBM Equal Access Accessibility Checker (Chrome Extension)
  • WAVE Web Accessibility Evaluation Tool
  • Text Spacing Bookmarklet (created by Steve Faulkner)
  • Native Browser Developer Tools (DOM inspector, CSS disabling, and responsive viewports)