Create account

Website check

guatzessen.at

Very well set up. Accessibility is at 96 (Excellent). Security is the strongest group at 98.

  • 0 high
  • 2 medium
  • 6 low
  • 14 of 14 pages checked
PDF download comes with Pro, which is not open for sign-up yet.
unchanged since 10 November
97 of 100 Excellent

What helps most

  1. Keyboard focus not visible Medium risk Accessibility
  2. Linked PDF documents are not tagged Medium risk Accessibility
  3. Linked PDF documents declare no language Low risk Accessibility

Result by area

Security

4 findings
Score 98 out of 100 Excellent

Per page: (2 × Transport security + 2 × Protective headers + Cookie attributes + Domain & mail security + Information exposure) / 7. The area is the mean of the 14 checked pages. A check counts when it passed or failed with a finding shown here. What does not apply, stayed uncertain or could not be measured does not count.

Transport security, protective headers, cookie attributes, what the domain and its mail records declare, and what the site gives away about itself.

Transport security

All passed Score 100 out of 100
Show the 17 further checks: Transport security
  • Passed HSTS preload state
    Tests whether the domain is on the browser preload list and whether the header agrees with that state. Evidence: guatzessen.at is on the HSTS preload list (list copy 1 days old)
  • Passed Site reachable over HTTPS
    Tests whether the site opens over an encrypted connection at all, so that what visitors send and receive cannot be read on the way.
  • Passed Redirect from HTTP to HTTPS
    Tests whether a request over unencrypted HTTP is moved onto an encrypted connection.
  • Passed Negotiated TLS version
    Tests which TLS version the browser actually agreed with the server while loading this page.
  • Passed Certificate validity
    Tests whether the certificate is valid right now and not about to expire.
  • Passed Certificate host name
    Tests whether the certificate is actually issued for the host name that was scanned.
  • Passed Certificate trust chain
    Tests whether the certificate can be verified against the public trust store.
  • Passed Certificate key strength
    Tests whether the key in the certificate is long enough to still count as safe.
  • Passed Certificate signature algorithm
    Tests whether the certificate is signed with an algorithm that still counts as safe.
  • Passed Outdated TLS versions
    Tests whether the server still accepts TLS 1.0 or TLS 1.1, versions that count as broken.
  • Passed Current TLS version
    Tests whether the server offers TLS 1.3, the current version of the protocol.
  • Passed Effect of the transport security policy
    Tests whether the transport security policy reaches the browser at all: it only takes effect on the encrypted final page, not on an unencrypted response or on the redirect alone.
  • Passed Lifetime of the HSTS policy
    Tests whether the declared lifetime of the transport security policy is long enough to have an effect.
  • Passed Mixed content
    Tests whether an encrypted page loads any of its own resources over an unencrypted connection.
  • Passed Form submission over HTTPS
    Tests whether the forms on the pages checked send their data to an encrypted address instead of to plain HTTP.
  • Passed Strict-Transport-Security header
    Tests whether the site tells browsers to use HTTPS for every later request, so a connection cannot fall back to an unencrypted channel.
  • Not measurable Cipher strength
    Tests whether the server accepts a connection that uses ciphers which count as weak. This scan did not collect the signal this check needs, so the check is not measurable and earns no points.

Protective headers

1 finding Score 100 out of 100
  • Low risk Cross-Origin-Embedder-Policy is only delivered in report-only mode
    Effort: Low · on /presse Evidence and fix: Cross-Origin-Embedder-Policy is only delivered in report-only mode

    The page sends its embedder policy exclusively as Cross-Origin-Embedder-Policy-Report-Only with the value "require-corp". That variant reports which embedded resource would have been blocked and blocks none of them, so the isolation the policy describes is not in force. This is a different situation from having no policy: the rules exist and are being measured, they are simply not switched on.

    How to fix it

    Once the reports name no resource you still need, deliver the same policy under the enforcing header name:

    Example for nginx
    add_header Cross-Origin-Embedder-Policy "require-corp" always;
    Apache, IIS, Cloudflare and other web servers need the same setting, written in their own syntax.

    Every embedded cross-origin resource has to send CORP or CORS headers before you switch it on.

    Evidence
    What is wrong: the policy is report-only, so nothing is actually blocked
