See Standards & agreements

Accessibility of websites and online documents

The University of Twente works hard to make its websites and (online) documents as accessible as possible. As an organisation that is partly state funded, we are very much aware that we serve the public interest. In your role as an administrator of the university’s web pages, this is something of which you should also be aware.

Definition Accessibility

To offer services and information in a way that it's usable for anyone, regardless of any disability.

Why do we need regulations on accessibility?

By applying the government’s digital accessibility guidelines (Digitoegankelijk), websites and web applications (online office documents included) become accessible to the general audience (citizens, companies and other governments), employees and students. People with chronical (e.g. from colour blindness blindness, hearing loss to deafness, several forms of autism) temporary (e.g. broken arm) or situational disabilities (e.g. play audio in the train) can have the same access to government information as people without these limitations.

As an organisation governed by public law, which serves the public interest and falls under the provisions of the General Administrative Law Act, the University of Twente must also comply with the Accessibility of Websites and Apps (Temporary Measures) Decree. (See also Article 1 of the Decree: – in Dutch only – which came into force on 1 July 2018).

What's it all about?


The definitions (see above link) contain the elements which must comply with the rules of the Decree. These cover all content: the entire body of information that an organisation wishes to transmit on a website or app, including text, downloadable documents, forms and interactive elements, such as the processing of digital forms and the completion of identification procedures. Article 2 of the Decree lists those elements which are NOT covered by the rules of the Decree.


A phased approach has been taken to implementation: see Article 6 of the Decree.

  • Websites published from 23 September 2018 are required to comply by 23 September 2019.
  • Websites published before 23 September 2018 are required to comply by 23 September 2020.
  • Apps have to meet the criteria no later than 23 June 2021.

Office documents on websites published before 1 January 2015 do not have to be made accessible. Documents published online between 1 January 2015 and 23 September 2018 do have to meet the accessiblity guidelines but only if the text describes a current administrative process. As from 23 September 2018 it is mandatory to publish accessible documents only.

In this respect, no distinction is made between internal (intranet) documents and external documents. 

Comply or explain

Paragraphs 2-4 of Article 3 offer the option of refraining from applying standard EN 301 549 if this presents disproportionate problems for the organisation. You can invoke this option if you are convinced that the expected benefits of applying the standard are outweighed by the organisational or financial costs involved. In our accessibility statement, we refer to the large number of managers (over than 1000) and the same number of websites. From an organisational perspective, this situation ensures that the University of Twente cannot guarantee complete accessibility despite its best efforts.

Most important tips


Information on the website (and therefore also in Office documents online) must always be Perceivable, Operable, Understandable and Robust (POUR).

POUR in WebHare

  • Perceivable
    • Add Alternative text to images
    • Embed videos with subtitles (Vimeo and YouTube)
    • Colour contrast (yellow and light pink are too light for buttons)
    • Size contrast (buttons have a certain minimum size so that people with limited motor skills (e.g. due to illness or medication) can click them easily)
    • Forms: fieldsets, questions contain description on the left (Name:) and input field on the right
  • Operable
    • Structure: Always a title, heading 1, continue with heading 2
    • Webpages can be used with keyboard
    • No flashy images
    • Find information via the navigation menu, sitemap, search engine, quicklinks
  • Understandable
    • Language (EN/NL/DE)
    • Consistent navigation (always in the menu, hyperlinks on the page itself, folder (+) or file (>))
    • Interaction design (colour button changes when using, required form fields)
  • Robust
    • Websites can be visited with different devices (desktop, smartphone, tablet, etc.), browsers (Chrome, Internet Explorer, Edge, Safari, etc.)

what website editors can do

  • Publisher (WebHare)
    1. Remove what is no longer relevant.
      Otherwise you run the risk that the page the user is searching for will be difficult to find, especially if there are many similar documents or older versions on the website. Do you prefer not to delete any pages? Do not put the pages offline, but archive them on your computer.
    2. Web page or office document?
      Can't decide between the two? Use a web page.
    3. Only use the features of WebHare
      Only use the elements offered in Webhare and do not create your own menus and buttons. 
    4. Alternative text to images
      Photos on websites should always come with a description, so that users with a visual impairment can find out the content of the photo because their screen reader tells them what the text says.
    5. Add subtitles to videos
      Always provide subtitles for videos content for people that cannot turn up volume when watching. YouTube and Vimeo both offer a simple tool to add subtitles.
    6. Hyperlinks
      1. Always open links in the same screen (and same tab) to avoid any problems with support programs. (If users want to open links in a new screen they can do this themselves by right-clicking).
      2. Put a link behind the description of the page where you are linking to.
        E.g. Go to the English website instead of Click here
    7. No documents in navigation menu
      Do not list downloadable files in a website menu. If you want users to download files, it is best to provide this information in an accompanying sentence on screen. There are two ways of doing this:
      1. Option 1 (preferred): Use the website component Download/Links (available as inline component or widget).
      2. Option 2: Save the downloadable file without a title in a folder in the Publisher and refer to it using a link. 
    8. Always add a title to a page (file).
      Make sure that every page on the website is visible in the menu as well. Otherwise it is not clear for users where they are on the website and how they are able to navigate through different levels.
    9. Prevent tables
      Tables do not work well on small screens. When you need a table, do not make them too wide (preferably a maximum of 4 columns). 
  • Office documents

    Quick wins

    1. Do not put the following office documents online:
      1. Scanned documents
        Pixelated, text cannot be read by a screenreader
      2. Badly designed documents
        Lack of elements visual identity, no uniformity, no contrast
      3. Documents meant for printing
        Crop marks, more info than needed
      4. Automatically converted PDFs
        Structure unknown, no alternative text to images, no bookmarks
    2. Remove what is no longer relevant
      Otherwise you run the risk that the document the user is searching for will be difficult to find, especially if there are many similar documents or older versions on the website.
    3. Form? Use webform in Publisher
      Preferably use the webform in WebHare instead of a form in a Word document.
    4. Save Word document as pdf or .odt
      Word documents that you put online should be saved in .odt format (open document text) instead of .doc or .docx. Not everyone has the Office software you need, to open them. Same counts for Excel (save as .ods) and Powerpoint (.odp). 
    5. Accessibility checker
      In Acrobat Pro there is a tool (‘Accessibility Checker’) which you can use to check whether your PDF is accessible. You can find it under Tools > Accessibility Checker > Full check.


    Making Office files perfectly accessible is a complicated business, but there are a number of quick wins that you can easily apply yourself. Watch the tutorial video below for a step-by-step explanation.

    The user has the right to receive an accessible document from the University of Twente and to request such a document if necessary. In the latter case, Marketing & Communication can help to make a document accessible. 

UT accessibility declaration

The University of Twente has drawn up a concise accessibility statement describing the current efforts to make accessible.

Sources and suggestions