This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
how_to:accessibility [2011/03/13 01:46] ccagle8 created |
how_to:accessibility [2014/02/07 10:53] (current) datiswous |
||
---|---|---|---|
Line 1: | Line 1: | ||
====== Accessibility Features ====== | ====== Accessibility Features ====== | ||
- | GetSimple has some accessibility features integrated into the backed of the site. The main feature is the ability to use [[http://en.wikipedia.org/wiki/Access_key|AccessKeys]] to navigate around and perform most actions. | + | GetSimple has some accessibility features integrated into the backed of the site. The main feature is the ability to use [[http://en.wikipedia.org/wiki/Access_key|AccessKeys]]((Browsers often have their own acceskeys for controlling the browser, so you should check that they don't conflict.)) to navigate around and perform most actions. |
You can tell if a button and/or link is accessible via an AccessKey if there is a letter within that link that has a dotted underline. | You can tell if a button and/or link is accessible via an AccessKey if there is a letter within that link that has a dotted underline. | ||
Line 7: | Line 7: | ||
{{:how_to:navigation-accesskey.png|}} | {{:how_to:navigation-accesskey.png|}} | ||
- | **HINT:** If you are a developer, you can add an AccessKey to your navigation link by wrapping a single letter in ''<em></em>'' code. | + | **HINT:** If you are a **developer**, you can add an AccessKey to your navigation link by wrapping a single letter in ''<em></em>'' code. If you are a **translator**, you can define the AccessKeys for the main Backend-Tabs in the section |
+ | //For: include-nav.php// in the language-file by wrapping a single letter in ''<em></em>'' code as well. | ||