Browser-based implementation of the MyUI Runtime: https://github.com/FraunhoferIAO/myui-runtime

see #6 and #7 (one is a wrapper of the other) but we got totally different results.

How can we address those issues?

Consistent aria support is particularly helpfull for screenreaders I guess so I typically would tag "blindness".

For stuff that makes switch input easier I would tag "physical disabilities".

https://sourceforge.net/projects/tipcon1/files/

Lots of things tagged here seams awkward to me: https://ds.gpii.net/learn/accessibility-masterlist/help-minimize-errors

Particularly those:

https://ds.gpii.net/develop/components?&field_techniques%5B0%5D=1483&field_component_type%5B1%5D=17223

see also #5

http://www.inference.org.uk/opengazer/
https://github.com/cmauri/eviacam
http://theeyeharp.org/
http://housemate.ie/magic-flute/
https://github.com/EsotericSoftware/clippy
https://github.com/AbilitySpectrum/GazeDetector
https://github.com/AbilitySpectrum/blink_based_aural_scanning_keyboard_with_Morse_code_option
https://github.com/AbilitySpectrum/ArduinoAAC
http://www.autohotkey.com/
https://github.com/MastaLomaster/bkb
http://www.cameramouse.org/
http://cnt.lakefolks.com/
http://www.canassist.ca/EN/main/programs/free-downloads/dynamic-keyboard/download-the-dynamic-keyboard.html
http://www.bc.edu/schools/csom/eagleeyes/
http://www.eyewriter.org/
http://www.gazespeaker.org/
http://wiki.cogain.org/index.php/Gazetalk
http://glovepie.org/
http://www.oneswitch.org.uk/2/I/JoyToKey/JoyToKey.htm
http://maavis.fullmeasure.co.uk/
http://www.webbie.org.uk/texttospeech.htm
https://github.com/OptiKey/OptiKey
http://presage.sourceforge.net/
https://github.com/pupil-labs/pupil/

Hardware components:
https://www.eyedrivomatic.org/
http://www.projectvive.com/
https://github.com/AbilitySpectrum/Sensact
http://enablingthefuture.org/
http://www.ki-i.at/4djoystick/
https://www.neilsquire.ca/research-development/projects-activities/lipsync/
http://www.celticmagic.org/
http://www.jouse.com/jouse3/home
https://www.liftlabsdesign.com/store/
http://eyegaze.com/
http://pupil-labs.com/pupil/
http://www.motionsavvy.com/
http://hackaday.com/2015/12/21/20-sip-and-puff-mouse-from-e-cig-and-3d-printing
http://www.tetramouse.com/index.html/

Good morning,

I have noticed react-a11y-dialog is already in the list, however the underlying actual accessible component, a11y-dialog, is not. It might be worth adding. :)

When you have a chance, can you please review the following entry and advise if this one belongs in the UL? Seems to me like this is one for the developers space:
MooTools accessible UI component sets
Developer's website: https://mootools.net/

Best Regards,
Lydia

The following is a working list of products currently listed in the Unified Listing that may instead belong in the DeveloperSpace:

As mentioned by Gregg and Jennifer

A great repo!

10 hardware category
62 in software category

Tweet from @willwade

Did I ever mention that OpenAssistive, the catalog of all things Open & #AssistiveTech is now online and working?
https://openassistive.org

http://whatsock.com/training/matrices/visual-aria.htm

Good morning,

react-menu-button is a React wrapper around inclusive-menu-button from @Heydon (see #6).

Could be worth adding. :)

Good morning,

inclusive-menu-button is a splendid library from @Heydon to create accessible menu button components (sort of dropdown style).

Definitely worth adding to the list. :)

https://css-tricks.com/can-make-icon-system-accessible/

Good morning,

outline-audit is a little script to audit the outline of a document. It detects if certain heading levels have been skipped, or if there is a missing top level heading.

Maybe worth adding to the list. :)

https://www.levelaccess.com/aria-widget-checklist-screen-reader-testing

by Jennifer

Good morning,

a11y-toggle is a small script to create accessible toggle for show/hide regions. It could be worth adding to the list. :)