Show the 21 further checks: Protective headers
  • Passed Content-Security-Policy
    Tests whether the page sends a content security policy at all. How far the policy limits which scripts, styles and frames the page may load is judged under "Strength of the content security policy".
  • Passed Value of the Cross-Origin-Opener-Policy
    Tests whether the value actually separates the browsing context instead of naming the browser default under a header name.
  • Passed Value of the Cross-Origin-Resource-Policy
    Tests whether the value restricts who may embed the response instead of allowing every origin.
  • Passed CORS configuration
    Tests whether the site opens its responses to any origin, in particular together with credentials.
  • Passed Cross-Origin-Embedder-Policy header
    Tests whether the page requires embedded resources to opt in before they are loaded.
  • Passed Cross-Origin-Opener-Policy header
    Tests whether the page separates its browsing context from windows it opens and from windows that open it.
  • Passed Cross-Origin-Resource-Policy header
    Tests whether the site states which other origins may embed its resources.
  • Passed Content security policy enforced
    Tests whether the policy is enforced or only reported, because a report-only policy blocks nothing.
  • Passed Delivery of the content security policy
    Tests whether the policy arrives as an HTTP header, which covers more cases than a policy placed in the page markup.
  • Passed Strength of the content security policy
    Tests whether the policy really constrains scripts, instead of letting everything through a broad directive.
  • Passed Permissions-Policy header
    Tests whether access to powerful browser features such as camera, microphone and location is explicitly restricted.
  • Passed Coverage of the Permissions-Policy
    Tests whether the policy actually names the sensitive browser features instead of staying empty.
  • Passed Referrer-Policy header
    Tests whether the site limits which address information is passed on when a visitor follows a link to another site.
  • Passed Strength of the referrer policy
    Tests whether the chosen referrer policy really withholds the address instead of passing the full URL on.
  • Passed Reporting-Endpoints header
    Tests whether the site names an endpoint that browsers can report policy violations to.
  • Passed X-Content-Type-Options header
    Tests whether the response pins the content types it declares, so a browser does not guess a different one.
  • Passed Value of the X-Content-Type-Options header
    Tests whether the header carries nosniff, the only value that has any effect.
  • Passed X-Frame-Options header
    Tests whether other sites are kept from embedding the page in a frame, a common clickjacking indicator.
  • Passed Value of the X-Frame-Options header
    Tests whether the framing rule uses a value that current browsers still honour.
  • Passed X-XSS-Protection header
    Tests whether the site still sends the retired XSS filter header, which current browsers ignore and which used to cause problems of its own.
  • Does not apply Subresource integrity
    Tests whether scripts loaded from other sites carry an integrity hash, so an altered file is not executed. Does not apply to this page: the scan collected the signal, and what this check judges is either not present here or not required for this site.

Cookie attributes

All passed Score 100 out of 100
Show the 4 further checks: Cookie attributes
  • Passed HttpOnly attribute on cookies
    Tests whether cookies are withheld from scripts in the page, which limits what injected script code can read.
  • Passed SameSite attribute on cookies
    Tests whether cookies state whether they may travel on requests that start on another site.
  • Passed Secure attribute on cookies
    Tests whether cookies are marked so that they are only ever sent over an encrypted connection.
  • Does not apply SameSite=None without Secure
    Tests whether a cookie that allows cross-site use is at least limited to encrypted connections. Does not apply to this page: the scan collected the signal, and what this check judges is either not present here or not required for this site.

Domain & mail security

