Note:

If you want to create a new page for developers, you should create it on the Moodle Developer Resource site.

Aria Guidelines: Difference between revisions

From MoodleDocs
(This page will not be migrated to new devdocs)
 
(18 intermediate revisions by 2 users not shown)
Line 1: Line 1:
This is a collection of best practice techniques for use of aria attributes and related features to enable access from assistive technologies in Moodle (e.g. screenreaders, zoom text, keyboard navigation).
{{Template:WillNotMigrate}}


As developers are fixing bugs or designing new interactions for keyboard access, please add to this list of examples.
{{obsolete}}


This page has been replaced because the content was no longer applicable to the current version of Moodle.


== Drag and drop ==
Current documentation can be found here:
=== Summary ===
Drag and drop is an interaction technique involving either a mouse or touch enabled device where content is click and dragged from it's original position into a new position to permanently change the position of the element in the page. Unless care is taken, this interaction is not possible for users not using a mouse or touch interface (this could be a screen reader, or someone may have a motor impairment). Note: providing a non-javascript alternative for this interaction is not sufficient to make this accessible (javascript enabled != can use a mouse).


=== Accessibility Goals ===
[https://docs.moodle.org/dev/Accessibility "Accessibility in Moodle"]
Provide a keyboard equivalent for this interaction.


=== References ===
The previous version of this document can be seen [https://docs.moodle.org/dev/index.php?title=Aria_Guidelines&oldid=42229 in the history]
http://www.w3.org/TR/2009/WD-wai-aria-practices-20090224/#dragdrop
http://www.w3.org/TR/2008/WD-wai-aria-20080204/#dragdrop
 
=== How this applies to Moodle ===
Keyboard navigation for drag and drop has been built into the Moodle yui module moodle-core-dragdrop (once MDL-36002 is integrated). If you are implementing drag and drop in Moodle - use it - don't roll your own. Second - if you are using drag and drop in Moodle - you must use obvious "grab handles" which is a standard element used to initiate the drag and drop. Get a grab handle with M.core.dragdrop.get_drag_handle() (which will return a Y.Node with an image of a grab handle and event listeners already setup).
 
The way this works with M.core.dragdrop is that pressing enter on the drag handle will open list of valid drop targets for the drag with all the correct aria attributes.
 
=== Related tracker issues ===
MDL-36002
 
 
== Opening a dialogue/popup ==
 
* focus
* label
* calling button
* calling link
 
== Collapsing/Expanding ==
 
=== Accessibility Goals ===
You need to alert the user of a collapsing/expanding changes.
 
=== References ===
'''aria-expanded''' http://www.w3.org/TR/wai-aria/states_and_properties#aria-expanded<br/>
'''aria-controls''' http://www.w3.org/TR/wai-aria/states_and_properties#aria-controls
 
=== Related tracker issues ===
MDL-36011

Latest revision as of 08:16, 27 May 2022


Warning: This page is no longer in use. The information contained on the page should NOT be seen as relevant or reliable.



Warning: This page is no longer in use. The information contained on the page should NOT be seen as relevant or reliable.


This page has been replaced because the content was no longer applicable to the current version of Moodle.

Current documentation can be found here:

"Accessibility in Moodle"

The previous version of this document can be seen in the history