Speaking of Wikipedia reads as follows: accessibility “accessibility is the characteristic of a device, a service or a resource to be easily usable by any type of user.”
A random idea at first sight … The really good encyclopedia does not stop in the citation and a few lines below elaborate on the speech calling it correctly: the term is commonly associated with the possibility for persons with reduced or prevented sensory motor skills, or psychic (living with disabilities is temporary, is stable), use of computer systems and available resources.
Behind that Word then it turns out that there is a world that many times is hidden until you’re gonna get the job right…
We then see some accessibility factors that are shown in the rules from WCAG. I would like to point out that these are just a few minor points that I came across recently. Take it as a “Summary” listing of good practices to be careful if you want to make a web site accessible.
Accessibility factors to which attention
Every email message sent must contain the possibility of direct contact with you (phone number, postal address or email address)
This is pretty self-explanatory, this means that at the bottom of every email sent via web delivery must be present … Watson Elementary!
Make sure that there is a contrast ratio of at least 4.5: 1 between text (and images of text) and background behind the text.
I confess that it took me a while to figure it out … Though investigating it turns out that there are even tools that, by putting the color in the foreground and the background, the report calculated. This parameter is necessary to ensure that the messages are indistinguishable from those who have severe vision problems.
Make sure that the web page contains another CAPTCHA that offers the same functionality but using a different mode.
Translated into the jargon: enter a captcha not only Visual but also sound for the blind
Always declares the background color. Criteria 1.4.3 and 1.4.6 and 1.4.8 of WCAG
First, the criteria are very detailed and articulated; however in my case what it required was to explicitly declare a background color via CSS if there is text.
Make sure the Visual order of the elements corresponds with the order of the SUN
And here … The SEO’S from around the world will turn but it’s the stark truth. To pass this hurdle you have to give up some trickery…
Use the alt attribute for images
This I think is now a dogma for anyone who chews. In this case, accessibility and SEO go hand in hand for luck…
Use the caption tag to attach captions to tables. Use the summary attribute to describe what the table.
I confess that these really were new to me. As long as you don’t know the existence, still think them both senseless … But so is…
Use the headers from h1-h6
I can go on it? I’d say I’m pretty critical anyway
Using the language Declaration in the html tag
html tag allows the use of the attribute lang=it or what you want. Is it OK to use it to allow multilingual voice to readers to choose the appropriate voice and intonation as well as need for Braille readers and to facilitate the choice of dictionaries for search engines.
In forms using the title where it is not possible to use a label
Well, the input field allows (is valid) the inclusion of a title. If you do not use the label is good to use it!
I did not understand what it does with accessibility, especially if understood as defined at the beginning of this article … However it is always a good practice … As far as possible!
The series ends here, although they are only small insights I think know them will help to get the idea that making a site accessible is not easy and often requires a big work, usually not budgeted. Learn to worry a little bit at a time, these issues can only be good for the web and may permit a better fruition of free information to people who have physical difficulties. Let us all a little thought in addition to the Web site?