3 findings Score 89 out of 100
  • Low risk DMARC policy only monitors for guatzessen.at

    Once your DMARC reports show only legitimate senders, raise the policy to "p=quarantine" and then to "p=reject".

    Effort: Medium · applies to the whole website Evidence and fix: DMARC policy only monitors for guatzessen.at

    The DMARC record of guatzessen.at carries no enforcing policy: it is set to "p=none" or names no policy at all. That collects reports but instructs receiving servers to deliver forged mail anyway.

    How to fix it

    Once your DMARC reports show only legitimate senders, raise the policy to "p=quarantine" and then to "p=reject".

    Evidence
    Measured value
    none
  • Low risk No MTA-STS policy announced for guatzessen.at

    Publish a TXT record at _mta-sts.guatzessen.at such as "v=STSv1; id=20260101000000" and serve the matching policy at https://mta-sts.guatzessen.at/.well-known/mta-sts.txt.

    Effort: Medium · applies to the whole website Evidence and fix: No MTA-STS policy announced for guatzessen.at

    No MTA-STS record was found at _mta-sts.guatzessen.at. Without it, a sending mail server has no published instruction to insist on an encrypted, authenticated connection to your mail servers, so an attacker on the network path can strip the encryption.

    How to fix it

    Publish a TXT record at _mta-sts.guatzessen.at such as "v=STSv1; id=20260101000000" and serve the matching policy at https://mta-sts.guatzessen.at/.well-known/mta-sts.txt.

    Evidence
    What is wrong: no record was found
  • Low risk No DANE record for the mail servers of guatzessen.at

    Publish a TLSA record under _25._tcp for each mail server of guatzessen.at, derived from its certificate, and renew it before the certificate changes. If your mail provider runs the servers, ask whether it offers DANE.

    Effort: Medium · applies to the whole website Evidence and fix: No DANE record for the mail servers of guatzessen.at

    The mail servers of guatzessen.at sit in a zone signed with DNSSEC, but none of them publishes a TLSA record. A sending server therefore cannot verify the certificate of your mail server and has to accept whichever one is offered.

    Reliability: Measured An unambiguous signal was read directly; only the pages inspected limit the statement. Asks DNS for the TLSA record of every mail server named in the MX records, and only where the zone of that mail server is signed with DNSSEC. The absence of the record is a fact about the zone. Only the first few mail servers are asked. How to fix it

    Publish a TLSA record under _25._tcp for each mail server of guatzessen.at, derived from its certificate, and renew it before the certificate changes. If your mail provider runs the servers, ask whether it offers DANE.

    Evidence
    What is wrong: no record was found
  • Informational At least 1 subdomain of guatzessen.at appears in public certificate logs

    Go through the list and ask for every name whether it should still be reachable in public. Names that are no longer needed belong out of DNS, and where a name has to stay it should carry the same protection as the main site: certificate, headers and updates. Certificate transparency cannot be switched off, so the list is public either way.

    Effort: Low · applies to the whole website Evidence and fix: At least 1 subdomain of guatzessen.at appears in public certificate logs

    Every certificate issued for a name below guatzessen.at is published in the certificate transparency logs, and at least 1 name appears there. The logs are read up to a fixed number of pages, so a very large estate can hold more than the number named here. That is an inventory and not a defect: a large estate is entirely normal, and it costs no points in either direction. It is worth reading because the list also holds what was forgotten, such as an old staging system, a shop that was replaced or the leftovers of a former host. Named here: www.guatzessen.at

    Reliability: Measured An unambiguous signal was read directly; only the pages inspected limit the statement. Reads the names from the public certificate transparency logs of the certificate authorities. A name that appears there really did have a certificate issued for it, so the list is not a guess. It is not complete either: a system without a public certificate, and a name behind a wildcard certificate, never show up in it. How to fix it

    Go through the list and ask for every name whether it should still be reachable in public. Names that are no longer needed belong out of DNS, and where a name has to stay it should carry the same protection as the main site: certificate, headers and updates. Certificate transparency cannot be switched off, so the list is public either way.

  • Informational DKIM selector of guatzessen.at could not be determined

    Nothing to do if your mail provider (w4ymail.at) signs outgoing mail for guatzessen.at. If you are unsure, ask your provider whether DKIM signing is switched on and under which selector the key is published.

    Effort: Low · applies to the whole website Evidence and fix: DKIM selector of guatzessen.at could not be determined

    According to its SPF or MX records, guatzessen.at sends its mail through the following mail providers: w4ymail.at. For none of them does this scan know a selector name under which DKIM keys are published. Besides the common selector names it therefore tried the selectors known from other mail providers and, for each of the names w4ymail, world4you taken from the providers and the DNS zone, the forms NAME, NAME1, NAMEdkim, NAME-dkim, NAME-dkim1, NAME-dkim-0001, NAME-dkim-0002, NAME-dkim-0003, dkim-NAME. None of them carries a key. A key under a selector the provider picked itself stays invisible here, so whether guatzessen.at signs its mail remains open.

    Reliability: Suspicion Inferred indirectly, from free text, labels or the pattern of an answer. This can be wrong in both directions, so check it before acting on it. Reads the mail provider from the SPF includes and the MX records and asks DNS for a DKIM key under the selectors known for that provider, under the common selector names, under the selectors known from other providers and under names formed from the provider, the nameservers and the zone mailbox. A hit is unambiguous. For the provider named here none of them carries a key, a key under a name of its own stays invisible, and nothing is concluded either way. How to fix it

    Nothing to do if your mail provider (w4ymail.at) signs outgoing mail for guatzessen.at. If you are unsure, ask your provider whether DKIM signing is switched on and under which selector the key is published.

    Evidence
    What is wrong: no selector known from the mail providers or derived from their names carries a DKIM key
    Measured value
    w4ymail.at
    Measured value
    w4ymail
    Measured value
    world4you
  • Informational Website not reachable over IPv6

    Ask your hosting provider for an IPv6 address for guatzessen.at and publish it as an AAAA record next to the existing A record.

    Effort: Low · applies to the whole website Evidence and fix: Website not reachable over IPv6

    The host guatzessen.at publishes no AAAA record, so it can be reached over IPv4 only. Visitors on an IPv6-only mobile or business network depend on their provider translating the connection for them.

    Reliability: Measured An unambiguous signal was read directly; only the pages inspected limit the statement. Asks DNS for the AAAA record of the scanned host. The absence of the record is a fact about the zone, not an interpretation. It is not a reachability test: a published address that answers nothing would still count as present. How to fix it

    Ask your hosting provider for an IPv6 address for guatzessen.at and publish it as an AAAA record next to the existing A record.

    Evidence
    What is wrong: no record was found
  • Informational Mail servers not reachable over IPv6

    Ask your mail provider whether the mail servers of guatzessen.at can be reached over IPv6 and have the matching AAAA records published.

    Effort: Low · applies to the whole website Evidence and fix: Mail servers not reachable over IPv6

    None of the mail servers of guatzessen.at publishes an AAAA record, so mail can only be delivered over IPv4. A sending server on an IPv6-only network needs a relay to reach you at all.

    Reliability: Measured An unambiguous signal was read directly; only the pages inspected limit the statement. Asks DNS for the AAAA record of every mail server named in the MX records. The absence of those records is a fact about the zone. Only the first few mail servers are asked, and no connection is attempted. How to fix it

    Ask your mail provider whether the mail servers of guatzessen.at can be reached over IPv6 and have the matching AAAA records published.

    Evidence
    What is wrong: no record was found
