Screenshot Accessible Five child theme for TwentyTenFive
WordPress 3.0 got a new default theme: Twenty Ten. It’s doctype is yet HTML5, but the rest is still old XHTML. This is where TwentyTenFive get’s into. It’s mission is to get Twenty Ten upgraded to HTML5.
This is indeed a real improvement, but still has the same accessibility issues as Twenty Ten, e.g. not enough contrast in colors, few improvements for keyboard users and you get no real information about user’s location within a web page.
Continue reading “WordPress Child Theme for TwentyTenFive: Accessible Five” »
I got somehow more professionalized in developing themes. There is now a development host running for my accessible child themes. WordPress provides a database for theme developers. So a developer can check a theme with standardized data to get all aspects of a WordPress theme running.
That’s why I now can offer a more solid update of Accessible TwentyTen – an accessible child theme for Twenty Ten. Continue reading “Accessible child themes: Updates” »
For developing purposes I am using now the newest WordPress release – aka nightly builds. I installed therefor the plugin WordPress Beta Tester. (Wow, linking is updated in WordPress editor – you can now make internal links easy by searching for terms or choosing articles directly – nice).
I tested Accessible 1.0 – the WordPress child theme – and MCE Accessible Language Change – both are working with the current developer release 3.1.
SteveAlee made an request in WordPress forum to merge the accessibility improvements of Accessible 1.0 into the WordPress default theme Twenty Ten. Of course this would be my favorite goal to get Twenty Ten fully accessible and not to make a child theme for that purpose.
But I followed the development of Twenty Ten in WordPress Core a lot and got the impression that it is not so easy to get Twenty Ten more and more accessible. There is a kind of effort there to get accessibility forward but it takes a lot of time. Even small improvements as the skip link which is not reachable for keyboard users is somewhere in the developing pipeline – in a future release. Continue reading “WordPress: Accessibility as a patch is not a good strategy” »
Screenshot: Buttons MCE Accessible Language Change
One thing I always missed in WordPress editor TinyMCE is to add language change. So I made my first plugin. :) This was somehow hard because it’s not only to get a plugin in WordPress running, you also have to get into programming with TinyMCE. So keep in mind when you use the plugin, I am a novice …
The Plugin MCE Accessible Language Change – now in the WordPress Plugin directory – adds two buttons to the editor: one for changing the language of a word or phrase within a
span element and one for changing or adding the language of already existing block elements as paragraphs or headlines. Furthermore you can add the target language to a link: Continue reading “WordPress Editor Plugin: MCE Accessible Language Change” »