sprungmarker testet
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. Weiterlesen „WordPress: Accessibility as a patch is not a good strategy“
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:
Accessible 1.0 – an accessible child theme for WordPress Twenty Ten theme – is now around for a while and get some attention and review:
Accessible 1.0 – an accessible child theme for WordPress Twenty Ten theme is now around for a while and is running live on following sites – thanks for testing and using it. 🙂 And just give me a note to put your site or blog into the list:
It is interesting to see the child theme running in the wild and real action. Good examples to get the real edges of the theme.
WordPress 3.0 came out with a new default theme: Twenty Ten. The theme is compared to Kubrick an improvement, but still has mostly the same accessibility issues as its forerunner, 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.
This is where Accessible TwentyTen get’s into: a child theme for the default theme Twenty Ten to get the parent theme more accessible. You get all functionality of Twenty Ten plus accessible features of the child theme. That’s a nice deal. 🙂
And: the child theme uses no templates, only a css file and some programming in functions.php. That’s all. Accessible TwentyTen should only be a small accessible enhancement.
Weiterlesen „WordPress Child Theme for Twenty Ten: Accessible TwentyTen“
Ich mag ja diese nicht mehr allzu neue Welt der Online-Kurse und so habe ich mich an das für mich neue Thema SVG rangewagt. Das W3C hat einen im Herbst angeboten und ich hab ihn durchgezogen.
Durchgezogen ist auch das richtige Wort. Als dann doch Anfängerin zog der Kurs in nur 5 Wochen eine Unmenge an Themen durch. Dazu hatte man stets Teile der Spezifikation, des Online-Materials und des verknappten, vereinfachten Materials durchzuackern. Dann jeweils Hausaufgaben zu erledigen, die sich nicht unbedingt direkt aus dem gerade noch gelesenen Material ergaben. 😉 Also schlicht – man war oft ziemlich auf sich allein gestellt.
Die letzten Monate des Jahres sind irgendwie immer eher stressig – scheint so ein Naturgesetz zu sein. Daher erst jetzt den zweiten Teil zum Thema Webfonts in der Praxis.
Im ersten Teil ging es darum, sich einen Überblick zu Webfont-Services zu schaffen, im zweiten Teil geht es nun um die konkrete Praxis – egal ob es sich um selbst- oder fremdgehostete Fonts handelt – wie sieht das konkrete Ergebnis aus, wo treten die Probleme auf, auf was muss man acht geben, was kann man noch nachjustieren.
Weiterlesen „Webfonts in der Praxis – Teil 2 – Beispielfont Lobster“
WordPress 3.0 came out with a new default theme: Twenty Ten. The theme is compared to Kubrick an improvement, but still has mostly the same accessibility issues as its forerunner, 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.
This is where Accessible 1.0 get’s into: a child theme for the default theme Twenty Ten to get the parent theme more accessible. You get all functionality of Twenty Ten plus accessible features of the child theme. That’s a nice deal. 🙂
And: the child theme uses no templates, only a css file and some programming in functions.php. That’s all. Accessible 1.0 should only be a small accessible enhancement.
You find all informations about Accessible 1.0 on a new site – Accessible WordPress. Please follow updates and download the accessible child theme there: WordPress Child Theme for Twenty Ten: Accessible TwentyTen.
Thanks. 🙂
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: Weiterlesen „WordPress Plugin: MCE Accessible Language Change“