Show the 11 further checks: Domain & mail security
  • Passed SPF record (mail domain)
    Tests whether the domain names in DNS which servers are allowed to send mail on its behalf. Evidence: v=spf1 mx include:spf.w4ymail.at a:mail.erseni.com -all (3 DNS lookups)
  • Passed DNSSEC (web zone)
    Tests whether the DNS answers of the zone that serves the website are cryptographically signed. Where the website is an alias (CNAME) of another zone, that zone is tested and the chain is shown with the result.
  • Passed TLS-RPT record (mail domain)
    Tests whether the domain names a place that receives reports about failed mail transport encryption.
  • Passed Nameserver redundancy
    Tests whether the zone is served by more than one nameserver, so a single failing server does not take the website, the mail and every subdomain down at once.
  • Passed Mail servers in the MX records exist
    Tests whether every mail server named in the MX records of the domain exists in DNS. A name the DNS answers with "does not exist" cannot receive mail; a mail server whose DNS gives no answer at all leaves the check unmeasured.
  • Passed Names pointing at an unused hosting account
    Tests whether the scanned address or its www counterpart is directed by CNAME at a hosting platform whose target is free to be claimed, because it resolves nowhere or the platform answers with the page it shows for an unclaimed name. A CNAME onto such a platform is normal by itself and is not reported; only these two observations are.
  • Passed CAA record (web zone)
    Tests whether the zone that serves the website limits in DNS which certificate authorities may issue certificates for it. Where the website is an alias (CNAME) of another zone, that zone is tested and the chain is shown with the result.
  • Passed Reputation of the domain
    Tests whether Google Safe Browsing lists the domain as dangerous, which makes browsers warn visitors before the site opens.
  • Possible risk DKIM key (mail domain)
    Tests whether a DKIM key can be found under one of the common selector names, so outgoing mail can be signed and a forged sender is recognisable, and whether an RSA key there has at least 2048 bits. Only when no name exists under _domainkey at all is the key reported as missing; if something is published there under a selector of your own, the check stays unresolved. This scan looked but could not resolve this check either way. Treat it as a point to verify yourself: it earns its points once a scan confirms it.
  • Does not apply Remaining registration period
    Tests how long the registration of the domain still runs, because an expired domain takes the website, the mail and every subdomain down at once. The date is only readable where the registry serves it over RDAP, which the generic domains do and the country code domains of this market do not; without it the check stays unmeasured and is never counted as a defect. Not counted: no expiry date could be read for this address over RDAP, either because its registry publishes none or because the address is no registered domain. That is no defect of the site, and the check earns no points either way.
  • Does not apply Website answers over IPv6
    Opens a connection to port 443 at up to three published IPv6 addresses of the scanned host until one of them answers. Without an AAAA record the question does not arise and the check stays neutral. Does not apply to this page: the scan collected the signal, and what this check judges is either not present here or not required for this site.

