Recently, I had to update an old website of one of my clients so that it could meet the accessibility standards. The idea of digging up old code three or four years ago is simply not appealing, mainly because many of the programming conventions I used were no longer applicable, especially in terms of accessibility. I used to use absolute font size, fixed page width and table to do layout design and space allocation.
Like many sites that were constructed at that time, my client's Web site uses the cascading Style Sheets (CSS) to format the text. It does not use any of the more powerful layout features of any CSS, nor does it allow HTML devices to be independent, which is one of the main advantages of CSS accessibility.
How did the problem come about?
Before I outline a way to make a site more accessible, it may be helpful to understand the causes of today's numerous accessibility problems:
A superficial understanding of HTML: During the 1990 's great Internet development, everyone began to build websites. The WYSIWYG editor makes it easy for almost everyone to build a Web site without having to bother learning HTML. Unfortunately, this ease of use has led to some lame code, which has hampered accessibility.
The limitations of HTML in design: Developers and designers often deliberately mistakenly use HTML tags, especially
What makes CSS more accessible?
CSS emerged in 1996 to address the above problems. By using CSS, you can separate the content of an HTML file from the information about its presentation or style. This allows you to apply accurate formatting and achieve the desired layout without using HTML code that might confuse screen readers and specialized browser software.
For example, although HTML tables are used to arrange tabular data, they are often used to align elements on a page. But the reader and the software for example speech Synthesizer require valid HTML code. So when they encounter a page that incorrectly uses elements such as a table, the resulting results can be confusing to the user.
[1] [2] [3] Next page
tags, to overcome the limitations of HTML in layout and design. This design approach can also lead to code that hinders accessibility.