![\"How](\"https:\/\/education.telefony-taksi.ru\/wp-content\/uploads\/sites\/664\/2023\/04\/barrierefreiheit-bei-wordpress-webseiten-68b1.png\")
<\/p>\nModern and search engine optimized web design includes the best possible accessibility of a website. Hearing impaired people, blind people or people with other physical limitations should be able to access the website according to the "Web Content Accessibility Guidelines (WCAG) 2".0" of the "W3C" (World Wide Web Consortium) find web pages that meet certain requirements and facilitate use.<\/p>\n
<\/p>\n
These specifications \/ parameters for accessible web design are:<\/p>\n
Regardless of the hardware and software, accessibility in the context of web offers ensures that people can use the site regardless of their physical limitations. When it comes to the barrier-free design of online presences, the terms "accessibility" are used as an alternative to "barrier-free".<\/p>\n
WordPress websites can be designed as barrier-free as any other website. This requires either manual optimization or the use of specialized plugins or themes.<\/p>\n
Many themes for WordPress are already relatively accessible out of the box. Further it is worth to design the WP website responsive, because mobile optimization simplifies the enlargement for visually impaired users. When setting up the WordPress website should be specifically filtered for accessible themes.
\nTip: If you use third-party themes, you should make sure that they place value on accessibility.<\/p>\n
Tools like WAVE can be used to check if the theme is already accessible. Furthermore, the BITV test offers a good possibility to manually check the accessibility of the site. Unfortunately, the market does not currently offer a plugin for WordPress that makes the website completely and automatically accessible. However, plugins can support website operators to ensure accessibility.<\/p>\n
And everyone can use the following tips to make the site much more accessible. WordPress itself already offers interesting help and possibilities to make a WordPress site easier to read for special programs. This allows special programs and hardware to provide optimal help to people with limited mobility. It is an interaction of different components that makes a WordPress website accessible.<\/p>\n
![\"Accessibility](\"https:\/\/education.telefony-taksi.ru\/wp-content\/uploads\/sites\/664\/2023\/04\/barrierefreiheit-bei-wordpress-webseiten-df5d5.png\")
<\/p>\n
With WAVE you can test websites for accessibility<\/p>\n
Google offers Lighthouse, a tool that helps website owners identify accessibility issues. Quite incidentally, the performance is also tested and it can be distinguished between mobile and desktop in the tests.<\/p>\n
![\"Accessibility](\"https:\/\/education.telefony-taksi.ru\/wp-content\/uploads\/sites\/664\/2023\/04\/barrierefreiheit-bei-wordpress-webseiten-0682a5c-1.png\")
<\/p>\n
The Google Lighthouse results page after the accessibility check<\/p>\n
Images on a WordPress page need a description. This allows the visually impaired to visualize what is depicted. Here WordPress offers a good possibility for detailed description of single images. In the WordPress media library, there are options for image description that is captured by screen readers. Once the image has been selected, it is possible to specify a title or alternative text that is read out to users.<\/p>\n
The title is displayed when the user hovers the mouse cursor over the image. This option is more for visually impaired users. Blind users have the option to have the text read aloud. Title and alternative text may then be identical, because the help software of blind people reads out only one of the two at a time. Plugins like "Access Monitor" hit when both texts are the same.<\/p>\n
The following image is ideal. The name of the image, the alternative text and the caption can give the user info about what to see via a screen reader.<\/p>\n
![\"I](\"https:\/\/education.telefony-taksi.ru\/wp-content\/uploads\/sites\/664\/2023\/04\/barrierefreiheit-bei-wordpress-webseiten-2cc8c9.jpg\")
<\/p>\n
A woman with sneakers is standing on a snakeboard<\/p>\n
General things for images<\/p>\n
Blind people need basic information because they can't see images. Therefore it is important to describe what is visible on the image at all. A more general image description of the image structure is helpful. Further, captions support comprehension. In addition, captions facilitate comprehension for every user and should therefore ideally be visible to everyone.<\/p>\n
There is also an input field for captions. This is used to add a description to an image that can be read by screen readers. This allows even blind or severely visually impaired people to grasp the contents of an image more quickly.<\/p>\n
User groups that use screen readers need links that describe where the online journey goes after the click. Website visitors without visual impairments are also happy about a clear designation. It is simply more pleasant to know where the link leads to before you click on it. Surprises are rather unpopular on the Internet and can lead to the fact that users do not click on the link. D.h. the link text should be descriptive.<\/p>\n
Bad link texts: Link, More, Next, Here ..<\/p>\n
It is easier for screen readers, web crawlers or other technical assistants if content is well structured. Page titles, subheadings and subtitles should be marked with tags like H1, H2 or H3. A well-structured and clean HTML code of the WordPress theme is crucial here. No programming knowledge is required for these options and no special plugins are needed either. WordPress is already able to do this. The codes are well known and available online in a variety of ways. Even tags like "bold", "italic" or "underline" do not require any programming knowledge today. Gutenberg and the TinyMCE editor can set this text formatting without problems.<\/p>\n
![\"Accessible](\"https:\/\/education.telefony-taksi.ru\/wp-content\/uploads\/sites\/664\/2023\/04\/barrierefreiheit-bei-wordpress-webseiten-4db9760.png\")
<\/p>\n
Using the TinyMCE editor, the headings can be easily marked up and thus made accessible<\/p>\n
An example of suboptimal color combinations is a gray font on a white background. Strong contrasts between font and background ensure optimal readability. The ideal contrast ratio can be achieved by a tool. Here WordPress offers a sufficient selection. Just know that strong contrasts are more user-friendly than light gradients that blend into pastel colors.<\/p>\n
![\"Examples](\"https:\/\/education.telefony-taksi.ru\/wp-content\/uploads\/sites\/664\/2023\/04\/barrierefreiheit-bei-wordpress-webseiten-c7178e.png\")
<\/p>\n
Green on black is significantly less legible than green on white.<\/p>\n
As a rule, people without visual impairment have hardly any problems reading texts in smaller font sizes. Those who are a bit farsighted may run into their limits. It is worth using the ideal font size of 16 points. This is set as default in most browsers. Here it is advisable to check and possibly make an adjustment. Possibly. it also makes sense to implement the possibility of font enlargement. For this purpose, there are special plugins that incorporate font resizing.<\/p>\n
If you like to work with capitalized words in a menu or in headings, you want screen readers to recognize that. To make this possible, the CSS command "text-transform: uppercase" should be used.
\nNote: If a WORD is written directly in capital letters, the screen reader reads the individual letters aloud, spells out literally. This can lead to confusion for the listener, so it's better to leave it out unless a spelling is explicitly requested.<\/p>\n
Due to various limitations (for example, spasticity), some people cannot use a mouse and rely on web applications using only the keyboard. To let everyone know where they are on the web page even without a keyboard, selected input fields can be visually highlighted. In many browsers this function is already preset. You can use visual anchors to enable keyboard control.<\/p>\n
Users need to know what data to enter in a contact form. Input fields should therefore be described. It should be noted that the description should be placed outside the field. Only if the field is described outside, it can be read by the wizard. Only setting the attribute "Placeholder" is not enough.<\/p>\n
It makes sense to clearly mark mandatory fields. An asterisk can serve perfectly here. The description of the button at the end of a contact form is important, but often neglected. The action should clearly express what pressing the button triggers. Therefore, a description with "Order" or "Submit" should definitely be provided in this area as well. This gives users who can't see what is being clicked some reassurance.<\/p>\n
Good:
\nLast name (mandatory field)<\/p>\n
Color-blind users can not recognize if a labeling is done exclusively by color. If a mandatory field is not filled out in an online form, there should be more than one colored border around the field. Error messages should be additionally formulated.<\/p>\n
With the WordPress text editor "TinyMCE" (Classic Editor) and the Gutenberg editor, not all texts can be made accessible, but both editors form a basis on which to build. The plugin TinyMCE Advanced offers a good help possibility. In addition to quotations, lists and abbreviations, lists or subheadings can be set off.
\nUsers who have some knowledge of HTML do not need another editor. If the text editor is changed to HTML, one can quickly learn the few markups and adapt the website.<\/p>\n
![\"WP-Accessibility](\"https:\/\/education.telefony-taksi.ru\/wp-content\/uploads\/sites\/664\/2023\/04\/barrierefreiheit-bei-wordpress-webseiten-dba2.png\")
<\/p>\n
WP-Accessibility can be used to optimize WP websites in the area of accessibility<\/p>\n
Sooner or later, everyone who deals with WordPress and accessibility encounters the plugin WP Accessibility by Joe Dolson (hereafter: WPA).<\/p>\n
WPA installs a toolbar to change font size and colors. Thus, accessibility is made possible by manual intervention of the user. So it is not a native accessibility optimization for all. This could be considered a disadvantage. On the other hand, it is also an easy way to quickly add an accessibility option into existing designs.<\/p>\n
Besides the toolbar, WP-Accessibility provides very important optimizations for more accessible websites.<\/p>\n
The plugin has some small weaknesses, but it enables an accessible page without own programming knowledge. You can't provide a perfectly accessible site, but the plugin allows you to get started. People with disabilities will find it easier to use the site.
\nUnfortunately, the plugin WPA cannot replace an accessibility-ready theme. It is not possible to integrate standards-compliant HTML into the theme code via plugin. Further, aspects such as the interaction of design and theme can only be implemented at the theme level. Even in keyboard navigation, the correct focus order is only apparent from the context.<\/p>\n
There is no plugin that offers everything in one. However, there are some plugins on the market that can be helpful. You have to be aware that you can't be sure to be accessible just because a plugin was installed. Also, these plugins do not need to be installed to make the site accessible. It is only shown which options are available on the market.<\/p>\n
There are free variants of each of the plugins that already provide some help. For example, the plugin "Hurrakify" has the option to have individual terms from a text explained using descriptions from a dictionary. With the plugin "Access Monitor" WordPress content is tested for accessibility. You need a little experience with digital accessibility as with all automated testing tools. Thus the individual error messages are comprehensible and can be estimated. Ultimately, each site owner must decide whether images have a meaningful alternative text.<\/p>\n
The plugin "Content Author Accessibility Preview" shows content creators possible accessibility issues before a post is published.
\nNote: Unfortunately, ReadSpeaker's plugin for reading text aloud is a "website slower". It takes several seconds longer until the page is loaded. This can lead to users bouncing before the page is actually displayed. This is especially counterproductive for users who use mobile devices. Generally, severely visually impaired or blind people use read-aloud programs on their own devices. Therefore, such a plugin on a WordPress site is rather not recommended.<\/p>\n
For Google it is a concern that websites are accessible. Therefore, it also makes sense for website owners to make sure they put accessibilty on their To Do list for SEO. If website content is accessible for people with disabilities, the Google Bot will have an easy time as well. Here you can find information from Google about accessibility. Certainly worth taking a look at. Google also offers its own ScreenReader with the ChromeVox.<\/p>\n
Unfortunately, the market does not offer an all-rounder that makes a WordPress site accessible. But with WP Accessibility a start has been made. With this or with a mix of free plugins for different areas, a WordPress site can quickly be made as accessible as possible without additional monetary expenditure. This does not require great programming skills.<\/p>\n
It's important to choose a theme that is already accessible from the start. In this area WordPress offers enough possibilities. Furthermore, a lot can be done with simple means to make the use of a WordPress site easier for people who rely on screen reader programs or have physical limitations. It is the interaction of several components that optimize the result. Instead of mainstream and a universal solution, a conglomerate of different options is available.<\/p>\n","protected":false},"excerpt":{"rendered":"
Modern and search engine optimized web design includes the best possible accessibility of a website. Hearing impaired people, blind people […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[134],"tags":[],"yoast_head":"\n