Information exposure

All passed Score 100 out of 100
Show the 10 further checks: Information exposure
  • Passed security.txt
    Tests whether the site publishes a contact point for security reports at the agreed address.
  • Passed Directory contents visible
    Tests whether a directory the page loads its own files from answers with a list of its contents instead of a page. Only directories derived from the resources of the page are asked, no addresses are guessed.
  • Passed Internal information in the markup
    Tests whether the delivered markup contains error output, a directory of the server, an internal network address in a comment or a string with the shape of an access key. The check reads the markup that every visitor receives anyway and reports the kind of the find, never its wording.
  • Passed Technology disclosed in headers
    Tests whether the response names the software, framework or platform behind the site.
  • Passed Server version disclosed
    Tests whether the response names the exact version of the software that serves the site. Evidence: Server header without a version number: erseni
  • Passed Public source maps
    Tests whether the source maps of the own scripts of the page can be downloaded, which hand out the original source code and the server paths of the build.
  • Passed Unusual content on the page
    Tests whether the delivered page contains elements that injected code typically leaves behind: an invisible frame that loads from another site, a script that decodes its own content before running it, or an automatic redirect to another site. Each of these has legitimate uses, so the check reports a pointer to look at rather than a verdict.
  • Passed No directory contents visible on any page
    Runs only in the scan of a whole website and tests the directories of the files every scanned page loads. One directory that lists its files fails the website, because further pages bring further directories such as uploads or plugins.
  • Possible risk Age of the software in use
    Tests whether the products the page names about itself, such as the content management system, the web server or a JavaScript library, are behind their current release. The check reads only what the page discloses of its own accord and reports nothing when no version is visible or the release reference is too old to judge against. A version built by a Linux distribution stays open, because the distribution brings security fixes into it without changing the number. The same holds for a build that another vendor, such as the content management system, has adapted and marked with a suffix behind the version number. A library loaded from a public CDN such as unpkg, jsDelivr or cdnjs is read off its address; where no release reference covers it and the vulnerability database lists nothing for its version, the check stays open as well. A self-hosted library is named by its file hash, its signatures, its licence head or the global it creates, whatever the file is called; one that is recognised but states no version keeps the check open, because its age cannot be judged. This scan looked but could not resolve this check either way. Treat it as a point to verify yourself: it earns its points once a scan confirms it. Evidence: gsap 3.15.0, no release data to judge this version against
  • Does not apply Maintenance of the server platform
    Tests whether the server banner points to an operating system release or an OpenSSL line whose maintenance has ended. Only a banner that pins the release down is judged; where it names neither, the check reports nothing. Does not apply to this page: the scan collected the signal, and what this check judges is either not present here or not required for this site.

