| Order ID | ||||||
|---|---|---|---|---|---|---|
|
|
#223969 | |||||
|
|
#223847 | |||||
|
|
#223224 | |||||
|
|
#223224 | |||||
|
|
#223224 | |||||
|
|
#223224 |
Archives: Replies
Replies for tickets on suppota
Reply to: tickets(405193)
| Order ID | Product | Activations Limit | Actions | |||
|---|---|---|---|---|---|---|
|
EVOICSae2a*** |
Active Next Payment March 6, 2027 | Not yet ended | #223969 | ICS Importer | 1 | |
|
EVO1dc7c1e*** |
Active | – | #223847 | EventON | 1 | |
|
EVOf3c03b7*** |
Active Next Payment February 22, 2027 | Not yet ended | #223224 | Full Cal | 1 | |
|
EVO52893d3*** |
Active Next Payment February 22, 2027 | Not yet ended | #223224 | Daily View | 1 | |
|
EVOwv6c4d1*** |
Active Next Payment February 22, 2027 | Not yet ended | #223224 | Weekly View | 1 | |
|
EVOYVbca0b*** |
Active Next Payment February 22, 2027 | Not yet ended | #223224 |
Reply to: tickets(405193)
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||
Reply to: tickets(405496)
Hi, I rearranged it like that. now it looks even more odd.
Reply to: tickets(405537)
Reply to: tickets(405497)
Reply to: tickets(405497)
WCAG 2.2 Accessibility Audit Report
EventOn Calendar Plugin
Audit Date March 21, 2026
Target URL https://wdkwlodawa.pl/kalendarz-wydarzen/
Conformance Target WCAG 2.2 Level AA
Helpdesk Reference https://helpdesk.ashanjay.com/
Document Classification Developer Report — Internal Use
Table of Contents
1. Executive Summary
2. Methodology
3. Severity Classification
4. Findings Summary Table
5. Detailed Findings
5.1 Principle 1: Perceivable
5.2 Principle 2: Operable
5.3 Principle 3: Understandable
5.4 Principle 4: Robust
6. Conformance Statement
1. Executive Summary
This report documents the findings of a WCAG 2.2 Level AA conformance audit conducted on the EventOn calendar plugin as deployed at wdkwlodawa.pl/kalendarz-wydarzen/. The audit identified 28 distinct accessibility barriers across all four WCAG principles (Perceivable, Operable, Understandable, Robust). Critical failures were found in keyboard operability, screen reader compatibility, dynamic content announcement, semantic structure, and the new WCAG 2.2 success criteria including Target Size and Focus Not Obscured. The plugin in its current state does not meet WCAG 2.2 Level AA conformance requirements.
Total Issues Identified: 29
Critical: 9 | Major: 17 | Minor: 3
2. Methodology
The audit was performed using a combination of automated analysis (DOM inspection, HTML source review) and manual heuristic evaluation against all applicable WCAG 2.2 Level A and AA success criteria. The evaluation focused exclusively on the EventOn plugin output, including its calendar grid, event cards, expandable event detail panels, month navigation controls, search/filter functionality, location maps, social sharing widgets, and AJAX-driven content loading. Testing tools included browser DevTools accessibility inspector, keyboard-only navigation testing, and structural HTML/ARIA analysis.
3. Severity Classification
Severity Definition
Critical Complete barrier preventing access to content or functionality for one or more user groups. Immediate remediation required.
Major Significant barrier that causes substantial difficulty. High-priority remediation.
Minor Low-impact issue that causes inconvenience but does not prevent access. Standard remediation priority.
4. Findings Summary Table
ID Severity WCAG SC Component Success Criterion
P1-01 Critical 1.1.1 Organizer Thumbnail Images Non-text Content (A)
P1-02 Major 1.1.1 Google Maps Embed / Location Widget Non-text Content (A)
P1-03 Major 1.3.1 Event Listing Structure Info and Relationships (A)
P1-04 Critical 1.3.1 Expandable Event Detail Panels Info and Relationships (A)
P1-05 Major 1.3.1 Heading Hierarchy Within Event Details Info and Relationships (A)
P1-06 Major 1.3.1 Date/Time Semantics Info and Relationships (A)
P1-07 Minor 1.3.1 Event Type Tags / Category Labels Info and Relationships (A)
P1-08 Major 1.3.2 Event Card Content Order Meaningful Sequence (A)
P1-09 Major 1.4.3 Event Type Color-Coded Tags Contrast (Minimum) (AA)
P1-10 Minor 1.4.3 Month/Year Header Text Contrast (Minimum) (AA)
P1-11 Major 1.4.11 Month Navigation Controls Non-text Contrast (AA)
P2-01 Critical 2.1.1 Event Card Expand/Collapse Interaction Keyboard (A)
P2-02 Critical 2.1.1 Month Navigation (AJAX Calendar Switching) Keyboard (A)
P2-03 Major 2.1.1 Event Search / Filter Controls Keyboard (A)
P2-04 Critical 2.1.2 Expanded Event Detail Panel No Keyboard Trap (A)
P2-05 Major 2.4.3 Event Detail Panel Focus Sequence Focus Order (A)
P2-06 Major 2.4.6 Repeated Identical Headings Headings and Labels (AA)
P2-07 Major 2.4.7 Event Card Focus Indicators Focus Visible (AA)
P2-08 Critical 2.5.8 Social Share Buttons Target Size (Minimum) (AA) — WCAG 2.2
P2-09 Major 2.5.8 Month Navigation Arrow Buttons Target Size (Minimum) (AA) — WCAG 2.2
P2-10 Major 2.4.11 Sticky Header Overlapping Focused Elements Focus Not Obscured (Minimum) (AA) — WCAG 2.2
P3-01 Major 3.1.2 Mixed-Language Content Without lang Attributes Language of Parts (AA)
P3-02 Minor 3.2.1 Event Card Focus Behavior On Focus (A)
P3-03 Major 3.2.4 Inconsistent ”More” / ”Learn More” Button Labels Consistent Identification (AA)
P4-01 Critical 4.1.2 Event Card Expand/Collapse Controls Name, Role, Value (A)
P4-02 Critical 4.1.2 Month Navigation Controls Name, Role, Value (A)
P4-03 Critical 4.1.3 AJAX Calendar Content Update Status Messages (AA)
P4-04 Major 4.1.3 Search/Filter Result Updates Status Messages (AA)
P4-05 Major 4.1.2 ”Get Directions” Form Controls Name, Role, Value (A)
5. Detailed Findings
5.1 Principle 1: Perceivable
Content must be presentable to users in ways they can perceive.
P1-01: Organizer Thumbnail Images
Severity: Critical WCAG SC: 1.1.1 — Non-text Content (A)
Organizer avatar images within event detail panels use empty alt attributes (alt=””) despite being meaningful content images that convey organizational identity. These images are treated as decorative by assistive technology, resulting in loss of contextual information.
P1-02: Google Maps Embed / Location Widget
Severity: Major WCAG SC: 1.1.1 — Non-text Content (A)
The embedded location map within event detail panels lacks an accessible name. No aria-label, aria-labelledby, or title attribute is present on the iframe or container element. Screen reader users encounter an unlabelled interactive region.
P1-03: Event Listing Structure
Severity: Major WCAG SC: 1.3.1 — Info and Relationships (A)
The event list is not rendered using semantic list markup (<ul>/<ol>/<li>). Individual event cards are wrapped in generic <a> anchors without conveying their structural relationship as a list of items. Screen readers cannot communicate the total count of events or the user’s position within the list.
P1-04: Expandable Event Detail Panels
Severity: Critical WCAG SC: 1.3.1 — Info and Relationships (A)
Event cards function as disclosure widgets (expand/collapse pattern) but lack the required ARIA markup. No role=”button”, aria-expanded, or aria-controls attributes are present. The relationship between the trigger element and the detail panel is not programmatically determinable.
P1-05: Heading Hierarchy Within Event Details
Severity: Major WCAG SC: 1.3.1 — Info and Relationships (A)
Event detail panels use <h3> headings (”Szczegóły wydarzenia”, ”Czas”, ”Organizator”, ”Lokalizacja”) without a parent <h2> within the same content region. This creates a heading level skip that disrupts the document outline for screen reader navigation.
P1-06: Date/Time Semantics
Severity: Major WCAG SC: 1.3.1 — Info and Relationships (A)
Event dates and times are presented as plain text spans with visual formatting only. No <time> elements with datetime attributes are used. Machine-readable temporal data is absent, preventing assistive technology from parsing and announcing dates in the user’s locale format.
P1-07: Event Type Tags / Category Labels
Severity: Minor WCAG SC: 1.3.1 — Info and Relationships (A)
Event type badges (e.g., ”KONCERT”, ”ZABAWA”, ”PŁATNE”) are rendered as styled text without semantic grouping or ARIA role. Their function as categorical metadata is not programmatically determinable.
P1-08: Event Card Content Order
Severity: Major WCAG SC: 1.3.2 — Meaningful Sequence (A)
The DOM order within event cards places abbreviated day names, dates, and times in a sequence that does not match the logical reading order when linearized. Screen readers encounter fragmented date components (day abbreviation, date number, month abbreviation, time) as separate disconnected text nodes.
P1-09: Event Type Color-Coded Tags
Severity: Major WCAG SC: 1.4.3 — Contrast (Minimum) (AA)
Color-coded event type labels rely on background colors that may fail the 4.5:1 contrast ratio requirement against white or light text. Specific combinations observed include light-colored tag backgrounds with white text on the calendar event strips.
P1-10: Month/Year Header Text
Severity: Minor WCAG SC: 1.4.3 — Contrast (Minimum) (AA)
The month separator headers (e.g., ”marzec 2026”, ”kwiecień 2026”) use a text color that requires verification against its background for 4.5:1 minimum contrast compliance.
P1-11: Month Navigation Controls
Severity: Major WCAG SC: 1.4.11 — Non-text Contrast (AA)
Calendar navigation arrows for switching between months lack sufficient contrast against their background. The interactive boundary of these controls is not visually distinguishable at the required 3:1 ratio.
5.2 Principle 2: Operable
User interface components and navigation must be operable.
P2-01: Event Card Expand/Collapse Interaction
Severity: Critical WCAG SC: 2.1.1 — Keyboard (A)
Event cards use <a href=”#”> as click targets for expand/collapse behavior. While technically focusable, pressing Enter navigates to ”#” (top of page) rather than toggling the detail panel. The expand/collapse functionality appears to be bound exclusively to click/touch handlers without equivalent keyboard event listeners (keydown/keyup for Enter and Space).
P2-02: Month Navigation (AJAX Calendar Switching)
Severity: Critical WCAG SC: 2.1.1 — Keyboard (A)
The month forward/backward navigation controls that trigger AJAX content reloading have not been verified to support keyboard activation. If these controls are implemented as non-semantic elements (e.g., <span> or <div> with click handlers), they are completely inoperable via keyboard.
P2-03: Event Search / Filter Controls
Severity: Major WCAG SC: 2.1.1 — Keyboard (A)
The ”Wyszukaj wydarzenia” (Search Events) input and any associated filter controls require keyboard operability verification. If filter actions are triggered via mouse-only events, keyboard users cannot filter the calendar.
P2-04: Expanded Event Detail Panel
Severity: Critical WCAG SC: 2.1.2 — No Keyboard Trap (A)
When an event detail panel is expanded, there is no evidence of focus management. Keyboard users may not be able to navigate into or out of the expanded panel content in a predictable manner. The ”Get Directions” and ”Share” interactive elements within the panel may create focus traps or unreachable content.
P2-05: Event Detail Panel Focus Sequence
Severity: Major WCAG SC: 2.4.3 — Focus Order (A)
The DOM position of the expanded event detail panel content relative to its trigger element suggests that focus order may not follow the visual presentation. When a user activates an event card, focus does not programmatically move to the revealed content.
P2-06: Repeated Identical Headings
Severity: Major WCAG SC: 2.4.6 — Headings and Labels (AA)
Multiple event detail panels contain identical heading text (”Szczegóły wydarzenia” appears twice within each event’s expanded panel). Duplicate headings within the same content block create confusion for users navigating by heading.
P2-07: Event Card Focus Indicators
Severity: Major WCAG SC: 2.4.7 — Focus Visible (AA)
Custom CSS applied by the EventOn plugin overrides or suppresses the browser’s default focus outline on interactive elements. No alternative visible focus indicator was observed on event card links during keyboard navigation.
P2-08: Social Share Buttons
Severity: Critical WCAG SC: 2.5.8 — Target Size (Minimum) (AA) — WCAG 2.2
Social media sharing icons within event detail panels (Facebook, Twitter, LinkedIn, Email, WhatsApp) are rendered at dimensions that appear to be below the 24×24 CSS pixel minimum target size required by WCAG 2.2 SC 2.5.8. These compact icon buttons lack adequate spacing offsets to compensate for their small size.
P2-09: Month Navigation Arrow Buttons
Severity: Major WCAG SC: 2.5.8 — Target Size (Minimum) (AA) — WCAG 2.2
The left/right arrow controls for calendar month navigation may fall below the 24×24 CSS pixel minimum target size. No padding or margin offsets are apparent to meet the undersized target exception.
P2-10: Sticky Header Overlapping Focused Elements
Severity: Major WCAG SC: 2.4.11 — Focus Not Obscured (Minimum) (AA) — WCAG 2.2
The site employs a fixed/sticky navigation header. When keyboard users tab through event cards near the top of the viewport, focused elements may be partially or fully obscured behind the sticky header, violating the requirement that focused elements not be entirely hidden by author-created content.
5.3 Principle 3: Understandable
Information and the operation of the user interface must be understandable.
P3-01: Mixed-Language Content Without lang Attributes
Severity: Major WCAG SC: 3.1.2 — Language of Parts (AA)
Event descriptions contain English-language terms and phrases (e.g., ”Read More”, ”Stand-up”, ”Golden Mics”) embedded within Polish-language content. These foreign-language segments lack lang=”en” attributes, preventing screen readers from switching voice synthesis to the correct language.
P3-02: Event Card Focus Behavior
Severity: Minor WCAG SC: 3.2.1 — On Focus (A)
Verification required: if focusing on an event card triggers an automatic expansion of the detail panel (as opposed to requiring explicit activation), this constitutes an unexpected change of context on focus.
P3-03: Inconsistent ”More” / ”Learn More” Button Labels
Severity: Major WCAG SC: 3.2.4 — Consistent Identification (AA)
The expandable event descriptions use ”Więcej” (More) as a truncation toggle, while organizer sections use ”Dowiedz się więcej” (Learn More). Both controls perform functionally identical expand actions but use different labels, creating inconsistency.
5.4 Principle 4: Robust
Content must be robust enough to be interpreted by a wide variety of user agents, including assistive technologies.
P4-01: Event Card Expand/Collapse Controls
Severity: Critical WCAG SC: 4.1.2 — Name, Role, Value (A)
Event cards function as toggle buttons but are implemented as <a href=”#”> elements without appropriate ARIA roles or states. Missing: role=”button” (or native <button>), aria-expanded=”true|false”, and aria-controls referencing the detail panel ID. The accessible name, role, and current state of these controls are not programmatically determinable.
P4-02: Month Navigation Controls
Severity: Critical WCAG SC: 4.1.2 — Name, Role, Value (A)
Forward/backward month navigation elements lack programmatic role and accessible name. Screen readers cannot identify these controls or their function. No aria-label (e.g., ”Next month”, ”Previous month”) is present.
P4-03: AJAX Calendar Content Update
Severity: Critical WCAG SC: 4.1.3 — Status Messages (AA)
When the user navigates to a different month, the calendar content is replaced via AJAX. This content update is not communicated to assistive technology. No aria-live region, role=”status”, or role=”alert” is present to announce that new events have loaded or that the displayed month has changed. Screen reader users receive no feedback that the page content has been dynamically modified.
P4-04: Search/Filter Result Updates
Severity: Major WCAG SC: 4.1.3 — Status Messages (AA)
When event search or filter controls modify the displayed events, the result status (e.g., number of matching events or ”no events found”) is not announced via an ARIA live region. Screen reader users have no indication that the event list has been filtered.
P4-05: ”Get Directions” Form Controls
Severity: Major WCAG SC: 4.1.2 — Name, Role, Value (A)
The ”Uzyskaj wskazówki” (Get Directions) section within event detail panels contains input fields for origin and destination addresses. These inputs lack associated <label> elements or aria-label attributes. The accessible name is derived only from placeholder text, which is insufficient per WCAG requirements.
6. Conformance Statement
Based on the findings documented in this report, the EventOn calendar plugin as deployed at the audited URL does not conform to WCAG 2.2 Level AA. Multiple Level A failures were identified, which precludes any claim of Level A, AA, or AAA conformance. The issues span all four WCAG principles and affect users of screen readers, keyboard-only navigation, voice control, switch devices, and users with low vision.
This report is intended for submission to the EventOn development team via the vendor helpdesk at https://helpdesk.ashanjay.com/. It documents defects only; remediation recommendations are outside the scope of this document and should be addressed by the plugin vendor in accordance with WCAG 2.2 normative requirements and ARIA Authoring Practices Guide (APG) design patterns.
— End of Report —
Reply to: tickets(404267)
Hello.
Sorry, but the translation still isn’t showing up correctly in the tab. If I enable the option to display event tags on the page in the front-end’s classification and filtering section, it doesn’t appear translated correctly on the page.
Reply to: tickets(405453)
Hello Artem
you could check the issue yourself, if you just deactivate the FullCal Plugin and check the homepage with a mobile.
If I change the theme the EventOn is not visible because it is embedded in elements of the theme.
Even if I leave only the plugins for the theme (tagDiv Cloud Library, tagDiv Composer) and the EventOn Plugins active you can see the issue if you scroll fast up and down.
I send you a screenshot.
Reply to: tickets(405497)
Thank you very much for letting us know of this. We are always striving to improve EventON to meet industry standards. With that said, do you have a report of what issues comes up for your website against WCAG compatibility? If you can share that we can directly get those specific items resolved quickly for you.