Mario is committed to making websites accessible to all users. He takes into consideration all of the common, as well as most of the uncommon, best practices for making a website accessible. Again, Mario makes every effort to develop pages that are accessible to users who may be:
- Partially sighted
- Mobility impaired
- Dyslexic or cognitively impaired.
- We provide appropriate alternate text for images to help communicate the content of the images.
- Careful consideration of color blindness with regards to color schemes.
- Careful understanding given to non-traditional browsers (i.e. screen readers).
- Links include “title” attributes to help describe the target of the link.
- Acronyms and Abbreviations include "title" attributes to explain their meaning.
- Tables are created so that they are conveniently accessible by screen readers.
As with the original intention of the web, screen readers and other assistive technologies largely ignore visual styling and focus primarily on semantics and structure. Screen readers are audio interfaces. Rather than displaying web content visually for users in a "window" or screen on the monitor, screen readers convert text into synthesized speech so that users can listen to the content.
Note: Software programs can access any content and read electronic text out loud so that a blind person can use a computer.
Important: In today's current market place accessibility also refers to device independence, which means that sites and applications can dynamically resize and adapt to different browser and device viewports.
- Section 508 Accessibility Program
- SitePoint: How to Use ARIA Effectively with HTML5
- UX Magazine: 15 Website Accessibility Tips That Increase Everyone's Engagement
- Web Accessibility Initiative (WAI)
- Web Content Accessibility Guidelines (WCAG) Overview