Accessibility

4 findings
Score 96 out of 100 Excellent

Per page the score of Accessibility (automated checks). The area is the mean of the 14 checked pages. A check counts when it passed or failed with a finding shown here. What does not apply, stayed uncertain or could not be measured does not count.

How usable the site is with a keyboard, a screen reader, or reduced vision.

Accessibility (automated checks)

4 findings Score 96 out of 100
  • Medium risk Keyboard focus not visible

    Give every focusable element a clearly visible focus style, for example an outline, and do not remove the browser focus outline without a replacement.

    Effort: Medium · on 4 of 14 pages: /auszeichnungen-preise, /presse, /kochakademie and 1 more Evidence and fix: Keyboard focus not visible

    Of 147 elements reached with the Tab key, 21 looked exactly the same with and without focus. Visitors who navigate by keyboard cannot see where they are on the page.

    Affected elements a.mb-2 a a#logo "Guat'z Essen, zur Startseite" and 18 more How to fix it

    Give every focusable element a clearly visible focus style, for example an outline, and do not remove the browser focus outline without a replacement.

  • Medium risk Linked PDF documents are not tagged

    Export the documents as tagged PDF (PDF/UA) from the authoring program, or tag them afterwards and check the reading order.

    Effort: Medium · on /presse Evidence and fix: Linked PDF documents are not tagged

    2 of 2 linked PDF documents that were read carry no tag structure. Without tags a screen reader cannot tell headings, lists, tables and reading order apart and reads the document as one stream of text.

    How to fix it

    Export the documents as tagged PDF (PDF/UA) from the authoring program, or tag them afterwards and check the reading order.

  • Low risk Linked PDF documents declare no language

    Set the document language in the authoring program or in the document properties before exporting the PDF.

    Effort: Medium · on /presse Evidence and fix: Linked PDF documents declare no language

    2 of 2 linked PDF documents that were read declare no document language. A screen reader then reads the text with the pronunciation rules of whatever language its user has set.

    How to fix it

    Set the document language in the authoring program or in the document properties before exporting the PDF.

  • Low risk Linked PDF documents show no document title

    Enter a meaningful title in the document properties and set the option to show the document title instead of the file name when the PDF opens.

    Effort: Medium · on /presse Evidence and fix: Linked PDF documents show no document title

    2 of 2 linked PDF documents that were read either have no title or do not tell the viewer to show it, so the window shows a file name instead of a title.

    How to fix it

    Enter a meaningful title in the document properties and set the option to show the document title instead of the file name when the PDF opens.

