Zum Inhalt springen

Accessibility

Statement

Status: March 19, 2026

The Austrian Research Centre for Forests (BFW) is committed to making its website accessible in accordance with the Federal Act on Barrier-Free Access to Websites and Mobile Applications of Public Sector Bodies (Web Accessibility Act – WZG), as amended, implementing Directive (EU) 2016/2102 of the European Parliament and of the Council of October 26, 2016 on the accessibility of the websites and mobile applications of public sector bodies (OJ L 327, 2.12.2016, p. 1).

This accessibility statement applies to the website www.bfw.gv.at.

Tested (the entire website was tested):

  • Homepage
    • Main menu/navigation + submenu
    • Cookie banner
    • Search
    • Search results
  • 43 main pages + 20 department pages
  • 20 department pages
  • All article/post templates
  • One sample page for each article/post type (5 pages)
  • English version (identical to the German version; therefore only spot checks were carried out in English here: main menu/navigation + submenus, homepage, main pages, posts, and spot checks of additional pages)

Accessibility testing tools used and results after a comprehensive revision with regard to WCAG 2.1 AA:

QualWeb

(ACT Rules + WCAG Techniques, A/AA)
All pages and all website extensions were tested in full
✅ 0 Failures

Axe (axe™)

WCAG2A/2AA: 50 real WordPress pages (all templates, every post type, and all main menu pages)
✅ 0 Violations

Lighthouse

A full website audit resulted in 100/100 on all pages except 2 (2 exceptions = WCAG 2.2 / but false positives, therefore here as well ✅ 0 actual violations)

color.a11y.com/Contrast/

Manual tests were also carried out regarding navigation, focus, and contrast. Noticeable contrast weaknesses were additionally rechecked with the color.a11y Contrast Checker alongside the automated tools. Result with regard to WCAG 2.1 AA: ✅ 0 Violations

achecker.ca

Additional spot checks were also carried out here, all of which resulted in ✅ 0 Violations.

1. Non-accessible content

1.1 Conformance status

The website www.bfw.gv.at fully conforms to the requirements of the Web Accessibility Directive (EU) 2016/2102 in conjunction with WCAG 2.1, Conformance Level AA.

All tested pages and templates meet all WCAG 2.1 success criteria at Levels A and AA. The remaining limitations described below relate exclusively to the voluntary AAA level (going beyond the legal obligation), known tool misjudgments (false positives), and legacy editorial content (PDFs and h1-h6 heading structures in older posts).

1.2 Remaining limitations at AAA level (not required for AA)

1.2.1 Enhanced color contrast (WCAG 1.4.6 / QW-ACT-R76)

Affected: approx. 15 page templates and one post template (single posts)
Rule: QualWeb ACT-R76 – corresponds to WCAG 2.1 Success Criterion 1.4.6 “Contrast (Enhanced)”, Conformance Level AAA
Description:
On some pages, text colors are used that do not achieve the enhanced contrast ratio of 7:1 (AAA requirement) in all areas. The minimum contrast ratio of 4.5:1 according to WCAG 1.4.3 (AA) is met on all affected pages. This limitation concerns only the optional AAA level and therefore does not constitute a conformance gap under WCAG 2.1 AA.

Legal relevance: The obligation under the Web Accessibility Directive (EU) 2016/2102 relates to WCAG 2.1 AA. This point is therefore not reportable.

1.2.2 Abbreviations without an <abbr> element on event detail pages (WCAG 3.1.4 / QW-WCAG-T7)

Affected: Individual event detail pages (generated by the third-party plugin Modern Events Calendar)
Rule: QualWeb WCAG-T7 – corresponds to WCAG 2.1 Success Criterion 3.1.4 “Abbreviations”, Conformance Level AAA
Description:
On event detail pages, abbreviations (e.g. academic titles, technical terms) may appear without the HTML element <abbr title=”…”>, which would provide screen reader users with an expanded form. The content on these pages is generated fully automatically by the plugin; individual <abbr> markup would require deep intervention in the plugin or extensive manual post-processing of each entry.

For users without assistive technologies, all content is fully understandable; screen readers can also read the text content correctly.

Legal relevance: No conformance gap under WCAG 2.1 AA.

1.3 Limited findings of two testing tools (no actual barriers)

On two pages, the testing tool Google Lighthouse shows deductions from the maximum score of 100/100 which, after detailed analysis, were classified as technical misjudgments by the tool (false positives):

Page /fachinstitute/waldwachstum-waldbau-genetik/waldbau/ – Lighthouse 96/100

Lighthouse reports button/link target sizes as too small under the target-size rule.

