Accessibility Statement

Last updated: June 2026

Harbinger Tribune is committed to making its website harbingertribune.com accessible to all people, regardless of physical or cognitive impairments, devices used, or assistive technologies. We aim to conform to the Web Content Accessibility Guidelines (WCAG) version 2.1 at Level AA, the internationally recognised standard for digital accessibility. Although Harbinger Tribune does not specifically direct its services at the EU/EEA market and does not consider itself a covered entity under the European Accessibility Act (Directive (EU) 2019/882) on that basis, we aim, as a matter of policy, to align our accessibility practices with its requirements as well, given that our audience includes readers from around the world.

1. Conformance Status

This website is partially conformant with WCAG 2.1, Level AA. Partially conformant means that some parts of the content do not yet fully comply with the accessibility standards. Known limitations and our remediation measures are described in Section 5.

2. Applicable Standards

WCAG 2.1 Level AA — W3C Web Content Accessibility Guidelines
Americans with Disabilities Act (ADA) — for US users, we are committed to making our Website accessible in accordance with Title III of the ADA and applicable case law regarding website accessibility
Section 508 of the Rehabilitation Act — we apply Section 508 standards for electronic and information technology accessibility
EN 301 549 — European accessibility standard for ICT products and services
European Accessibility Act (Directive (EU) 2019/882) — not applicable to us on a targeting basis (see the opening paragraph above), but aligned with voluntarily as a matter of policy

3. Technical Specifications

The accessibility of this website relies on the following technologies:

HTML5 (semantically structured with proper use of landmark elements: header, nav, main, article, aside, footer)
CSS3 (responsive design for all device classes)
JavaScript (progressively enhanced — core content accessible without JavaScript)
WAI-ARIA 1.1 (Accessible Rich Internet Applications)

4. Accessibility Features Implemented

Since July 2026, we also provide an interactive accessibility toolbar: a floating icon in the bottom-left corner of every page opens a panel where you can adjust text size in four steps, switch to a high-contrast display mode, underline all links, reduce animations and motion, and increase line and letter spacing for easier reading. Your selections are stored only in your own browser (never on our servers) and are applied automatically on return visits; a "Reset" button restores the defaults at any time.

4.1 Perceivable (WCAG Principle 1)

Alternative text (WCAG 1.1.1): All images with informative content have descriptive alternative text. Decorative images use empty alt attributes (alt="") so screen readers ignore them.
Captions for video (WCAG 1.2): No videos are currently used. Captions will be provided if video content is introduced.
Resizable text (WCAG 1.4.4): Text can be enlarged to 200% without loss of content or functionality.
Contrast ratios (WCAG 1.4.3): Normal text has a contrast ratio of at least 4.5:1 against the background. Large text has at least 3:1.
Text spacing (WCAG 1.4.12): Content remains accessible when line height is 1.5× font size, paragraph spacing is 2× font size, letter spacing is 0.12× font size, and word spacing is 0.16× font size.
No content that causes seizures (WCAG 2.3): No flashing or strobing content is used.

4.2 Operable (WCAG Principle 2)

Keyboard accessibility (WCAG 2.1): All functionality is operable via keyboard alone.
No keyboard traps (WCAG 2.1.2): There are no areas of the website where keyboard users become trapped.
Skip navigation link (WCAG 2.4.1): A "Skip to main content" link at the top of the page allows keyboard users to bypass navigation.
Page titles (WCAG 2.4.2): Each page has a unique, descriptive title.
Focus order (WCAG 2.4.3): Keyboard focus order follows the logical page structure.
Visible focus (WCAG 2.4.7): Keyboard focus is clearly visible on all interactive elements.
No time limits (WCAG 2.2): There are no time-limited interactions on the website.

4.3 Understandable (WCAG Principle 3)

Language of page (WCAG 3.1.1): The primary language of the website is declared in the HTML element (lang="en").
Consistent navigation (WCAG 3.2.3): Navigation appears in the same position and in consistent order across all pages.
Error identification (WCAG 3.3.1): Where forms exist, error messages are clear and descriptive.

4.4 Robust (WCAG Principle 4)

Valid HTML (WCAG 4.1.1): HTML code conforms to W3C standards.
Name, role, value (WCAG 4.1.2): All UI components have correct ARIA roles, names, and states.
Status messages (WCAG 4.1.3): Status messages are programmatically determined via ARIA live regions.

5. Known Limitations

Despite our efforts, the following known limitations exist:

Older imported articles: Articles imported via the WordPress import system may contain images without alternative text. These are being addressed progressively.
Complex data tables: Some HTML tables embedded in imported articles may lack complete header markup. These are being revised.
External embedded content: If external content (videos, maps) is embedded in the future, the accessibility of that third-party content cannot be fully guaranteed by us.
PDFs: Any PDF documents linked from articles are not guaranteed to be accessible in line with PDF/UA standards.

6. Feedback and Contact

We welcome feedback on the accessibility of our website. If you encounter barriers or need assistance, please contact us:

Email: support@harbingerpressmedia.com
Subject: Accessibility – harbingertribune.com

We will review your request and respond within five working days. We are committed to addressing reported accessibility issues as quickly as possible.

7. EU-Based Readers

Although, for the reasons explained above, we do not consider Harbinger Tribune to be a covered entity under the European Accessibility Act, EU-based readers who are dissatisfied with our response to accessibility feedback may, as a courtesy, contact the national accessibility enforcement body in their EU member state, established pursuant to Art. 27 of Directive (EU) 2019/882.

8. Date of This Statement

This Accessibility Statement was created on 1 June 2026 and will be reviewed and updated regularly.