Show the 19 further checks: Accessibility (automated checks)
  • Passed Accessibility statement present
    Tests whether the site links to an accessibility statement. Public bodies and, since the accessibility act, many businesses have to publish one; if it is missing, add a page that names the state of conformity and a contact option for barrier reports.
  • Passed Description of the service
    Tests whether the accessibility information describes the service the website offers and how it is carried out. The BFSG expects this general description as part of the accessibility information; a statement of a public body under the BITV does not need it, there the check does not apply.
  • Passed How the requirements are met
    Tests whether the accessibility information describes how the service meets the accessibility requirements, with the standard and the measures behind it. The BFSG expects an explanation, not only a claim; a statement of a public body under the BITV does not need it, there the check does not apply.
  • Passed Market surveillance authority named
    Tests whether the accessibility information names the market surveillance authority responsible for the provider, in Germany the MLBF. The BFSG expects it to be named; a statement of a public body under the BITV does not need it, there the check does not apply.
  • Passed Automatically detectable barriers
    Tests how many of the automated rules the page breaks, for example missing text alternatives, unlabelled controls or too little contrast. Each violation is a concrete place in the markup that can be repaired.
  • Passed Automatically detectable barriers on a narrow screen
    Runs the automated rules a second time at a width of 320 pixels, where many sites switch to their mobile layout, and reports only what the desktop run did not already find. Collapsed menus and mobile controls often break the same WCAG rules as the desktop view, for example 4.1.2 (name, role, value).
  • Passed Focused element not hidden
    Tests whether an element that receives keyboard focus within the visible area sits completely under a fixed header, a banner or another layer (WCAG 2.4.11 focus not obscured). An element that receives the focus outside the visible area is reported under "Keyboard focus visible".
  • Passed No keyboard trap
    Tests whether the Tab key always moves the focus on. An element that keeps the focus locks keyboard users out of the rest of the page (WCAG 2.1.2 no keyboard trap).
  • Passed Moving content can be paused
    Tests whether videos and animations that start on their own and run longer than five seconds can be paused or stopped. Constant motion makes it hard for many people to read the rest of the page (WCAG 2.2.2 pause, stop, hide).
  • Passed Reduced motion respected
    Tells the page that the visitor prefers reduced motion and tests whether its animations stop. People who react to motion with dizziness set this preference in their system (WCAG 2.3.3 animation from interactions).
  • Passed No accessibility overlay
    Tests whether the page loads an overlay widget that promises accessibility as an add-on. An overlay does not repair the markup, does not satisfy the accessibility act and can get in the way of the assistive technology visitors already use.
  • Passed Readable on a narrow screen
    Tests whether the content reflows into a narrow window instead of forcing the visitor to scroll sideways. People who enlarge the page or use a small screen otherwise lose part of the text on every line.
  • Passed Accessibility statement reachable from every page
    Runs only in the scan of a whole website and tests whether every scanned page links the accessibility statement. The statement has to be reachable from every page, not only from the start page.
  • Does not apply Feedback option in the statement
    Tests whether the accessibility statement names a way of reporting a barrier, for example a mail address, a form or a telephone number. Name a contact person plainly in the statement. Does not apply to this page: the scan collected the signal, and what this check judges is either not present here or not required for this site.
  • Does not apply State of conformity in the statement
    Tests whether the accessibility statement says how far the site meets the requirements, that is fully, partially or not at all, and against which standard. Without that sentence the statement does not say what visitors can expect. Does not apply to this page: the scan collected the signal, and what this check judges is either not present here or not required for this site.
  • Does not apply Known barriers listed in the statement
    Tests whether the accessibility statement names the parts that are not accessible yet. Listing them honestly, together with the reason and an alternative, is part of a complete statement. Does not apply to this page: the scan collected the signal, and what this check judges is either not present here or not required for this site.
  • Does not apply Date of the last review
    Tests whether the accessibility statement carries the date on which it was drawn up or last reviewed. Without a date nobody can tell whether it still describes the current site; review it regularly and record the date. Does not apply to this page: the scan collected the signal, and what this check judges is either not present here or not required for this site.
  • Does not apply Enforcement procedure in the statement
    Tests whether the accessibility statement names the supervisory or arbitration body a visitor can turn to when a barrier report gets no answer. Name the body that is responsible for you, with its contact details. Does not apply to this page: the scan collected the signal, and what this check judges is either not present here or not required for this site.
  • Does not apply Reasons for the known barriers
    Tests whether the accessibility statement says why the parts it names are not accessible, for example a disproportionate burden, or offers an accessible alternative for them. A barrier listed without a reason leaves visitors without a way around it. Does not apply to this page: the scan collected the signal, and what this check judges is either not present here or not required for this site.

