So, you’re a Web developer and you want to get started with accessibility? It seems overwhelming, right? It doesn’t have to be. But you’ll need to do some homework. Luckily, there are a lot of amazing resources out there. Here are a few that I’ve curated which are essential to your journey. Semantics First of all, it’s important to understand the relevance of writing semantic code. The article Semantics to Screen Readers written by Melanie Richards dives into how your code will be handled all the way to the end-user via a screen reader. Here’s a tip: Study the HTML…
Comments closedCategory: Digital Accessibility
If you want to bring awareness to your colleagues or your superiors, or if you yourself are looking into understanding digital accessibility, these articles will help you get started. Let’s start with the beginning Introduction to Web Accessibility from the Web Accessibility Initiative will provide an overview of context, types of disabilities accessibility practices addresses, what making a website accessible entails and some common examples of accessibility issues. People with disabilities The best way to learn about accessibility is to be familiar with how people with disabilities interact with technology. The article Stories of Web Users, again by the Web…
Comments closedThat’s the life long mission, isn’t it? Plainly put and without dancing around the topic, how is it that people don’t already care? By people, I speak of those of us that work in the Web industry. If you work in this field and you haven’t heard anything about Web accessibility, it’s probably because you live under a rock. But then again, maybe it’s because the education of Web related subjects is still in its infancy. Maybe it’s because of the open and versatile nature of the Web, in that anyone can potentially, with the right tools and motivation, learn…
Comments closedHTML code semantics, forms, tables, Use CSS, Tabbed navigation, Colour contrast, WAI-ARIA attributes. HTML code semantics Following HTML code semantics is fundamental in making your web applications accessible because assistive technologies, like screen readers, rely on the code to transmit the correct information to the user. Forms are communly inaccurate due to a lack of the label tag or the misuse of the input fields.(Check out the W3C for forms in HTML4 or W3C for forms in HTML5.) Another commun mistakes involves data tables weither by not structuring your table with the proper elements or by adding visual attributes that should go…
2 CommentsHere are the main things to think about when designing a website: Maintain a design and layout consistency throughout the site, Avoid clutter, Include written transcript for any audio and visual media, Avoid multiple level menus. Do not have more than two levels, Include a sitemap when your site has embed pages, Avoid making the width of content too large, Any one link should have the same title, Make the titles of the pages clear, Content must be simple and to the point (Especially if your target audience is broad.), Do not add default value in form fields, Make sure…
One CommentThis assessment is very simplistic and constitutes a basic preliminary review. It is not comprehensive nor exhaustive. I chose themes from the Free Theme Directory and searched for Web Accessible and Accessibility. I narrowed my selection by considering which theme would be easily customizable, have good contrast between foreground and background, have elements in a convenient location and be aesthetically pleasing as is. I then used the plugin Demo Data Creator to generate more content for posts, pages, comments and categories. The following themes made the cut: Precious version 4.0.1 At first glance the layout is pretty simple and effective.…
9 CommentsThe secret of the “em” is proportions. Keeping the appropriate proportions regardless of the size. Let’s use font-sizes as an example. First, set a parent font-size as an absolute measurement. Let’s say 16 pixels in the body. All subsequent sizes use the following formula: child pixels/parent pixels = child ems. So if you want an h1 to have a pixel size of 24, then its em unit would be 1.5 (from 24/16). Nested elements require particular attention, because they multiply on each level. If you have a div inside a div and the outer div has a font-size of 1.5em,…
Comments closedThe main consensus is to avoid them. Why you say? Well because it’s not necessary. If you really want to open a link in another tab or window, you can do it yourself: In Firefox, hover over the link you want to access, right-click your mouse to get a menu and click on “Open Link in New Tab” or “Open Link in New Window”. In Internet Explorer, hover over the link you want to access, right-click your mouse to get a menu and click on “Open in New Tab” or “Open in New Window”. I found other compelling reasons to…
Comments closedWebsites dedicated to online awareness and magazines alike are pushing more and more the importance of Web Standards. Sites like A List Apart has been an advocate for Web Standards and Web Accessibility for years. WordPress, Joomla and other content management systems have embraced the principles of accessibility. Forums like Accessifyforum have also seen increased interest. Governments and now Educational Institutions, mainly Universities are taking the matter into their hands. Blogs like www.prettysimple.co.uk/blog and contests like at www.accessibilityinfocus.co.uk encourage and pursue the issue in terms of content, design and context. I even came across a guild for accessible web designers.…
Comments closedLists can be tricky, but as long as you keep a consistent structure and the correct sequence, lists are a piece of cake. Here are the basics to remember: Make your menus into unordered lists, Place the list inside a div, Have an H2 header with menu title (hide it if not need to be visible), The ul has no left indentation (for browser compatibility), Use display:inline for horizontal lists, Breadcrumbs use nested lists, Be diligent. To read more about lists: CSS Design: Taming Lists
Comments closed
