I am in the process of updating HTML5Accessibility.com (ETA mid September) to take into account the changes in accessibility implementation support in the latest browser versions. I have decided not to update support information for Safari/Webkit on Windows and Opera on Windows or Mac as these browser/OS combinations show no sign of active HTML accessibility implementation support. If and when they do, I will do detailed tests of theses browsers once again.
While discussing long descriptions on the HTML working group mailing list I took a look at how some sites provide skip links as an example of contingent visible display of content as a more palatable design concept for some accessibility features, as against always displayed or always visually hidden.
The internet has opened the world to me in truly countless ways. However, that isn’t to say I don’t face numerous obstacles along the way. To understand the obstacles I face while using the web, a snapshot of my disability might be beneficial.
As web designers we must constantly criticize and re-evaluate our own digital works. Many rework changes into website aesthetics or graphics, maybe an updated site logo or sidebar. Ultimately where we should be focusing towards is user experience and accessibility.
Writing and receiving approval for a business case can be a challenge, especially when the return on investment (ROI) is not clear to management. The landscape of my social networking company is one of high competition and a business model based on receiving revenue from online advertising. We're constantly pushing to innovate new and often complex features, and fix the most pressing bugs.
The goal is to make information —especially content in the Web in Spanish and English— more accessible to people with dyslexia. The model will include NLP methods tested using MTurk and eye tracking with regular and dyslexic