Not part of the scan at the moment, so not scored: Data protection, Legal obligations, Quality & technology, Trust & transparency

How the score is calculated

The checked pages

14 of 14 pages found are checked. The findings are listed above with their area.

  • /kontakt

    Page score 99 of 100
    Security
    98
    Accessibility
    100
  • /barrierefreiheit

    Page score 99 of 100
    Security
    98
    Accessibility
    100
  • /datenschutz

    Page score 99 of 100
    Security
    98
    Accessibility
    100
  • /impressum

    Page score 99 of 100
    Security
    98
    Accessibility
    100
  • /tisch-reservieren

    Page score 99 of 100
    Security
    98
    Accessibility
    100
  • /unser-genusserlebnis

    Page score 99 of 100
    Security
    98
    Accessibility
    100
  • /staff

    Page score 99 of 100
    Security
    98
    Accessibility
    100
  • /auszeichnungen-preise

    Page score 95 of 100
    Security
    98
    Accessibility
    90
  • /peter-fankhauser

    Page score 99 of 100
    Security
    98
    Accessibility
    100
  • /presse

    Page score 90 of 100
    Security
    98
    Accessibility
    73
  • /news

    Page score 99 of 100
    Security
    98
    Accessibility
    100
  • /kochakademie

    Page score 95 of 100
    Security
    98
    Accessibility
    90
  • /gerichte

    Page score 99 of 100
    Security
    98
    Accessibility
    100
  • /

    Page score 96 of 100
    Security
    98
    Accessibility
    92

Show this result on your website

A seal with the score and a link to this report, to put on your website.

Copy the code and paste it where the seal should appear. The seal loads from scan.erseni.com, add it to your privacy policy as a recipient.

Code for your website Code for the image

Check the whole website

We found 14 addresses on guatzessen.at. Without an account we check the address you entered, the domain, the host and the mandatory pages of this website. With a free account you check every further page of the website as well, and every result adds to this website result.

Sign up for free Sign in
Scan again
Scan another website Compare with earlier scan Accessibility statement
This website report brings together every checked page of https://guatzessen.at/: the start page, the mandatory pages and every further page that was scanned. Domain and host checks hold once for the whole website, page checks say on how many pages they hold, and every finding names the pages it was found on. How to read this report Every score runs from 0 to 100. Colours follow three bands: 80 and above is green, 50 up to 80 is amber, anything below 50 is red. Ranks: Legendary 100 · Excellent 90-99 · Strong 80-89 · Solid 65-79 · Needs work 50-64 · Weak 25-49 · Critical 0-24 The colour shows the broad band a score falls into, the rank places it more precisely within that band. Legendary needs every check that could be judged to have run; a score of 100 with checks left open is Excellent. Every check belongs to exactly one category and every category to exactly one group. A category gives up to 100 points, fixed per check; a check earns its points only when it passes on the whole website or there is nothing to check. A group is the mean of its categories, some of which count twice, and carries this share of the score: Security 67%, Accessibility 33%. The score is the mean of the groups shown above, a group with factor 2 counting twice. A single weak check therefore only moves the figure through its category and group, and can sit well below the score. Findings are grouped by category, with the category that needs the most attention first. Open a category to see its findings, ordered by risk: “High risk” first, then “Medium risk”, “Low risk” and purely informational notes. Several categories can be open at the same time. Effort estimates how much work a fix typically takes: “Low” is a quick configuration change, “Medium” needs development time, “High” means a larger project.

Product

Learn

Legal

Cancel contracts here Withdraw from contract © 2026 Erseni