Accessibility: Difference between revisions

Jump to navigation Jump to search
Line 6: Line 6:


== TODO ==
== TODO ==
* Add a label tag to each and every form element (Work in progress) -> LDR: Warning, this creates some bugs. It seems label is ok only if it includes an edit form alement like a radio or an input field. Create problem with some js lib if included in other case like in readyonly mode of a form.
Note by LDR: I sorted with what i think shoul dbe a priority
* Add shortcuts to content/search/action/submenu above the menu
 
* Avoid reloading the page as much as possible (cf. Modules configuration page)
# Add a title to all pages to help identify them
* Generate accessible PDF (Element creation order matters)
# Use th tag for table headers -> LDR: Warning, create also pb with some js lib. We started to move to th in past and we add to move back to td. But I can't remember in which case, we experience this...
* Prefer modal popups to message at the bottom of the page or put these at the top
# Add a label tag to each and every form element (Work in progress) -> LDR: Warning, this creates some bugs. It seems label is ok only if it includes an edit form alement like a radio or an input field. Create problem with some js lib if included in other case like in readyonly mode of a form.
* Avoid messages that automatically disapear
# Add shortcuts to content/search/action/submenu above the menu
* Add a title to all pages to help identify them
# Avoid reloading the page as much as possible (cf. Modules configuration page)
* Use th tag for table headers
# Generate accessible PDF (Element creation order matters)
# Prefer modal popups to message at the bottom of the page or put these at the top
# Avoid messages that automatically disapear

Navigation menu