Assessment: This rule corresponds to WCAG 2.5.8 “Target Size (Minimum)”, which is included exclusively in WCAG 2.2 (not WCAG 2.1). Direct measurements via browser dev tools showed an actual height of 26 px – meaning the minimum requirement of 24 × 24 px according to WCAG 2.5.8 is met. The discrepancy is caused by a known artifact of Lighthouse’s headless rendering environment for tel: and mailto: links.

Axe WCAG2A/WCAG2AA: 0 Violations on this page.

Conclusion: No action required under WCAG 2.1 AA. No actual barrier.

Page /gesellschaft-internationales/green-care-wald/ – Lighthouse 92/100

Lighthouse reports the color combination #8c6a0d (foreground) on #3f7381 (background) with a contrast ratio of 1.05:1.

Assessment: A review of all parent elements via window.getComputedStyle showed that all backgroundColor values are transparent (rgba(0,0,0,0)) and that the actual background is white (#ffffff). The actual contrast of #8c6a0d on white is approx. 4.77:1 and therefore meets WCAG 1.4.3 AA (minimum requirement: 4.5:1), and thus also WCAG 2.1 AA.

Lighthouse does not correctly traverse transparent backgrounds in its headless rendering environment; this is a known Lighthouse false positive. Axe WCAG2A/WCAG2AA (contrast rule isolated): 0 Violations on this page.

In addition, target-size (WCAG 2.5.8 / WCAG 2.2) is also reported here – likewise no action required under WCAG 2.1.

Conclusion: No actual barrier, no WCAG 2.1 AA conformance gap. In practice, these two pages, like all the others, should therefore also achieve an ideal Lighthouse score of 100.

1.4 Older PDFs and legacy editorial content

For older PDF documents that were published on www.bfw.gv.at before the systematic accessibility review, as well as for editorial posts from earlier periods, full compliance with all WCAG 2.1 AA criteria cannot be guaranteed. This particularly concerns the correct order and hierarchy of headings (heading order), which may deviate from the specification in some older posts.

In older posts, heading sequences may occasionally not strictly follow h1-h6 order and may also appear unordered; secondly, older PDFs may still be included there. Older PDFs are generally exempt because, due to the large number of older PDFs, revision is not possible or not economically reasonable.

All administrators and editors of BFW have been explicitly instructed to comply with WCAG 2.1 AA requirements when creating future content. Newly created posts, pages, and uploaded documents should therefore be fully conformant. Older content will also be updated for accessibility during its next substantive revision.

1.5 External content / third-party systems

Affected: Page /waldwissen-forschung/bfw-projektdatenbank/
An embedded external iframe (bfw.ac.at/rz/pip.startseite, project database) lies outside the direct sphere of influence of the BFW website (cross-origin third-party system). Content and functionality of this embedded system may in some areas deviate from the accessibility standards of the main website. The iframe itself is correctly marked up with a descriptive title attribute (WCAG 4.1.2 AA).

1.6 Issues resolved during the 2026 accessibility audit

As part of a comprehensive technical review and revision, the following issues were identified and fully resolved:

  • 1 | WCAG 4.1.2 / ACT-R13 | Level A
    aria-hidden="true" containers with focusable child elements (Borlabs/AJAX context)
    Measure: Focus management and hidden-state logic hardened
    Status: ✅ fixed
  • 2 | WCAG 2.1.1 / ACT-R43 | Level A
    Scrollable main section (#right-part) not reachable in sequential keyboard navigation
    Measure: Added a tabindex attribute, aria-label, and HIDDEN_ONLY_SCROLL_REGION logic; verified on 224 URLs
    Status: ✅ fixed
  • 3 | WCAG 1.3.1 / WCAG-T17 | Level A
    Incorrect label positioning and association in search form fields
    Measure: Standardized labels, for/id associations, and semantic form structure
    Status: ✅ fixed
  • 4 | WCAG 3.2.2 / WCAG-T19 | Level A
    Form (event filter) without a valid submit mechanism
    Measure: Ensured a correct button[type=submit] element
    Status: ✅ fixed
  • 5 | WCAG 1.3.1 / WCAG-T3 | Level A
    fieldset groups without a meaningful legend element
    Measure: Added legend elements (optionally visually hidden via sr-only)
    Status: ✅ fixed
  • 6 | WCAG 2.5.3 / ACT-R30 | Level A
    Visible link text not contained in the accessible name (aria-label vs. textContent mismatch)
    Measure: Corrected aria-label values via wp_strip_all_tags() to exactly match the visible text
    Status: ✅ fixed
  • 7 | WCAG 2.4.4 / WCAG-T20 | Level A
    Redundant title attributes on links (link text = title, repeated wording)
    Measure: Removed redundant title attributes
    Status: ✅ fixed
  • 8 | WCAG 4.1.2 / Axe aria-allowed-role | Level A
    Invalid ARIA role on a slider element (careers page)
    Measure: Restored a valid role/element combination
    Status: ✅ fixed
  • 9 | WCAG 1.3.1 / Axe landmark-contentinfo-is-top-level | Level A
    contentinfo landmark (breadcrumb) nested inside another landmark
    Measure: In header.php: changed role=”contentinfo” to role=”navigation” on the breadcrumb element
    Status: ✅ fixed
  • 10 | WCAG 1.3.1 / WCAG-T32 | Level A
    <li>/<dd>/<dt> elements not inside proper list containers
    Measure: Corrected list markup in affected templates
    Status: ✅ fixed
  • 11 | WCAG 1.4.4 + 1.4.5 / WCAG-T28 | Level AA
    Absolute font-size values with !important prevent text scaling on numerous pages (including event, FAST, menu, and content pages)
    Measure: Converted all absolute font-size values with !important to relative units or scalable values; verified on 63 URLs
    Status: ✅ fixed
  • 12 | WCAG 1.4.3 / Axe color-contrast | Level AA
    Newsletter form: opacity: 0.8 reduced contrast to 3.9:1 (< 4.5:1 AA minimum)
    Measure: _style.scss: opacity: 1 on #newsletter.separator → contrast 5.1:1
    Status: ✅ fixed
  • 13 | WCAG 1.4.3 / WCAG-T31/F24 | Level AA
    Inline color color:#447681 without a background-color declaration (ACF field Projects & Research)
    Measure: Added background-color: #fff to the inline style
    Status: ✅ fixed
  • 14 | WCAG 1.4.3 / WCAG-T31/F24 | Level AA
    WP Custom CSS: color: #EAFAD1 on #secondary-menu without background color, contrast 4.15:1
    Measure: WP Custom CSS: color: #fff; background-color: #447681 (contrast 4.56:1)
    Status: ✅ fixed
  • 15 | WCAG 4.1.2 / Axe frame-title | Level A
    External <iframe> (BFW project database) without a title attribute
    Measure: Added title=”BFW Project Database: Overview of Current and Completed Research Projects”
    Status: ✅ fixed
  • 16 | WCAG 1.3.1 / Lighthouse heading-order | Level A
    Heading hierarchy H1 → H5 (skip) on page /das-bfw/
    Measure: Corrected the H5 block to H2
    Status: ✅ fixed
  • 17 | WCAG 4.1.1 / WCAG-T35 | Level A
    Duplicate ID Ebene_1 in an SVG element (Social Forestry Work page)
    Measure: Renamed the second SVG ID to Ebene_1_grid
    Status: ✅ fixed
  • 18 | WCAG 1.4.3 / ACT-R37 | Level A
    Contrast warning on an sr-only submit button (events)
    Measure: Added visibility: hidden to the sr-only submit button
    Status: ✅ fixed
  • 19 | WCAG 4.1.2 / ACT-R35 | Level A
    Empty <h1> element without an accessible name (Advisory Board page)
    Measure: Added get_the_title() to the hidden H1
    Status: ✅ fixed
  • 20 | WCAG 2.5.8 / Axe target-size (WCAG 2.2, voluntary) | Level AA*
    Search form button: clickable area 23.4 × 25.4 px (< 24 × 24 px according to WCAG 2.5.8)
    Measure: _search.scss: min-width: 24px; min-height: 24px → button ≥ 24 × 24 px
    Status: ✅ voluntarily fixed

*) WCAG 2.5.8 is included exclusively in WCAG 2.2 and is not part of the legal WCAG 2.1 AA obligation. The measure was implemented voluntarily as a best practice.

2. Preparation of this accessibility statement

2.1 Assessment methodology

The accessibility audit was carried out by the Austrian Research Centre for Forests (BFW) as a self-assessment. No external certificate was requested; the review was conducted independently through internal technical testing using established testing tools, as well as manual verification and external IT and web experts from subsolutions.newmedia.

2.2 Testing tools used

  • QualWeb (ACT Rules + WCAG Techniques, both via CLI and AI tests, plus a complete page-by-page online manual test via https://qualweb.di.fc.ul.pt/)
    Automated rule testing according to WCAG 2.1 A/AA (ACT rules + WCAG techniques)
    Scope of use: All pages and templates; direct execution via Node.js CLI
  • A XE / axe™ (via Playwright, WCAG2A/WCAG2AA, and additionally via Chrome extension during manual testing)
    Automated accessibility testing, including contrast, ARIA, and landmark structure
    Scope of use: 50 real WordPress pages; including isolated contrast scans. Plus all pages were also checked manually with the Chrome extension.
  • Google Lighthouse (automated audits with v13.0.3, accessibility mode via CLI, and additionally via Chrome extension during manual testing)
    Score-based overall assessment
    Scope of use: All pages; results 96–100/100 (actually all 100/100, except for 2 false positives)
  • Manual testing (Playwright: keyboard and mouse smoke tests)
    Keyboard navigation (open/close menu, Escape, focus return, AJAX navigation), mouse control
    Scope of use: All pages, all content (just not every single post, because the template is always the same and there are too many posts; see above)

2.3 Scope of the audit

The audit covered all pages and content of www.bfw.gv.at, including:

  • Homepage
  • All main navigation items (News, About BFW, Research Institutes, Society & International Affairs, Education & Training, Forest Knowledge & Research, Events, Services & Products)
  • All page templates: Blog/News, Press, Research Institute, Department, Staff, Publications, Events + event details, Careers, Locations & Contact, Search, Project Database, Advisory Board, and more
  • Representative individual posts (press release, article, product, event detail)
  • German- and English-language pages
  • and much more

The audit was carried out locally (staging environment) and, for verification purposes, also on the live environment www.bfw.gv.at.

2.4 Date of the last substantive update of this statement

March 19, 2026

3. Further steps to improve accessibility

The Austrian Research Centre for Forests (BFW) considers digital accessibility an ongoing task and has initiated the following measures to ensure and further improve accessibility in a sustainable manner:

3.1 Editorial quality assurance for new content

All administrators and editors of www.bfw.gv.at have been instructed to comply with WCAG 2.1 AA requirements when creating new posts, pages, and documents. Particular emphasis is placed on:

  • correct heading hierarchy (no skipped heading levels in heading order)
  • meaningful alternative text for images
  • accessible design of uploaded documents (especially PDFs)
  • sufficient color contrast in editorially added content

3.2 Revision of legacy content

Older posts and documents published before the systematic accessibility review will be updated for accessibility during their next substantive revision as part of regular maintenance. Priority review is planned for content that is accessed particularly frequently.

3.3 Improvement of the contrast level to AAA standard (voluntary)

On approx. 15 page templates and one post template, color combinations are used that meet the WCAG 2.1 AA minimum contrast ratio (4.5:1) but do not in all areas achieve the optional AAA value (7:1 according to WCAG 1.4.6). As part of the ongoing visual development of the website, BFW is examining whether a gradual move toward AAA contrast values is possible without impairing the visual identity of the site.

3.4 Review and markup of abbreviations (voluntary, AAA)

On event detail pages, abbreviations are output by the third-party plugin used (Modern Events Calendar) without <abbr> markup (WCAG 3.1.4, Level AAA). BFW is examining whether a technical solution can be developed at plugin or theme level to enable automatic or manual markup of abbreviations in the future.

3.5 Ongoing quality assurance during further development

With every significant technical enhancement of www.bfw.gv.at (new templates, structural changes, plugin updates), accessibility audits are carried out as an integral part of the development and approval process. The audit basis includes QualWeb (ACT Rules + WCAG Techniques), Axe, and Google Lighthouse, supplemented by manual spot checks.

3.6 Accessible PDFs

Newly uploaded PDF documents should comply with the requirements of WCAG 2.1 and/or the PDF/UA standard. For older archived documents, a risk-based prioritization approach is applied: documents with high access frequency or particular relevance to the public are prioritized for revision.

This statement applies to the website https://www.bfw.gv.at (Austrian Research Centre for Forests – BFW).
Created: March 18, 2026 · Last updated: March 18, 2026

4. Feedback and contact details

The offers and services on this website are continuously being improved, replaced, and expanded. Usability and accessibility are of great importance to us.

If you notice barriers that hinder you in using our website – problems that are not described in this statement, or deficiencies regarding compliance with accessibility requirements – please let us know by email. We will review your request and contact you as soon as possible.

Please describe the problem as precisely as possible and always provide the URL(s) of the affected webpage or document.

4.1 Contact

Please send all messages and suggestions directly to the webmaster of this website or the BFW Press Office.

4.2 Enforcement procedure

If you are not satisfied with the response you receive via the contact option above, you may submit a complaint to the Austrian Research Promotion Agency (FFG). The FFG accepts complaints electronically via the contact form on the FFG website.

Contact form of the complaints office

These complaints are examined by the FFG to determine whether they relate to violations of the provisions of the Web Accessibility Act, in particular deficiencies in compliance with accessibility requirements, by the federal government or an institution attributable to it.

If the complaint is justified, the FFG must propose recommendations and measures to the federal government or the relevant legal entities in order to remedy the deficiencies concerned.

Further information on the complaints procedure